I have a large process that I want to break up into more reuseable parts. I need to be able to combine these into screen flows for use in different stages. Looking at the documentation I have found this is supported as long as the sub flows are also screen flows.
I am not using breadcrumbs in the UI.
The issue I have found is that the 'Back' navigation button is not working on the assignment directly following a subflow. It is taking the user back to the last assignment in the current flow not the last one of the sub flow.
Is there an easy way to stop this / some configuration I have missed? I want the behaviour to be the same as if all of the assignments are in the same screen flow.
This is expected behavior by pega, If you want to achieve this you have to remove the subprocess and use all the assignment shape in the Same screenflow.
Cause : Creation of Supprocess is nothing but a different instance of flow, which you are referencing it within a Screenflow. Therefore Whenever you trying to navigate back it is looking for current Instance rather than moving the control to different instance.
Posted: 3 years ago
Posted: 5 Aug 2019 6:42 EDT
Michael Greenwood (Michael Greenwood)
Where does it say this is expected behaviour? Reading this (which is the 8.1.5 help file) I would say its not behaving as I expected. If calling a screen flow from another screen flow is allowed then the rest of the functionality (i.e. navigation and UI) should also work.
I get why this is hard to implement as the sub flow won't exist any longer on the item, but if this is the limitation then I would say its not really supported functionality and the documentation should be updated. I can't see why you would want to call a sub flow within a screen flow if you can't navigate back.