Challenge
Configuring Case locking
Configuring Case locking
1 Task
10 mins
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! |
Challenge Walkthrough
Detailed Tasks
1 Modify the Case Type to allow multiple stakeholders
- In the Pega instance for the challenge, enter the following credentials:
- In the User name field, enter SSA@TGB.
- In the Password field, enter pega123!.
- In Dev Studio select the Candidate Case Type.
- In the Settings tab, click Locking to manage concurrent access.
- Click 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.
- Save your changes.
This Challenge is to practice what you learned in the following Module:
Available in the following mission:
Want to help us improve this content?