Designing Views with Constellation

3 Tasks

30 mins

Pega Platform '26

Pega Platform '25 Pega Platform '24.2 (English) Pega Platform '24.2 (日本語) Pega Platform '23

Visible to: All users Applies to: Pega Platform '26

Intermediate

User Experience

Constellation

English

Scenario

Sweet Life Inc. (SL) wants to replace its legacy complaint management solution. SL has engaged Pega to develop an application called Tell Us More, which can allow Sweet Life to learn more about how its customers perceive their products and services.

The Tell Us More application will be built over an Enterprise Layer that has already been configured for Sweet Life. The Tell Us More application currently consists of three Case Types:

• Incident: Allows users and Case workers to track customer issues and initiates Sweet Life's response to their customers. Incident is the primary Case Type associated with the Tell Us More application.
• Process Payment: Supports payment processing when the resolution of an Incident Case involves a refund or compensation.
• Ship Parcel: Supports package shipment when the resolution of an Incident involves the replacement of a faulty or broken product or the delivery of a gift.

Sweet Life decides to build its Tell Us More application by using the Pega Constellation architecture. You are a member of the team of System Architects who work to configure the UI of the application with Constellation and add missing pieces to the Data Model and application logic as needed to produce an MLP1 solution.

At this point in the application development process, the team focuses on the Incident Case Type. As a System Architect on the Sweet Life application project, your challenge is to configure the Determine Category View that is associated with the Determine Incident Type Step of the Create Stage.

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

Role	User name	Password
System Architect	Author@SL	pega123!

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

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

• Log In

Detailed Tasks

1 Add fields to the Incident Case Type Data Model

1. Open the Dictionary data object and click the Records tab. Note the relationship between Incident Type and Incident SubType records. Subtypes reference a parent type via Parent Key. 
   
2. Click Case Types > Incident.
3. Click the Data Model tab and then click Add Field.
4. Click Add field to add a new field to the Data Model:
   1. In the Field name field, enter Incident Type.
   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.
   5. In the list that is displayed, select Dictionary > List Dictionary Filtered to configure the Data Page source.
   6. In the Data view parameters section, in the Type list, select Constant.
   7. To the right of the Constant value, enter IncidentType.
   8. Leave the value for the ParentKey constant empty.
   9. In the Identifier field and Display field lists, select Key.
   10. Click Submit & add another. 
       
5. Configure another field for the Data Model:
   1. In the Field name field, enter Incident SubType.
   2. Repeat steps 4b to 4f.
   3. In the Data view parameters section, to the right of the Constant value, enter IncidentSubType.
   4. In the ParentKey list, select Field, and then enter or select Incident Type as the value.
   5. In the Identifier field and Display field lists, select Key.
   6. Click Submit.
6. Click Save.

2 Configure the Determine Category View

1. In the Incident Case Type, click the UX tab.
2. In the pane on the right, click the Other Views tab.
3. In the Form section, click Determine Category to open Edit View: Determine Category.
   
4. In the Fields section, click Add, then click Fields.
5. In the list of available fields, select the Incident Type and Incident SubType checkboxes, and then click Add.
   
6. Click the handle for the Incident Type field, and then drag it above the Incident SubType field.
   
7. To the right of the Incident Type field, click the Gear icon to open the Configure field: Incident Type window: 
   1. Confirm that the configuration of the Display as field is Dropdown (default).
   2. In the Conditions section, in the Required field, select Always. 
   3. Click Save.
8. To the right of the Incident SubType field, click the Gear icon to open the Configure field: Incident SubType window:
   1. Confirm that the configuration Display as field is Dropdown(default).
   2. In the Conditions section, in the Required field, select Always. 
   3. In the Visibility section, select Custom Condition. 
   4. To the right of Custom Condition, click the Gear icon.
   5. Create a Condition where Incident Type is not null, and then click Submit.
      
   6. Click Save.

Note: Constellation automatically saves changes to Views when the changes are submitted. Real-time changes to the View are displayed in the Preview pane of the Edit View window.

3 Configure user instructions and helper text

1. In the Edit View: Determine Category window, in the Instructions list, select Override case step instructions.
2. In the Instruction text field, click the Value type icon, select Static (Text), and then enter Please select type and subtype of your incident. 
   
3. To the right of the Incident Type field, click the Gear icon to configure the text for the field:
   1. In the Helper text field, enter Select category of your incident. Is it related to a purchased product or requested service?
   2. Click Save.
4. To the right of the Incident SubType field, click the Gear icon to configure the text for the field:
   1. In the Helper text field enter Choosing the proper subtype allows for faster incident resolution.
   2. Click Save.
5. Click Save to save your work.

---

---

Available in the following mission:

• Constellation Adoption v4