A screen flow is the most appropriate design for a guided, procedural process where user actions need to be controlled and sequenced. It presents one screen at a time, dictating the navigation path based on prior decisions (like credit score), which ensures compliance with business rules and prevents agents from skipping mandatory steps.

Stage preconditions are evaluated when a case tries to move into that stage. By setting a precondition that checks for the required data (e.g., .CreditCheckStatus = “Complete”), the case will remain in the previous stage until the condition is met. This is the declarative, best-practice approach for modeling dependencies between stages based on data availability.

Pega’s approval shape natively supports multi-vote (or multi-approver) configurations. By setting the ‘Votes required’ to 2 and assigning it to the ‘SeniorAdjuster’ work group, you declaratively enforce the business rule. The system will manage the task, track the votes, and resolve the step only when two distinct users from that group have approved, which is more robust and manageable than creating duplicate manual tasks.

The ‘OnAdd’ method of a file attachment property (a property of type File) is a rule that executes automatically when a file is uploaded and attached to the case. Placing the virus scan logic here ensures it is invoked immediately and consistently for every attachment, without relying on user action or a separate process stage. It’s a direct, event-driven approach.

The ‘Next stage’ dropdown is populated based on the stage connectors defined in the case life cycle design. If a stage has no outgoing connectors, the system has no defined path for the case to leave that stage, which causes it to appear stuck and disables the manual stage advancement option. This is a fundamental design issue in the case lifecycle.

Routing to a work queue allows multiple users to see the assignment. Configuring the queue with ‘Push to worklist’ means the assignment will proactively appear (be pushed) to the worklist of users who are currently subscribed to that queue and are available (e.g., have an ‘On Shift’ status). This combines the shared nature of a queue with proactive distribution.

The most robust, declarative way to enforce a business rule before case closure is through a stage precondition. If a ‘Closure’ stage has a precondition like ‘.CallbackCompleted = true’, the case cannot enter that stage—and thus cannot be closed—until the condition is satisfied. This is a core guardrail in case life cycle design.

A when rule (or a dynamic calculation) is ideal for determining the correct routing destination based on real-time data. The logic can inspect the submitter’s manager (direct report) and then assign the task to the alternative management work group (e.g., if submitter’s manager is a Department Manager, route to Regional Manager work group). This automates the conflict-of-interest check.

Pega’s Audit rule type allows you to define declarative policies for tracking changes to specific properties. You can create an audit policy for the ‘Investigation Notes’ field that records who changed it, the old value, the new value, and the timestamp. This built-in feature is designed for compliance and audit trails without requiring procedural code in activities or transforms.

A screen flow is the most appropriate design for a guided, procedural process where user actions need to be controlled and sequenced. It presents one screen at a time, dictating the navigation path based on prior decisions (like credit score), which ensures compliance with business rules and prevents agents from skipping mandatory steps.0