Skip to main content

Sourcing a page property with a keyed Data Page

1 Task

10 mins

 Visible to: All users Applies to: Pega Platform '26
Intermediate
Data Integration
Data Management
English

Scenario

You are a Solution Builder working on TGB's HRApps application. Recruiters want applicants to see the job description of a position when selecting an open position during the Submission Stage. To support this, you configure the D_PositionList Data Page for keyed access, source the Position property from the keyed Data Page, and display the Job Description as a read-only field in the Collect Personal Details Step.

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
Solution Builder SSA@TGB pega123!

After completing this challenge, you should be able to: 

  • Configure keyed access on a Data Page.
  • Source a page property using a keyed Data Page.
  • Add a sourced property as a read-only field in a Case View.

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 Sourcing a page property with a keyed Data Page

Solution Builder Advanced Sourcing a page property with a keyed Data Page Doc Journey

Use the technical documentation linked in the Journey map above to complete the assigned tasks. The technical documentation might have more information than you need to complete the tasks.

Acceptance criteria

Task 1: Configure keyed Data access for the Data Page

  • The D_PositionList Data Page has Access pages with user defined keys enabled.
  • The Page list keys field is set to .ID.
    Postion list data page configuration

Task 2: Source the Position property from the keyed Data Page

  • The Position property in the Candidate Case Type is converted to advanced configuration with Data access set to Refer to a data page.
  • The Data Page is set to D_PositionList (TGB-FW-HR-Data-Position) with the key .ID mapped to .PositionAppliedFor.
  • Save parameters with this property for access on reopen is enabled.
    Position property configuration

Task 3: Add the Job Description field as read-only

  • The Position > Job Description field is added to the Collect Personal Details Step User Action view as Read-only under Candidate Case Type.
    Note: If you don't see the Job Description field, mark it as a relevant record. 
  • The fields in the Collect Personal Details Step view are arranged in the following order:
    Order Field
    1 Position applied for
    2 Job description (Position)
    3 Referred by employee?
    4 Referring employee
    5 Candidate (Candidate)

Directions

  1. Open the D_PositionList Data Page and configure keyed access as detailed in the Acceptance criteria.
  2. Open the Position property in the Candidate Case Type, convert to advanced configuration, and configure the Data access section as detailed in the Acceptance criteria.
  3. Open the Candidate Case Type, navigate to the Collect Personal Details Step, and add the Position > Job Description field as read-only as detailed in the Acceptance criteria.
  4. Rearrange the fields to match the order defined in the Acceptance criteria.
  5. Save your changes.

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

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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