Question
Cognizant
US
Last activity: 4 Aug 2025 16:44 EDT
Back to back processing with child cases assignments is not working in constellation
We have a a place in the process flow that upon submission of a assignment we are creating child cases assigned to the same user. And we have enabled back to back processing in the assignment we are submitting. It is not bringing up the child case assignment in the perform mode to the user even there is no other actions they can perform in the parent.
Accepted Solution
Updated: 4 Aug 2025 16:44 EDT
Pegasystems Inc.
IN
Currently Constellation does not support this behavior.
But a tab is automatically added for the parent case - which lists all the child cases tagged to the parent. You can use this to navigate between the child cases.
A feedback is also raised to the product team.
Pegasystems Inc.
CA
In the latest version, the system displays a list of child cases(Left Navigation menu) immediately after case(s) are successfully created. However, users cannot work on the child cases directly, even though they are assigned to the same user.
Thank you,
HCA Healthcare
US
To make back-to-back processing work with child case assignments in Constellation, make sure the child cases are created immediately after the parent assignment is submitted, and they are assigned to the same user. Enable back-to-back processing in the parent flow action and ensure the child cases are routed correctly to the current user, not to a work queue. Also, check that there are no pending assignments left in the parent case that might block the next screen. Use a synchronous method like pxAddChildWork to create the child cases in the same step, so the system knows to launch the next assignment. This setup helps show the child case assignment screen right away without needing the user to go back to the portal.
Cognizant
US
@Sairohith it was implemented in the way you highlighted here but it was not working. We opened a support ticket as well and it was opened as a feedback item to work on. For the moment we use a workaround of adding items needs to get worked on immediately through local action, which supports back to back processing.