Resuming a flow after the case is transferred from a work basket to work list
Hi, I am trying to find a way to implement a slightly complex functionality. We have existing code in which the case may be in any flow action in Main flow, but when the user tries to cancel the case we will copy the main flow details into a page inside pyWorkPage and remove the main flow and start the cancel flow. Now what we want to achieve is that when they select a particular option when inside cancel flow we want to transfer it into a workbasket. And whenever a user transfers that case into his worklist he have to resume from the screen in which cancel option was selected in the main flow and main flow needs to be continued. Now the details of the main flow are available in the page we copied but I am struggling to find a way to put together all these conditions and achieve this functionality. Any idea on how this functionality can be achieved will be helpful.
Our application was built in Pega 5 and now upgraded to Pega 7.1
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems
US
The safest way to get back to where you were in a flow is to return from a subflow and merely have a flow connector back to where you want to be.
A more-advanced way is to use flow tickets.
Pegasystems
US
The phrases that jump out at me are:
"remove the main flow"
"main flow needs to be continued"
"built on Pega 5 and now upgraded to 7.1"
Without knowing more about your design details, I would say that if you might be continuing the main flow, then don't remove it in the first place.
Did you have all of what you describe working on Pega 5 and now you're trying to move it to 7.1? Or did you never have that part working? If you already had it working, you may be able to use a large part of your design in Pega 7.1.
Tata Consultancy Services
US
Our application was built on Pega 5 but upgraded to Pega 7.1 an year back. So what I was trying to say is that we still use the old Pega 5 flow procedure and not steps and stages. "Remove the main flow" in the sense we end the flow using setTicket "Reject".
No all of what I was describing is not there already.
Things that are there already:
1)User proceeds in main flow. When he tries to cancel the case, we copy the main flow inside a page and give set ticket "Reject" to the main flow. and we start a Cancel flow(A separate flow that is not in main flow). And when certain conditions are met we copy back the main flow to pxFlow from the page we saved and also set the newAssigneePage. So when the cancel flow ends it resumes in where he clicked Cancel in the main flow(This will be done by the same user who cancelled the case).
Things we want to achieve:
1) When the user is in cancel case flow and if certain conditions are met we want to transfer it to a workbasket. And when any user(Not necessarily the one who worked earlier) transfers it to his work list we want to start the main flow again, but also in the same place where it cancel was clicked earlier.
Pegasystems
US
Copying anything to pxFlow sounds dangerous and out-of-guardrails. I suggest you not do that. Why are you doing that? There's probably a simple standard way to do what you are trying to do.
Tata Consultancy Services
US
This is a very old code. Like 5-6 years old. The reason they have done is to come back to the same flow action where Cancel case was clicked. Is there any alternate way to do this.
Accepted Solution
Pegasystems
US
The safest way to get back to where you were in a flow is to return from a subflow and merely have a flow connector back to where you want to be.
A more-advanced way is to use flow tickets.