Automating decisions based on business logic allows application users to focus on more nuanced 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 Pega Platform™, you can model complex case life cycles 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.
In a Pega Platform application, a flow is a sequence of events that models a business process. You create flows to support the different paths that users can take through a case life cycle. You can define paths in a flow by using graphical shapes and connectors. The shapes and settings that you choose depend on the types of decisions that users make, and the order in which the events occur.
In the center of the following image, click the vertical line to compare the case life cycle and process flow views.
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 workflow automatically. An automated decision evaluates business logic or a set of one or more conditions.
For example, the decision shape Credit score in range? models an automated decision following a credit check on a potential policy holder. The decision shape determines if an insurance agency wants to sign a new policyholder. If the result is Yes, then the customer is notified, and the work is routed to the underwriter. If the result is No, then the case proceeds to follow up with the customer, likely with a denial notification.
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 life cycle. By skipping a stage, you can support out-of-sequence processing in a case.
- Cases that go back to the beginning of the current stage. You can use the Change Stage shape to return to a stage in the case life cycle. By revisiting a stage, you can support repeat processes in a case as necessary.
Check your knowledge with the following interaction.