Skip to main content

Linking Cases and Case Types in Constellation applications

3 Tasks

35 mins

Visible to: All users Applies to: Pega Platform '26
Intermediate
User Experience
Constellation
English

Scenario

During the application design phase, the business stakeholders for Sweet Life determined the need to establish relationships between Cases. For example, Sweet Life must recognize similar Incident Cases easily so that the management can evaluate its Caseload more efficiently.

Another business requirement of the Tell Us More application specifies that data related to the shipping process must transfer between the Incident and Ship Parcel Cases.

To facilitate this functionality, you are tasked with configuring the Link Similar and Shipping Service Views in the Incident Case Type.

Note: This challenge has been configured with Single sign-on (SSO) using your Pega Academy credentials. If you are not automatically signed-in to the challenge environment after initializing the instance, you may use the credentials provided.

The following table provides the credentials you need to complete the challenge:

Role User name Password
System Architect Author@SL pega123!
Note: This challenge does not have a demo video. Please refer to the Detailed Tasks for step-by-step instructions to complete the challenge.

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Configure the Link Similar View

  1. In the navigation pane, click Case Types, and then click the Incident Case Type to open it.
  2. On the Workflow tab, in the Process Stage, click the Link Similar Incidents Step.
  3. In the Step pane, click Configure User Action.
  4. Add the Similar Incidents Field to the Link Similar View:
    1. On the View tab, click Add, and then click Fields.
    2. Select the Similar Incidents checkbox, and then click Add.
  5. Configure the Similar Incidents Field:
    1. Click Similar Incidents to open the Edit Field: Similar Incidents pane.
    2. In the Display as list, select Simple table.
    3. Confirm that the Override parameters checkbox is selected.
    4. Confirm that IncidentType is set to Field Incident Type, IncidentSubType is set to Field Incident SubType, and CaseID is set to Field ID.
    5. In the Columns section, remove Primary Fields, and then add ID, Incident Type, and Incident SubType.
      The Edit Field: Similar Incidents pane with Override parameters selected, IncidentType, IncidentSubType, and CaseID mapped to Fields, Simple table in the Display as list, and the ID, Incident Type, and Incident SubType columns
    6. Click Back to return to the Link Similar View.
    Note: The gear icon of the Field (Configure Similar Incidents) sets the Label and the Conditions (Required, Disabled, or Visibility), not the query mapping.
  6. In the Instructions list, select Override case step instructions.
  7. In the Instruction text field, in the Value type list select Static (Text) and enter Link this Incident Case to similar Incident Cases in past for better root cause analysis.
  8. Click Submit, and then click Save.

2 Configure the Shipping Service View

  1. Open the Incident Case Type and click the Data Model tab, and then click the Fields tab.
    The Data Model tab of the Incident Case Type with the Fields tab and the Add Field button
  2. Click Add Field, and then create a Field with the following details:
    1. In the Field name field, enter Shipping Service.
    2. In the Field type list, select Picklist.
    3. In the Display as list, select Drop-down list.
    4. In the Picklist options list, select Data page, and then in the list to the right, select Shipping Service > List Shipping Service.
    5. In the Display field list, select Service Name.
    6. Click Submit, and then click Save.
      The Add Field to Incident dialog box with Shipping Service in the Field name field, Picklist in the Field type list, Data page and List Shipping Service in Picklist options, and Service Name in the Display field list
  3. Click the Workflow tab. In the Fulfillment Stage, click the Dispatch shipment Step, and then click Configure User Action.
  4. Add the Fields Gift SKU, Shipment notes, and Shipping Service to the View.
  5. Drag Gift SKU to the second position.
  6. For each of the three Fields, click the gear icon, set Required to Always, and then click Save.
  7. In the Instructions list, select Override case step instructions.
  8. In the Instruction text field, set the Value type list to Static (Text) and enter Confirm shipment details.
    The Configure User Action dialog box for the Dispatch shipment Step with Override case step instructions, Confirm shipment details in the Instruction text field, and the Shipment notes, Gift SKU, and Shipping Service Fields
  9. Click Submit, and then click Save.

3 Configure the Ship Parcel Case

  1. In the navigation pane, click App, and then on the Classes tab, expand SL-TellUsMore-Work > ShipParcel > Data Model > Data Transform, and then click the CreateShipmentCase Data Transform.
  2. Add a Set action with the target .ShippingService.ServiceName equal to the source ParentPageParamName.ShippingService, and then move it to line 1.
    Note: To move the row, drag it onto the top edge of line 1. If you drop it in the middle of line 1, the Invalid Drag and Drop message is displayed, and the row does not move.
  3. Click Save.
    The CreateShipmentCase Data Transform with a Set action on line 1 that sets .ShippingService.ServiceName equal to ParentPageParamName.ShippingService
    Note: ShippingService is a scalar property in the Incident Case Type but is defined as a page in the Shipment Case Type.
  4. Open the Ship Parcel Case Type, click the UX tab, click Other Views, and then open the Schedule deliver View.
  5. Confirm the Shipment details Field Group contains Shipping Service and Courier.
    Edit View: Schedule deliver with the Customer Info and Product Info Views and the Shipment details Field Group containing Shipping Service, Courier, and DeliveryDate
  6. Click Save.


Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice