Using a Data Transform to set the Assign-To property (like .pyAssignmentTarget) is the most efficient and Pega-recommended approach for dynamic assignment based on user input. It allows the value to be calculated and stored in a property, which is then simply referenced by a standard Assignment shape, keeping the flow clean and the logic reusable. Pre-processing activities or committing in a When rule are less optimal and can cause performance or data issues.

When a utility (sub)flow finishes, it returns an outcome to the calling (primary) flow. If the outcome name returned (e.g., ‘Done’) does not match the outcome name expected on the connector from the Subprocess shape in the primary flow, the primary flow will not follow the intended path and may appear to stall. This is a common configuration error in subprocess invocation.

The ‘Addressed To’ field in the Assignment shape’s configuration is designed to accept a property reference. By entering the property name (e.g., .Reviewer) that holds the party (like a work group or user) calculated by the decision tree, the assignment becomes dynamic. The system will resolve the property value at runtime to determine the actual assignee.

Pega’s default behavior for an Assignment shape is to have the ‘Resolve on stage change’ option checked. This means when the case advances to a new stage, any open assignments from the previous stage are automatically resolved (typically as skipped). To allow an assignment to remain open across stages (e.g., a monitoring task), you must explicitly uncheck this setting in the Assignment shape’s configuration.

The most direct and maintainable way to make an SLA action (like a Warning) conditional is to use a precondition on the specific step (Warning or Deadline). The precondition is a When rule that evaluates at runtime—if it returns true, the step executes. Checking the current stage (.pxStage) is a common and effective condition for stage-dependent SLAs.

A ‘Wait for Condition’ shape pauses a flow thread until its condition is met. However, for the system to re-evaluate the condition after a change made by an external process (like a connector or agent), that external process must explicitly notify the waiting thread. This is typically done by calling the Obj-Notify method or using a standard Notify shape. Without notification, the waiting thread may not wake up to check the updated condition.

The ‘Delegate’ action is specifically designed for temporary reassignment. When a user delegates a task, they specify a delegatee and an optional expiration date/time. The task moves to the delegatee’s worklist. If it is not completed by the expiration time, it automatically returns to the original owner’s (the manager’s) worklist. This is a built-in, user-initiated feature that perfectly matches the requirement.

In a list view (or summary view) rule, you can create a calculated column. The expression for this column can use the @HTML.DecodeText function along with a When rule or a conditional statement to return different HTML image tags () based on the value of the urgency property. This is a standard and flexible way to render dynamic icons directly in a Pega list.

A custom ‘Route to’ strategy (e.g., a Filter strategy) is the most robust and configurable solution. You can pass a page list of potential candidates (like the Approver work group) and a page containing context (like the previous approver’s ID). The strategy’s logic can then filter out the previous approver from the list of eligible users before routing, ensuring they are not selected for the immediate next assignment.

Using a Data Transform to set the Assign-To property (like .pyAssignmentTarget) is the most efficient and Pega-recommended approach for dynamic assignment based on user input. It allows the value to be calculated and stored in a property, which is then simply referenced by a standard Assignment shape, keeping the flow clean and the logic reusable. Pre-processing activities or committing in a When rule are less optimal and can cause performance or data issues.0