Skip to main content

Creating data relationships in Views

4 Tasks

10 mins

Visible to: All users
Beginner Pega Platform '23 Data Integration User Experience Constellation English


The Mayor of MyTown asks you, the town project manager, to enable residents to report problems they encounter on line so that the necessary work can be performed and approved. To accomplish this task, you need to add the project request type to the town's standard online submission form. You also need to encourage users to add their personal information to their report so they can be contacted should additional information be needed to complete the work. You can accomplish this by adding data relationship fields to the Views for the Steps that gather and display the specific information.

Some Views have been previously configured by a different MyTown developer. 

Note: The framework of this challenge uses the Constellation architecture of Pega Platform™. To practice this challenge on the Traditional UI architecture, see the Creating a data relationship version 8.7 challenge.

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

Role User name Password
Application Developer author@mytown pega123!
Note: Your practice environment may support the completion of multiple challenges. As a result, the configuration shown in the challenge walkthrough may not match your environment exactly.

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

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

Challenge Walkthrough

Detailed Tasks

1 Create the Request type data reference field in the Report problem Step

  1. In the Pega instance for the challenge, enter the following credentials:
    1. In the User name field, enter author@mytown.
    2. In the Password field, enter pega123!.
  2. In the App Studio navigation pane, click Case Types > Service Request to display the Service Request Case Life Cycle.
  3. In the Service Request Case Type, click the Report problem Step to open the contextual property pane on the right.
  4. In the contextual property pane, click Configure View to add fields to the View.
  5. Below the Fields section, click Add.
    Locating the Add field button below the Fields section of the Report problem configuration screen.
  6. Click Fields > Create new field to open the Add field dialog box.
    Highlighting the location of the Create new fields button.
  7. In the Name field, enter Request.
  8. In the Type list, select Data reference
  9. In the Data object list, select Request type.
  10. In the Options field, select List of records.
  11. Click Submit to close the Add field configuration window. 
    Modal window highlighting the Request data reference field.
  12. Using the left-side Direction icon, drag the Request row to drop it above the Description (ServiceRequest) field.
    Request added to the list of fields,

2 Configure the properties of the Request field

  1. To edit the properties of the Request field, click Request.
    Request data relationship link
  2. In the Input settings section, in the Display as list, select Combo-Box.
  3. In the Display field list, select Type.
    Highlighting selections for the Display as and Display for the Request field.
  4. Click Back to return to the Edit View: Report problem window.
  5. To the right of Request, click Configure to open the Configure field: Request dialog.
    Request data reference Configure icon
  6. In the Conditions section, in the Required list, select Always.
    Highlighting the value of Always for the Required field.
  7. Click Save to dismiss the Configure field: Request dialog.
  8. Click Submit to finish configuring the Request View properties.

3 Create the Embedded Data field Submitter Information

  1. Click the Identify submitter Step to open the contextual property pane on the right.
  2. In the Step properties pane, click Configure View.
  3. In the Fields section, click Add.
  4. Click Fields > Create new field to open the Add field dialog box.
    Highlighting the location of the Create new fields button.
  5. In the Name field, enter Submitter information.
  6. In the Type list, select Embedded Data.
  7. In the Data object list, select the Person data object.
  8. Confirm the radio-button selection is Single record.
  9. Click Submit.
    The Submitter information field configuration box.

4 Create the Submitter Information View

  1. In the Fields section, click Submitter information (Person)
    Selecting the Submitter information (Person) field
  2. To the right of Primary Fields, click the Remove icon to delete the Primary Fields row.
  3. Click Add > Fields.
  4. Select the Address, First name, Last name, and Phone fields, and then click Add.
  5. Using the Direction icons, drag the rows in the order of First name, Last name, Address, and Phone.
    Fields in the Submitter information view
  6. Click Submit to finish configuring the Submitter information View.
  7. Click Save.

Confirm your work

  1. In the Service Request Case Type, click the Data Model tab to confirm that the Request and Submitter information data relationship fields are displayed. 
    Service request data model
  2. Click Save and run.
  3. In the Report problem Step, confirm that the Request field is required and displays a combo-box that provides the Types: Traffic signal, Pothole, Park maintenance, and Road debris.
    Report problem view with Request options displayed
  4. Select Traffic signal, and click Next to advance the Case.
  5. Click Next to advance past the Identify location View.
  6. In the Identify submitter Step, confirm that the View has First name, Last name, Address, and Phone fields.
    Identify submitter view at runtime

This Challenge is to practice what you learned in the following Module:

Available in the following missions:

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