Discussion
Water NSW
AU
Last activity: 3 Aug 2017 5:09 EDT
Wait for Dynamically Created Sub Cases of Different Type to Resolve
Hi,
We are creating sub cases dynamically using the "Create Cases" flow shape.
The sub cases are of different sub classes from the class of the parent case.
They are created from a page list. Example: subCasesList.pxResults. Here, the pxResults pages will be of different classes.
The number of each of the cases created will vary.
The Problem:
The parent case needs to wait in the current step until all of the sub cases are resolved. Once all of the subcases are resolved, the case should move to the next stage/step.
Solutions Tried:
1. Included consecutive Wait shapes for each type of case. - Flow did not progress.
2. Tried including conditions to skip Wait shapes if type of case is not available. We did this by checking if the page list has pxResults pages with pxObjClass of the case type. - Flow always followed the ELSE path and immediately moved to the next stage.
How can this be done? Is it possible to do it without creating individual wait shapes for each sub case?
Pegasystems Inc.
IN
You can have the"AllCoveredResolved" ticket on the parent flow assignment shape where you want to resume. Once all the children are resolved, the parent flow resumes from this assignment. Please let me know if this solves your problem.
Pegasystems Inc.
IN
You should route the parent case to a waiting work basket and have this ticket in another shape in the same flow. It works. When any child is resolved,updatestatus activity checks the parent if all its children are resolved. If yes, this ticket will be set on the parent flow.
Water NSW
AU
Hi Kalyan,
I tried it again. It works. The case waits till all the sub cases are resolved.
The issue is, while waiting, a link is displayed in the Case Contents area. Once clicking on this link, it opens up a sections displaying a button that provides an option to continue the flow if needed.
When we use the Wait shape this does not happen. Is there a way to do the same using the wait shape?
If no other way, we might have to think of customizing the section that displays the progress button i guess.
Pegasystems Inc.
IN
Hi ilhanUwais,
You are right. This way, you will have access to proceed the case further. For that, customizing the pyAssignmentListGadget section will help. Or, an accessWhen rule in the class will also works. Thanks!
-Kalyan
Pegasystems Inc.
IN
would routing the waiting assignment to administrator or auto-process workbasket helps instead of OOTB rule customization? Please share your thoughts...
EvonSys
LK
Hi,
How about creating a declare-Cn Change rule watching for pxCoveredCount & pxCoveredCountOpen properties with condition
pxCoveredCount > 0 && pxCoveredCountOpen ==0
Configure pzChangeStageWrapper activity to run when above condition is TRUE. So the flow will go to next stage only when all covered cases are resolved.
Regards,
Asela
EvonSys
LK
Hi Kalyan,
We could achieve this by using OOTB ticket AllCoveredResolved as shown in attached screenshot. Using boolean condition
pxCoveredCount > 0 && pxCoveredCountOpen ==0
will prevent flow from going to the next stage. We need not assign WOject to a WBasket. Could be done while WO is in current user's WList.
Regards,
Asela
CPFB
SG
Hi Asela,
This scenario is checking all child cases, I have a requirement where Parent case contains different class child cases and I need to check only particular child case to be resolved to close parent case. I tried wait shape but for this is routing to WB to wait. But I need to stop Parent case for the particular class child case without routing the assignment.
Could you please provide me the possible approach for this scenario.
Water NSW
AU
Hi everyone,
The above solution by Asela is what we have implemented for now. We had to remove the Submit button in the flowaction, so that the flow will not go into a loop when the user keeps clicking submit.
This is sort of a small hack. Please suggest if there are any other better ways to do this.
Thanks!
Virtusa Corp.
US
Hi Ilham,
In Action tab of the flowaction you can check Hide the default action section buttons which will not allow the user to proceed further, i.e. if you route the case to any work basket and select check box would benefit un-necessary actions performed by the user even acidentally opening the case from basket
Water NSW
AU
Hi Raghu,
Thank you for your reply. However, that is exactly how we have hidden the Submit button currently.
We are looking for another way to make the parent case wait until all the subcases are resolved instead of the above loop method. Appreciate it if you can suggest something for that.
Thank you & regards
Ilham
Virtusa Corp.
US
if you dont want to hide the submit button from flow action as well, route the work item or case to workbasket where none of the user have access to pull the case from this workbasket. You can give access to administrator only.