Jeremy Posted January 20, 2021 Posted January 20, 2021 When we have issues with BPMs and we go into them to fix them etc, would it be possible to note which nodes the process has been through? When looking at some of our processes where there are multiple branches and nodes it can be difficult to work out which path the process took and either got stuck or sometimes when testing new processes it would be great to see the path the process took. I know that you can click on a node when designing to see the future possible paths, but wondered if this could be done retrospectively so we can check/view flows? Hope this makes sense....
HHH Posted January 22, 2021 Posted January 22, 2021 @Jeremy A tip when creating and testing new BPM's I tend to add a lot of stage checkpoints during design and testing, almost one on each side of every node That way I'm able to follow flows and if the flow stops see where it halts. After testing I remove all the excess checkpoints
Jeremy Posted January 22, 2021 Author Posted January 22, 2021 @HHH that is fine for testing, but I was wondering about this for fixing live bpm errors so that you can follow the flow that the process took to find the possible error beforehand.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now