Pega Flow Design and Shapes

To extend a deadline of 5 business days to five and one half days (5.5 days), you need to add 12 hours. Since the Days field is already set to 5, you only need to modify the Hours field to 12.

In PEGA, routing activities (like Router, Split-Join, etc.) execute their logic and return the result in an output parameter called AssignTo. This parameter contains the name of the assignment that the work should be routed to next. This is a fundamental mechanism for dynamic routing in flows.

Statement A is false because Routers provide general routing logic and conditions, but they don't specify exact destinations. The flow engine determines the final assignment based on the Router's evaluation. Routers set up the decision tree but don't hard-code every destination, allowing for more flexible and reusable routing logic.

In Pega PRPC flow diagrams, a Ticket shape represents an exception handling event. When a ticket is raised, the flow execution immediately jumps to that ticket shape to handle the exception, bypassing normal flow paths.

Assignment flow shapes have several key properties: LocalAction defines actions available at the assignment, Service Level Rule defines the time expectations for completing the assignment, and Assignment Activity specifies what the assignment actually does. These are core configuration properties that define assignment behavior in a flow.

Local Flow Actions are actions that users can perform without leaving the current assignment - things like submitting a form, attaching a document, or taking a side action. These are added to Assignment shapes specifically because that's where users interact with the work. Utility, Decision, and Connector shapes don't have user forms, so they don't get Local Actions.

A connector emanating from an Assignment is called a Flow Action because it represents an action that moves the flow forward. When a user performs an action (like Submit or Approve), they're triggering a Flow Action that routes the work to the next step. Local Actions are different - they're actions you take WITHOUT leaving the current assignment.

Routers can only be attached to Assignments in PEGA flows. Routers provide conditional routing logic for assignments, determining which path the flow should take after an assignment is completed. Utilities and Start Flow shapes are not valid attachment points for Routers - the routing logic is specifically designed to work with assignment-based decision points.

Split For Each takes a single work object and sends it through multiple flows based on a page list or group. Each iteration creates a separate execution path for the SAME work object, not different work objects. This is useful when you need to process multiple items in a list or perform parallel operations on different aspects of a single case.

In workflow and process modeling systems, a Utility component is a versatile node that can emit various types of connectors: Always connectors for unconditional flow, When connectors for conditional triggers based on events, Status connectors that activate based on state changes, and Else connectors as default paths. This flexibility makes Utility components highly reusable in workflow design.

In workflow modeling, Decision nodes do not require explicit connectors for every possible return value. You can design workflows with default/else paths that catch unspecified outcomes, or use implicit handling where some values don't require separate routing. Requiring connectors for every possible value would make diagrams unwieldy, especially for decisions with many potential outcomes.

In Pega Decision shapes, you're not required to create a separate connector for every possible return value. A default connector can handle any return values not explicitly matched, making flows more maintainable.

Integrator shapes in Pega are specifically designed to invoke connector rules, which enable communication with external systems. They cannot invoke service rules directly - that's what the Integrator shape itself is for. The tasks in Integrators run sequentially within the flow, not in parallel.

Pega provides standard router rules, but developers can also create custom router rules to implement specific routing logic. The statement claims you cannot create your own routers, which is incorrect - custom routers are commonly used for specialized routing requirements.

The Split-Join shape in Pega enables parallel processing of multiple subflows on the current work object, improving performance for tasks that can run concurrently. It does NOT operate on arbitrary work objects, and it waits for ALL subflows to complete before resuming the parent flow.

When using a Utility shape in Pega flows, the Activity must be specifically configured as a Utility type to appear in the SmartPrompt list. If it's not showing up, the Activity likely isn't set up properly as a Utility - the class or initialization issues wouldn't prevent it from appearing in the list.

To enable SmartPrompt assistance for Decision connectors in Pega, you must list all possible return values on the Decision's Results tab. This provides the metadata needed for SmartPrompt to suggest appropriate connector labels and configurations. The setting isn't automatic and doesn't go in the Properties panel.

Pega flows are designed with a single entry point, which means only one Start shape is allowed per flow. Multiple Start shapes would create ambiguity about where execution begins. While flows can have multiple End shapes or other branching points, the Start must be unique.

In Pega utilities, the TaskStatus-Add method is used to set a status value that can be tested later in the flow using Decision shapes. Java steps and Transitions don't set flow-testable statuses, and History-Add is for audit trail purposes, not flow control.

In Pega PRPC, Utility shapes support multiple connector types: Always (unconditional execution), When (conditional based on criteria), Status (based on flow status codes), and Else (fallback when no When conditions match). All four types can emanate from a Utility shape.