Repository navigation
Replies: 3 comments 2 replies
|
Short answer: there still isn't a built-in "current progress" projection for rendering a stepper like the screenshot, but the runtime APIs now give you better primitives than relying on If you want to build this dynamically, I would look at these first:
A useful detail here is that Relevant source:
For comments like "manager rejected this step because ...", I would not depend on the journal alone. I'd store that data explicitly in workflow variables or your own domain/persistence model, then correlate it back to For waiting/blocking steps, |
|
Closing this as answered. There still is not a built-in stepper/progress projection for this UI, but the current |
Uh oh!
There was an error while loading. Please reload this page.
I have currently created a fixed step workflow. Defined programmatically. I am using the IWorkflowExecutionLogStore to get the workflow history in order to populate the below. I am wanting a more dynamic approach. Can anyone point me in the right direction? This is especially relevant in the case where a workflow can go back to the begining or a previous step. I need to show the outcome of the step - for example a comment from a manager why the workflow cannot proceed. They need to see that comment in the relevant step.
All reactions