Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Best practices for managing interactions between parent and child cases

Updated on September 6, 2023

Understanding how to correctly handle parent and child cases is crucial to maintaining data consistency and ensuring accurate case processing, especially when interacting with parent and child cases on multiple tabs within the same user session.

Note: Applicable to Theme Cosmos applications.

In Pega Platform Case Management, you can start multiple child cases from a parent case and work on the child cases in parallel to the parent case, which speeds up case resolution.

Typically, you use child cases when you want to model work:

  • that is performed by different parties
  • that follows different reporting options
  • that follows different time frames
  • that is common to multiple case types

You add a child case to a case type by adding a Create case automation step to the case life cycle. When encountering the Create case step, the system creates an instance of the specified child case type and copies data from the parent case (cover case), to the child case (covered case).

When a user works on both parent and child cases in separate tabs within the same session, it's essential to understand the expected behavior. If a child case is resolved, the parent case's data on the clipboard is not automatically updated. When the user resolves the child case and goes back to the parent case, the child case data is not updated on the parent case clipboard unless you specifically refresh the parent case. To prevent committing stale data, you must refresh the parent case tab before continuing with its processing.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us