Using Conditions and optional Actions
1 Task
1 hr
Beginner
Case Management
English
Scenario
The Partner Operations Manager at U+ Hotels wants to streamline the Partner Onboarding process by giving onboarding teams the flexibility to stop onboarding when needed, reducing unnecessary compliance work for low-risk and medium-risk partners, and automatically routing partners that fail compliance checks without manual intervention.
As a Solution Builder on the Travel Management Customer Support application, you are asked to implement optional actions, conditions, and decision logic using only the existing Partner Onboarding Case Life Cycle defined in the Blueprint.
The application must meet the following business requirements:
- Onboarding teams can stop onboarding at any point if the partner withdraws or required information is not provided. This requirement is implemented as a case-wide optional action.
- Not all partners require compliance checks. High-risk partners require additional background verification, and low-risk partners skip this work automatically. This requirement is implemented as a Condition on a Process.
- The case is routed automatically based on compliance results. If the partner fails compliance, the case moves to an existing rejection outcome. If the partner passes compliance, onboarding continues automatically. This requirement is implemented as a Decision.
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 may need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Solution Builder | [email protected] | pega123! |
After completing this challenge, you should be able to:
- Configure case-wide optional actions.
- Use a Decision to replace manual routing.
- Control Stage transitions by using automated logic.
Detailed Tasks
1 Use Conditions and optional Actions
Use the technical documentation linked in the Doc Journey above to complete the assigned tasks. The technical documentation might have more information than you need to complete the tasks.
Acceptance criteria
Task 1: Use optional actions
- In the Partner Onboarding Case Type, a Withdraw Partner Application process exists as a case-wide optional action.
- When the optional action is selected, Change to specific stage is configured to move the case to Reject Partner Onboarding Stage.
Task 2: Use conditions on a Process, and a Decision
- In the Compliance Check Stage, the Compliance Check Process runs only when the Partner Risk Profile is High. The Process is skipped for low-risk and medium-risk partners.
- A Decision is configured after the Review Legal Compliance Step, with the following logic:
- If the Compliance Check Status is Failed, the case transitions to the existing Reject Partner Onboarding outcome.
- Otherwise, the case continues to the next Step.
- Manager Approval step under Compliance Check Stage is removed.
- No persona is associated with the Decision Step.
Directions
- Open the Partner Onboarding Case Type.
- Create and configure the Withdraw Partner Application process as a case-wide optional action.
- Confirm that the case transitions to Reject Partner Onboarding Stage correctly when the optional action is invoked.
- In the Compliance Check Stage, On the Compliance Check Process, configure a condition so that it runs only when the Partner Risk Profile is High.
- Add a Decision Step after the Review Legal Compliance Step.
- Configure the Decision outcomes: if the Compliance Check Status is Failed, route the case to the Reject Partner Onboarding outcome; otherwise, continue to the next Step.
- Save the Case Type and then confirm the behavior.
Available in the following mission:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?