Using a stage pre-condition is the standard Pega best practice for conditionally including or skipping a stage based on case data. It keeps the case type maintainable, avoids duplication (unlike option B), maintains a single coherent flow (unlike option C), and enforces the business rule automatically without manual intervention (unlike option D).

The requirement is a classic data segregation or ‘scope of influence’ rule based on organizational structure (branch/territory). In Pega, this is implemented through access roles that leverage the Organization (Org) and Division (Div) hierarchy to filter which instances of a case (or other data) a user can access. The other options control the ability to perform actions or view UI components, not filter data based on organizational attributes.

A Declarative Expression is a rule that automatically calculates and maintains a property value (like ‘estimated delivery date’) based on other data (warehouse, shipping method, holidays). It recalculates automatically whenever its inputs change, ensuring the value is always current. A Decision Table (A) is for complex conditional logic, a When Rule (C) is for conditional logic in flows, and an Integration Connector (D) is for calling external systems.

Creating two separate Page List properties is the optimal design. It correctly models the one-to-many relationships (one claim has many parties, one claim has many items) using Pega’s embedded page structures. It is more scalable and maintainable than a single mixed list (A) or flat fields (D). Creating separate case types (C) is over-engineering for data that is intrinsically part of the claim and doesn’t need its own independent life cycle.

A Custom Calendar allows you to define specific business hours and holidays. This is required to correctly handle the ‘4 business hours’ metric and the complex rule about weekends. You can configure the calendar to exclude nights and weekends, ensuring the clock pauses at 5 PM Friday and resumes at 9 AM Monday. A Pause/Resume (A) is for event-based pauses, not scheduled ones. Urgency (C) and Routing (D) don’t control the timing logic of the SLA itself.

The ‘Reporting’ structure (often selected as ‘Manager’ or ‘Manager-of’ in the routing screen) leverages the organizational hierarchy (Org chart) built into Pega. You can specify a starting point (e.g., the case’s ‘Employee’) and set a depth (e.g., 2 levels) to automatically route to the direct manager and then escalate up the chain, perfectly matching the business rule. This is dynamic and maintainable compared to static lists (A) or complex custom code (D).

Applying a visibility condition directly on the control (the field widget) is the simplest, most declarative, and maintainable way to show/hide a single field based on a property value. It keeps the logic close to the UI element it affects. Using a section pre-condition (A) is better for showing/hiding groups of fields. Options C and D are overly complex and not standard Pega low-code best practices for this simple requirement.

The Wait shape is specifically designed to pause the execution of a flow (the parent case) until a specified condition is met, such as a child case reaching a certain status or milestone. You can configure it to wait for the ‘Fraud Check’ child case to reach the ‘Resolved’ milestone, which perfectly models the business dependency. A stage pre-condition (B) would prevent entry but wouldn’t ‘wait’ for an asynchronous event. An Event (C) could react but doesn’t inherently pause the flow. A Connector (D) is for integrations, not internal case coordination.

A Declare Trigger rule is the correct solution for implementing real-time, event-driven logic in response to data changes. It is triggered automatically when a specified property (e.g., AccountStatus) is updated, and it can execute a data transform to clear the other fields. This happens on the server immediately, providing a seamless user experience. An OnChange event (A) is client-side and less robust for complex business logic. Options B and C require explicit user or process steps, not automatic real-time action.

Using a stage pre-condition is the standard Pega best practice for conditionally including or skipping a stage based on case data. It keeps the case type maintainable, avoids duplication (unlike option B), maintains a single coherent flow (unlike option C), and enforces the business rule automatically without manual intervention (unlike option D).0