Pega Process Commander Workflow Design

Decision trees (and the Decision shape) are used in Pega flows to implement conditional branching - the equivalent of if...then...else logic. They evaluate conditions and route work down different paths. Utilities (A) perform processing, Routers (C) assign work, and Split for Each (D) iterates - none handle conditional logic.

Work parties are stakeholders interested in a work object's progress and outcome - they receive notifications and can view status, but don't necessarily perform the work themselves. Option B describes work object clusters, C describes performers with restricted access, and D describes users responsible for resolution - all different concepts.

In Pega flows, the Likelihood value on a connector indicates the probability that work will follow that particular path. This is used for SLA calculations, time estimation, and reporting. It does NOT relate to benchmarks (A), goal completion (C), or goal failure (D).

Pega SmartBuild best practices recommend keeping flows contained on a single Visio page for readability and maintainability. Spanning flows across multiple Visio pages (D) makes them harder to understand and maintain. The other options are acceptable: Assignments can have multiple connectors, flows can call subflows, and utilities can be chained.

Work parties represent the people and entities (customers, stakeholders, interested parties) who have an interest in the work object's progress and outcome. WorkList (B) is a user's queue, WorkBasket (C) is a shared queue, and Workgroups (D) are teams of users - none describe interested parties.

Local Flow Actions in Pega allow users to perform additional actions on an assignment without completing it. Actions like attaching documents, updating fields, or adding notes can be performed before the main approval action. This is the standard mechanism for enabling users to attach budget sheets while keeping the assignment open for approval.

Worklist assignments expect routing to a specific user's list, while ToWorkBasket sends assignments to a shared pool. This mismatch causes Pega to suspend the flow and redirect it to the FlowProblems flow for error resolution. The system prevents incorrect routing by triggering this safety mechanism.

A workbasket is a shared queue where assignments wait for any member of a group to process them. This differs from a worklist, which is personal to a specific user. Workbaskets enable workload distribution across teams, allowing multiple qualified users to pick up assignments from the same pool.

Pega has four standard assignment activities: Worklist (routes to individual user), Workbasket (routes to group), Agent (system processing), and External (external system processing). Router is a routing mechanism that determines destination, not an assignment activity type itself.

Activity parameters in Pega provide flexibility to control both the work object's overall status and the specific assignment's status. This allows activities to update state at both levels as needed during processing, enabling fine-grained control over workflow progression.

Connectors from an assignment shape represent regular flow actions that complete the assignment and advance the flow. Connector flow actions are a distinct concept - they are local actions that don't complete the assignment. The statement incorrectly equates these two different types of actions.

Every flow in Pega must have at least one Flow End shape - it's a required structural element. A flow cannot exist without termination points. While flows can have one or many Flow End shapes (useful for multiple exit conditions), having none is invalid and would prevent the flow from being saved.

Local Flow Actions (also called local actions) in Pega allow users to make updates to the work object, including attachments, without completing the current assignment. These actions update the work object and the changes are recorded in the object's history, but the assignment remains open for the actual completion action.

Process Commander (Pega PRPC) includes eight standard service level rules that can be used directly. 'Approval' and 'NotifyManager' are two of these predefined service levels that handle escalation and notification requirements. The other options, 'To Recipient' and 'To Approver', are not standard service levels included out of the box.

Flows and Assignments are core components that work together to manage business processes. Flows define the process path and route work through the system, while Assignments represent individual tasks that users interact with to complete work. Together they 'route work and resolve work' - routing moves assignments to the right people, and resolution occurs when users complete their assigned tasks.

Utility shapes in Pega flows can have multiple types of connectors that determine when the utility activity executes. These include Always connectors (unconditional), When connectors (condition-based), Status connectors (based on work object status), and Else connectors (fallback). All these connector types can emanate from a Utility shape.