In Pega, a Case Management platform, the Case Workflow is the process by which a case is moved through various stages of resolution. The Case Workflow can be controlled through the use of Work Objects, Work Baskets, Stages, and Rules. Work Objects represent the cases themselves and hold data and status information. Work Baskets are used to categorize and prioritize work objects. Stages define the steps or milestones in the resolution process, and Rules determine how cases move from one stage to another. Additionally, the Case Workflow can be customized using Pega’s Process Designer, which allows for the creation of custom stages, branching logic, and other features that can be used to control the Case Workflow.
Parallel processing in Pega
Parallel processing in Pega refers to the capability of executing multiple tasks or activities simultaneously within a single case or process. This allows for faster resolution times and increased efficiency. Parallel processing can be achieved in Pega through the use of parallel gateways in the process flow, split and join shapes, and parallel assignments.
The parallel gateway in Pega allows multiple branches of a process to be executed in parallel. The split and join shapes can be used to create parallel branches and to synchronize the execution of activities in the branches. Parallel assignments can be used to divide a single task into multiple subtasks and to allocate each subtask to a separate worker or group of workers.
By utilizing parallel processing in Pega, organizations can improve their overall process performance and increase the efficiency of their operations. However, it is important to carefully design and implement parallel processing to ensure that it meets the specific needs of the organization and does not negatively impact performance or stability.
How to perform processes in parallel in Pega
To perform processes in parallel in Pega, you can use the following steps:
- Define the parallel branches: Identify the tasks or activities that can be executed in parallel and group them into separate branches.
- Use a parallel gateway: In the process flow, use a parallel gateway to split the flow into multiple branches, allowing each branch to execute independently.
- Create parallel assignments: Divide a single task into multiple subtasks and allocate each subtask to a separate worker or group of workers. This can be achieved through the use of parallel assignments in Pega.
- Use a join shape: At the end of each parallel branch, use a join shape to synchronize the execution of activities and wait for all parallel branches to complete before moving on to the next stage of the process.
- Test the parallel process: After you have created the parallel branches, test the process to ensure that it meets the desired requirements and performs as expected.
By following these steps, you can perform processes in parallel in Pega, improving process performance and increasing efficiency. However, it’s important to carefully design and implement parallel processing to avoid potential issues such as race conditions, deadlocks, or resource contention.
Alternate Paths in Pega
In Pega, alternate paths refer to the ability to have multiple branches in a process flow that can be taken based on certain conditions. Alternate paths can be used to provide different paths of resolution for a case based on specific data, user input, or other factors.
To implement alternate paths in Pega, you can use decision shapes or rules that evaluate conditions and determine which path to take. For example, you could use a decision shape to determine whether a case requires additional review or approval based on its priority or complexity, and then route the case down the appropriate path accordingly.
The use of alternate paths can greatly increase the flexibility and adaptability of a process, allowing it to handle different types of cases and situations. However, it is important to carefully design and implement alternate paths to ensure that they provide the desired outcomes and do not introduce additional complexity or confusion into the process.
Optional actions in Pega
Optional actions in Pega refer to actions or activities that can be performed but are not required to complete a case. These actions can provide additional functionality or options for a case, but they can be skipped or bypassed if not necessary.
To implement optional actions in Pega, you can use a decision shape to evaluate conditions and determine whether the optional action should be performed. For example, you could use a decision shape to check if additional documentation is required for a case, and if it is not, skip the step to gather the documentation.
Optional actions can provide greater flexibility and customization to a process, allowing for different paths or scenarios to be handled. However, it is important to carefully design and implement optional actions to ensure that they do not introduce complexity or confusion into the process.
Adding optional actions to a case in Pega
To add optional actions to a case in Pega, you can follow these steps:
- Identify the optional action: Determine which action or activity in the process flow should be optional and what conditions should be evaluated to determine if it should be performed.
- Create a decision shape: In the process flow, add a decision shape to evaluate the conditions that determine if the optional action should be performed.
- Define the conditions: In the decision shape, specify the conditions that determine if the optional action should be performed. You can use expressions or rules to define the conditions.
- Connect the decision shape to the optional action: Connect the decision shape to the optional action to be performed. This can be done by using a flow action shape.
- Add a flow action shape for the case to continue: If the optional action is not performed, connect the decision shape to the next step in the process.
- Test the optional action: Test the optional action to ensure that it works as expected and that the process continues correctly if the optional action is skipped.
By following these steps, you can add an optional action to a case in Pega, providing greater flexibility and customization to the process. It is important to carefully design and implement optional actions to ensure that they do not introduce complexity or confusion into the process.
Skipping processes and stages in Pega
In Pega, skipping processes and stages refers to the ability to bypass certain steps in a case or process flow if they are not necessary or if specific conditions are met. Skipping processes or stages can improve the efficiency of a process by reducing the number of steps that need to be taken to resolve a case.
To skip processes or stages in Pega, you can use decision shapes or rules to evaluate conditions and determine if a step should be skipped. For example, you could use a decision shape to determine if a case is of low priority and can be resolved without going through the normal approval process, and then route the case directly to the resolution stage.
The use of skipping processes and stages can greatly increase the flexibility and adaptability of a process, allowing it to handle different types of cases and situations more efficiently. However, it is important to carefully design and implement skipping processes and stages to ensure that they provide the desired outcomes and do not introduce additional complexity or confusion into the process.
How to skip a process or stage in a workflow in Pega
To skip a process or stage in a workflow in Pega, you can follow these steps:
- Identify the process or stage to be skipped: Determine which process or stage in the process flow should be skipped and what conditions should be evaluated to determine if it should be skipped.
- Create a decision shape: In the process flow, add a decision shape to evaluate the conditions that determine if the process or stage should be skipped.
- Define the conditions: In the decision shape, specify the conditions that determine if the process or stage should be skipped. You can use expressions or rules to define the conditions.
- Connect the decision shape to the next step: If the process or stage should be skipped, connect the decision shape directly to the next step in the process.
- Add a flow action shape for the case to continue: If the process or stage should not be skipped, connect the decision shape to the process or stage that should be performed.
- Test the skipped process or stage: Test the skipped process or stage to ensure that it works as expected and that the process continues correctly if the process or stage is skipped.
By following these steps, you can skip a process or stage in a workflow in Pega, improving the efficiency of the process and allowing it to handle different types of cases and situations more effectively. However, it is important to carefully design and implement skipping processes and stages to ensure that they provide the desired outcomes and do not introduce additional complexity or confusion into the process.