Question
Last activity: 10 May 2016 12:55 EDT
How to navigate through multiple flows
Hi,
We have a stage based case type, having 2 stages, 3 steps (flows) each.
We have a requirement where the user needs to navigate through multiple Flows (each flow having few screens) back and forth and be able to update the data entered.
Each of the flows to be navigated back and forth have some decision shapes where a few validations happen. These validations decide where the case should proceed next.
I have tried to achieve the navigation initially using 'Local actions'. I've added all the "flow actions" I need to navigate to as local actions on the assignment shape of a flow as required.
This works for going back to the 'previous' screen from 'current screen', but on submitting the 'previous' screen, the 'current screen' is rendered without executing the decision shapes.
The control is taken back to the current screen without executing anything else. (Please see the attached document for screenshots).
"Screen flows" could be used to navigate between screens within the same flow is what I learnt.. Could they also be used between multiple flows..?
Do we have any OOTB feature that allows navigation between flows or can we achieve the navigation somehow?
Thanks,
VSR Krishna Sankarabhotla
Message was edited by: Marissa Rogers - Added Category
Pegasystems Inc.
US
Hello Venkata,
If you're looking for a jump to sort of functionality, you might consider tickets, but you'll want to be careful. What I might suggest is a master flow which calls all of your subflows, that way when you wan to go back, you just need to hit an end shape and pass a value for which flow you want to route to next (you'll need to account for really being done, but arguably "end" could be passed in to say unwind the main flow completely).
Thanks,
Mike
Thanks for your inputs Mike.. Based on your suggestion, I've tried something similar, using Screen flows: I have created a "master flow" as you said,which refers to a "sub (screen) flow" which in turn has 'sub-processes' each referring to my flows. But I have to convert my flows into 'screen flows' as the sub-process in a screen-flow didn't allow me to connect to my original flows (as they are not screen flows).
But doing this, my flows have a few routings to work baskets, which cannot be done in screen flows.... Any ideas on how can I route to a workbasket from a screen flow..?
Pegasystems Inc.
US
Venkata,
I haven't tried doing that in quite some time. If you are trying to route a screen flow to different work baskets, it sounds like you are going outside of the scope of that functionality. Is this whole design something that might be better served using a tree navigation? It sounds like you want your users to be able to jump backwards and forwards as you collect data and that should allow you to do it.
Thanks,
Mike