The most declarative and standard Pega approach is to use the case life cycle. Adding an ‘Entry’ step to the ‘Create’ stage ensures the task is created as an integral part of the case initialization process, making the design clear, maintainable, and aligned with case management best practices.

SLAs configured to start ‘When the assignment is created’ are designed for assignments that appear in a user’s worklist (like ‘Assign’ shapes). A ‘Utility’ shape executes an activity in the background and does not create a worklist assignment. Therefore, the SLA start condition is never met. The SLA should be configured to start ‘When the flow arrives at this step’ for a Utility shape.

A data page with ‘Load once and use cached value’ caches its data per *access group* by default. If the activity that loads the data does not include logic to filter results based on the current user’s context (e.g., using the Operator ID, Org Unit, or other role-based properties), the first user to trigger the load will cache data that is then served to all other users in the same access group, leading to a data leak.

The standard, declarative way to conditionally hide a UI element is to use the ‘Visibility’ panel on the section or field control. Configuring a ‘Hide if’ (or ‘Show if’) condition that references the value of the checkbox property (e.g., `.CheckboxProperty = false`) will dynamically show/hide the field based on user interaction, meeting the requirement without custom code.

The ‘Subprocess’ shape has a ‘Parameters’ tab where you define both the inputs passed to the subprocess and, crucially, the outputs returned from it. This is where you map the subprocess’s result property (e.g., .CreditStatus) to a property in the parent flow’s primary page. This output mapping is the primary mechanism for the parent flow to receive data from the completed subprocess.

The ‘Trace decision’ rule property is a built-in Pega feature for decision rules (like decision trees, tables, and maps). When set to ‘Yes’, the system automatically records the execution path, including conditions evaluated and results returned, into the standard Pega log (PegaRULES log). This creates the required audit trail without any custom development.

A Connect REST rule defines the endpoint, HTTP method, headers (like the client ID), and authentication. A Data Transform is then used to map the JSON response (the array) into Pega properties. While a Data Page is often the consumer of this setup, the core integration components are the Connect REST rule (for the call) and the Data Transform (for the response mapping).

This requirement is tied to a case life cycle event (resolution), not just a UI action. Using an ‘Exit’ step in the ‘Resolve’ stage declaratively ensures the property is set regardless of how the case reaches resolution (e.g., via the flow action, an automated process, or an API). This is more robust than tying it solely to the UI action’s pre-processing.

For counting records, retrieving the entire list of cases is inefficient. The optimal approach is to use a Report Definition rule as the source for the data page. The Report Definition can be configured with a ‘Count’ aggregate function in its column, allowing the database to perform the count and return only the single number, drastically improving performance.

The most declarative and standard Pega approach is to use the case life cycle. Adding an ‘Entry’ step to the ‘Create’ stage ensures the task is created as an integral part of the case initialization process, making the design clear, maintainable, and aligned with case management best practices.0