Automating Decisions in the Process Flow
In Pega Platform™, you can model complex Processes in a Case Lifecycle that require branching or skipping a Step. For example, when a home is above a certain age, it must be tested for lead paint. When a home is below a certain age, it does not need to be tested for lead paint.
To support complex workflows, you design Process Flows that model the different paths that users can take as they navigate through a Case Lifecycle. You can define paths in a flow by configuring the graphical shapes and connectors. The shapes and settings that you choose depend on the types of decisions that users make, the conditions that must be evaluated, and the order in which the events occur.
Automating Process Decisions based on business logic allows application users to focus on decisions that require human expertise. For example, a loan applicant with a low credit score but a high salary and a passing background check may require a loan officer to assess additional qualifying factors that cannot be automated.
In this topic, you examine how Process Flows are automated using Decision shapes and conditional execution.
Decision shapes
You can use a Decision shape to add a conditional path to a flow or model more complex use Cases. By defining the events that cause your flow to follow different paths, you can create Cases that support more than one outcome.
Decision shapes are configured to advance a Process automatically. An automated Decision evaluates business logic or a set of one or more conditions.
Match the numbers to the following image to learn more about a credit check Process with a conditional path:
- Credit score in range?: The Decision shape Credit score in range? models an automated Decision after a credit check on a potential policyholder. The Decision shape determines whether an insurance agency wants to sign a new policyholder.
- Yes: If the automated Decision determines the credit score is in range (the result is Yes), the system routes the work to the underwriter.
- No: If the automated Decision determines the credit score is not in range (the result is No), the Case proceeds to follow up with the customer.
Variations of the Decision Flow
Some variations of the Decision Flow include:
- Cases that move forward but may include another Step as needed. You can choose when additional processing is needed to support Case processing.
- Cases that go to another Stage. You can use the Change Stage shape to move a Case to a different Stage in the Case Lifecycle. By skipping a Stage, you can support out-of-sequence processing in a Case.
Note: For more information about Decision points, see Adding Decisions to a Process.
Check your knowledge with the following interaction:
This Topic is available in the following Modules:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?