Skip to main content


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

Sharing data between parent and child cases

Updated on December 1, 2021

For greater automation of your business processes, you can share data among the cases in your case hierarchy. When you reuse data between parent and child cases, you increase efficiency, improve data consistency, and as a result, resolve cases faster.

Aggregating data in a parent case in Dev Studio

Speed up case processing by configuring a parent case to update specific values each time the values in child cases change.

For example, you can create a parent case that represents a request for an insurance offer, and then supplement the case with child cases that visualize life insurance and property insurance in an insurance application. When a customer service representative (CSR) updates the values in the child cases, the insurance application automatically calculates the total value in the parent case.
Before you begin: Create a child case type. For more information, see Creating a child case type.
  1. In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
  2. Click the Settings tab, and then click Calculations.
  3. In the Calculations section, click Add calculation.
  4. In the Calculated property field, press the Down arrow key, and then select the property in which you want to aggregate data.

    The calculated property stores the sum of other properties, across all child cases of the parent case.

    Caution: Ensure that this property is not associated with a declare expression, because the value of the property can be overwritten.
  5. In the Case type list, select a class of a case type that is a child of your current case type.
  6. In the Property field, press the Down Arrow key, and select the name of a single-value property that you want to add to the cumulative property.
  7. Optional: To add more properties that the system sums up at run time, click Add property, and then repeat steps 5 through 6.
    For example: The following figure shows configuring a property in a parent case to be a sum of two properties from child cases:
    Configuring data aggregation from child cases to a parent case
    Dialog box with a calculated property in a parent case configured to be a sum of two properties from two child cases.
  8. Click OK.
  9. Click Save.
Result: At run time, an application updates the value of the calculated property in the parent case each time you change any of the selected properties in a child case.

Propagating data to a child case

Resolve cases faster by propagating data from a parent case every time you create a new child case. By sharing data between cases, you save time and ensure that your application uses consistent data throughout the entire case life cycle.

For example, you can create a parent case type that represents an accident claim review, and then supplement the process with child case types that visualize the estimation of vehicle damage and injuries. When you then create child case types, your application automatically copies the personal details of the customer issuing the claim into the new child case types. As a result, you save time because the information is already in the child cases.
Before you begin: Create a child case type. For more information, see Creating a child case type.
To propagate data, you first define the source properties in a parent case type that store the information that you want to copy, and then define the target properties in the child case type in which you want to reuse the data.
  1. In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
  2. Click the Settings tab, and then click Data propagation.
  3. In the Data propagation section, click a child case in which you want to reuse data.
  4. Click Add property.
  5. In the Propagate property value field, press the Down arrow key, and then select the source property from which to copy data.
    For example: You can enter a full property name to specify an embedded property. For example, enter .pyWorkParty(Customer).pyWorkPartyUri to specify the pyWorkPartyUri property that is defined on the Customer page of the pyWorkParty page group, as shown in the following figure:
    Entering the full name of a property to propagate to a child case
    A dialog box with the full name of a property to propagate to a child case.
  6. In the To property value field, press the Down arrow key, and then select the name of the property that your application sets in the child case at run time.
  7. Click OK.
  8. Optional: To propagate the values of more properties from the parent case type, repeat steps 4 through 7.
  9. Optional: To apply a data transform to set property values:
    1. Select the Apply data transform check box, and then select a data transform to apply.
    2. On the Definition tab of the data transform, in the Source field, enter pyParentPageName.
      Note: Do not add param before the page property name because the parameter is of the Page name type.
    3. On the Pages & Classes tab, in the Page Name field, enter pyParentPageName.
    4. In the Class field, enter a class that is equal to the class of the parent case.
    5. On the Parameters tab, add a new entry with a name of pyParentPageName.
    6. In the Data type field, select Page name.
      Note: Do not mark the parameter as required because the system provides the value at run time.
  10. Click Save.
Result: At run time, when you create a child case type, your application propagates the values of the properties that you select.

Related articles

Sharing data between parent and child casesSharing data between parent and child casesCreating contextual cases

Tags

Pega Platform 8.7 Case Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

100% found this content useful

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us