Skip to main content

Configuring Case locking

1 Task

10 mins

Visible to: All users
Intermediate
Pega Platform '23
Case Management
English
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Scenario

At TGB, candidates applying for an open position are interviewed by three to six existing employees. Each interviewer can independently rate a candidate in parallel Processes. The Human Resources (HR) department determined that multiple interviewers and all HR personnel need to access and potentially update the candidate Case at any time. Human Resources (HR) requests that the application prompts the user to reload or close the Case without saving if changes have already been committed by another user. 

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

Role User name Password
Senior System Architect SSA@TGB pega123!
Recruiter Recruiter@TGB pega123!
Employee Employee@TGB 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 Modify the Case Type to allow multiple stakeholders

  1. In the Pega instance for the challenge, enter the following credentials:
    1. In the User name field, enter SSA@TGB.
    2. In the Password field, enter pega123!.
  2. In Dev Studio select the Candidate Case Type.
  3. In the Settings tab, click Locking to manage concurrent access.
  4. Click Allow multiple users to allow the first user to submit the Case and notify all other users working on the Case to review the changes before submitting new updates.
    case-locking
  5. Save your changes.

Confirm your work

  1. Create a new Candidate Case and advance the Case to the Interviews Stage.
  2. Add the two interviewers in the following image and click Submit.
    multi-interviewers
  3. Verify the two Assignments are displayed. Note the Case number.
    multi-interviewers-assignments
  1. Log out of Dev Studio.
  2. In the Pega instance, enter the following credentials:
    1. In the User name field, enter Recruiter@TGB.
    2. In the Password field, enter pega123!.
  3. On the User Portal home page, in My Worklist, open the Case you noted in step 3, and proceed to the Interview candidate form.
  4. Copy the Pega lab instance URL from the browser window.
  5. In the browser, log in using a different profile, or log in as a guest, to access the same lab instance with two users, at the same time. 
    Tip: The following image is an example of how to log in using an alternate profile in Chrome, however, settings vary by browser. You may also use a private browsing window to log in as Employee@TGB.
    browser-alt-profile-login
  6. In the alternate profile browser window, navigate to the Pega lab instance URL you copied in step 7.
  7. In the Pega instance, enter the following credentials:
    1. In the User name field, enter Employee@TGB.
    2. In the Password field, enter pega123!.
  8. Repeat step 6.
  9. Return to the Recruiter@TGB browser window to complete the interview rating and click Save.
  10. Return to the Employee@TGB browser window to complete the interview rating and click Save.
  11. Confirm that the following message displays to verify the Allow multiple users Case locking strategy.
    case-locking-overlap-message
  12. Click Refresh to update the Case and confirm you can now save your changes.

 


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


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