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

feat: enhance parser to handle time for some events without an end event (workflow + visualforce) #211

Closed
Tracked by #228
lcottercertinia opened this issue Jan 4, 2023 · 0 comments · Fixed by #452
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@lcottercertinia
Copy link
Collaborator

lcottercertinia commented Jan 4, 2023

Is your feature request related to a problem?

Some events take time but have no specific end event e.g WF_APPROVAL_SUBMIT + WF_NEXT_APPROVER
I would like to see them on the timeline somehow.

Describe the solution you'd like

Improve the log parser to show time taken for more events without a specific end
e.g WF_APPROVAL_SUBMIT + WF_NEXT_APPROVER events.
WF: This is just about anything within the code unit workflow or start with WF_

VF: This also happens to some of the events for visualforce, they start with VF_
There may be some handling for VF_PAGE_MESSAGE we can do too

To get some of this to work we may have to do a second parse once the events have become child events of another.
This is because we can always use the end time of the parent of the start time of the next event as a fallback when inferring the end time

Some events do not seem to have an exit but do take up time I would like to see them reflect on the timeline
An example here would be WF_APPROVAL_SUBMIT events and basically any event within the code unit workflow

Describe the solution you'd like

I know this might be tricky and it would be great to get SF to add an end however the next best would be to use the next event along as the end time. e,g for a WF_APPROVAL_SUBMIT event the next WF_APPROVAL_SUBMIT might be the end stamp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant