Question
Sopra Steria
NL
Last activity: 5 Jan 2026 0:46 EST
Hiding assignments of child cases
In our Constellation UI application we do not want to show the assignments of the child cases in the assignment list. I noticed that the logic for this is implemented in the activity pzSetChildCases that is called from pzSetCaseInfo.
When disabling this step I only get the assignments of my case. These are pz rules. They cannot be overriden. Is there another option to implement this requirement?
Accepted Solution
Sopra Steria
NL
Pegasystems Inc.
CA
Hiding the child case assignments on the Parent Case is not a best practice. This might lead to maintenance issues in the long run. For example, if the Parent case is not resolved because there are dependent child cases still in Open status, I hope you can build security requirements if personas cannot access the child cases (ABAC, RBAC).
Sopra Steria
NL
I understand your concern regarding child cases not visible. We have an overview of the child cases in a tab on the parent case. We want the users to navigate tot the child case and pickup the task from there. On the parent case you cannot submit the last task if there are child cases open.
We still want the same persona to see and access the child case but just not from the assignment list in the parent case. But from our own overview in a tab on the parent case. So I do not think ABAC or RBAC will help.
Pegasystems Inc.
CA
I got it. Thanks for the clarifications. I was under the impression that there are different personas for parent-child cases.
I don't think there is an configuration to hide the child case assignments from the parent case. It's not recommended to override pz rules from a best practice standpoint.
Sopra Steria
NL
Thank you for the confirmation. I agree an override of a pz rule is not a best practice. I have been looking at the requirement from a different perspective. If our client does not want to use the parent case assignment list as a vehicle to access the tasks for a persona. Why do we create child cases. Would a structure with related cases not be a better fit. Will be exploring this in the coming days.
Accepted Solution
Sopra Steria
NL
We have implemented a workaround for this use case. We no longer create child cases but we create related cases. Our user should work from the specific case not from the parent case. With this in mind it makes sense to stop using the parent child relationship.
Intellativ
US
I have a similar requirement and coincidentally I have implemented the related cases concept as well. However, how do you stop the parent case from resolution until all the related cases are resolved? The wait shape only waits for one case type ( when it's not a child case), The ticket concept may not work since the parent case can go to a different stage while the related cases are being worked upon. Thank you
Sopra Steria
NL
We have created an assignment that the user needs to process on the "parent" case. When submitting this assignment we validate if all related cases are resolved. If so the user can proceed. If not the the user gets a message.
We also have made functionality for the user add extra related cases. These are also taken into consideration for the validation.
We have implemented a workaround for this use case. We no longer create child cases but we create related cases. Our user should work from the specific case not from the parent case. With this in mind it makes sense to stop using the parent child relationship.