A When rule with time qualification is the declarative, Pega-recommended approach for time-based events like escalations. It is efficient, runs automatically in the background, and can be easily configured to respect calendar-based constraints like business hours. The other options are either procedural (Wait shape), inefficient (polling agent), or not designed for automated case escalation (correspondence).

The primary advantage of a Process (configured as a Flow Action) over a Subprocess is architectural. A Process is a standalone, reusable asset that can be versioned, tested, and maintained independently. It promotes encapsulation and reduces duplication. Subprocesses are embedded snippets, making reuse and independent management harder. Both Subprocess and Process shapes can pass parameters, and performance difference is not the key design driver.

The core issue is that the goal is using raw elapsed time (24/7). The direct solution is to change the goal’s ‘Processing type’ to ‘Business time’ and associate it with a calendar that defines the operational hours (8 AM to 8 PM, weekdays). This instructs the system to only count time during the defined business hours. Using start/stop conditions (option B) is for more complex triggers, not for pausing based on a schedule. A When rule (C) is a procedural workaround, not the standard SLA feature.

The expression ‘.PremiumAmount > 10000’ is the standard, readable syntax for referencing a property on the primary page of the context (typically the case or data object) within a flow. The ‘@’ symbols are used in other contexts, like expressions in HTML or certain rule forms, but not for simple property comparisons in a flow condition. Option 0 is clean and directly tests the value.

The most direct and declarative method is to use the built-in visibility and requirement conditioning available on each UI control. On the ‘Condition’ tab of the field, you can set a visibility condition (e.g., ‘.CustomerType == “Promotional”‘) and a ‘Require if’ rule (which can be the same condition). This is a core Pega feature for dynamic UI behavior. Dynamic Layouts (A) are for more complex restructuring, and separate views/sections (B, D) are less efficient for a single field.

For the data from a connector to be saved into the Pega clipboard and used in the case, it must be written to a page. The ‘Page’ field on the connector’s ‘Response’ tab is critical—it defines the destination page (e.g., .CustomerPage). The mapping then populates properties on that page. Without specifying a target page, the data is processed but not persisted to the clipboard for use in the UI or subsequent steps. Data Transforms (B) can be used for further manipulation, but the initial save is controlled by the ‘Page’ setting.

The most efficient and maintainable method is to leverage the existing approval assignment. You can add a new outcome (e.g., ‘Modify’) to the assignment’s configuration. Then, in the flow, you can add a connector from the approval step labeled with this new outcome. This connector can route the case to the desired previous stage. This approach reuses the existing process logic and UI, merely extending its options.

For a calculated field to update dynamically in the UI as the user types in other fields, the control for the calculated field must have the ‘Refresh after input change’ property enabled. This triggers a partial page refresh, which will re-execute the Calculate rule and display the new value. The ‘When’ setting of the Calculate rule (A) governs when it runs on the server, but the UI refresh behavior is controlled at the control level. Client-side scripting (C) is not the standard Pega approach for this.

An Agent rule is designed for scheduled, background processing that operates across multiple data instances (like archiving old cases). It runs on a defined schedule (e.g., daily at 2 AM) and executes an activity. A Schedule rule (A) is for launching flows or activities at a specific time for a specific case. A When rule (C) is instance-specific (e.g., ‘for this case, do something after 90 days’). A Background Process shape (D) runs within the context of a specific case flow.

A When rule with time qualification is the declarative, Pega-recommended approach for time-based events like escalations. It is efficient, runs automatically in the background, and can be easily configured to respect calendar-based constraints like business hours. The other options are either procedural (Wait shape), inefficient (polling agent), or not designed for automated case escalation (correspondence).0