Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide Log Entry ID as an Output Variable on all Flow Actions #595

Open
justin-lyon opened this issue Dec 19, 2023 · 3 comments
Open

Provide Log Entry ID as an Output Variable on all Flow Actions #595

justin-lyon opened this issue Dec 19, 2023 · 3 comments
Assignees
Labels
Layer: Log Management Items related to the custom objects & Logger Console app Layer: Logger Engine Items related to the core logging engine Logging Source: Flow Items related to using Nebula Logger within Flow Type: Enhancement New feature or request

Comments

@justin-lyon
Copy link

justin-lyon commented Dec 19, 2023

New Feature Summary

I've created a generic Fault Screen that will log all errors to nebula then display a screen to the user with their error message.

It would be very handy if I could display a link to the new Log Entry in the Fault Screen so the end users could include it when submitting a request to our helpdesk.

In order to do that, I would need the Log ID that was created after the Log Error is completed.

image

@justin-lyon justin-lyon added the Type: Enhancement New feature or request label Dec 19, 2023
@jongpie
Copy link
Owner

jongpie commented Jan 18, 2024

@justin-lyon providing a link to the log entry probably isn't feasible - the LogEntry__c record is created async (using platform events), so there's not a Salesforce record/record ID at that point. I'm also limited on what changes I can make to the returned value for the Flow actions (due to limitations with changes in managed packages).

If I'm able to come up with a way to return a link that takes you to the Log__c record (instead of a specific LogEntry__c record), would that work for you? Making it work for a Log__c record is also going to be slightly tricky, but I have a few ideas of how to try to make it work.

@justin-lyon
Copy link
Author

I'm open to alternatives.

Using an external Id field with a guid generated at runtime comes to mind.

@jongpie
Copy link
Owner

jongpie commented Jan 19, 2024

Sounds good - I'm going to try to tinker with a few ideas over the next few weeks to see what's feasible, I'll keep you updated.

@jongpie jongpie added the Logging Source: Flow Items related to using Nebula Logger within Flow label Jan 28, 2024
@jongpie jongpie added Layer: Log Management Items related to the custom objects & Logger Console app Layer: Logger Engine Items related to the core logging engine labels Jul 30, 2024
@jongpie jongpie self-assigned this Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Layer: Log Management Items related to the custom objects & Logger Console app Layer: Logger Engine Items related to the core logging engine Logging Source: Flow Items related to using Nebula Logger within Flow Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants