The Certified Pega System Architect (PEGACPSA23V1)

In case management within Pega, when processing a parent case (P-l) with two child cases (C-l and C-2), the typical configuration requires that both child cases be resolved before the parent case can be resolved. This ensures that all related activities and requirements in the child cases are completed before the overall process (represented by the parent case) is considered complete. This approach is crucial for maintaining the integrity of the case processing lifecycle and ensuring that all necessary tasks are completed before concluding the parent case.

To configure duplicate case search logic to exclude resolved cases:

D. Add a must match condition where the work status of potential duplicates does not contain " Resolved " . This configuration ensures that the duplicate search logic explicitly filters out cases that have been resolved, thereby focusing only on active cases when evaluating for potential duplicates. This prevents already resolved cases from being considered in the duplication check, maintaining the relevance and accuracy of the duplicate search process.

In the context of creating a customer loyalty account where the customer ' s contact information is captured and displayed within the case, organizing and relating this data efficiently is key.

B. An Embedded data field : This option allows the contact information (name, email, phone number, address) to be structured as part of the case data in a coherent and integrated manner. Embedding this information ensures it is directly associated with each loyalty account case, facilitating data management and access within the application ' s data model.

A Data reference field (A) links to data instances outside the case, which is not the primary requirement here. A Case reference field (C) is used for linking cases together, which does not apply to this scenario of capturing contact information. A Query field (D) is intended for retrieving data based on a query, which is not relevant for directly embedding and displaying entered contact information within a case.

In a life insurance company with satellite offices in various countries and a policy requiring that underwriting be assigned based on the policy owner ' s residential address, the routing must be dynamic and adaptable to the specifics of each case.

B. Route the assignment to the correct work queue based on business logic : This approach allows for the flexibility to evaluate each policy owner ' s residential address and determine the appropriate satellite office work queue for assignment. By utilizing business logic, assignments can dynamically route to the correct office, ensuring compliance with company policy and efficiency in case processing.

Routing the assignment using an authority matrix (A) or a reporting structure (D) could provide structural frameworks for decision-making but might not offer the dynamic, case-by-case routing needed for this specific requirement. Routing to a specific underwriter (C) focuses on individual assignments rather than the broader need to assign work to office-specific queues based on geographic criteria.

Data transforms in Pega are primarily used for setting property values and manipulating data as it moves from one context to another, which makes them ideal for tasks such as converting data types (e.g., from integer to text) and copying data from existing entities to create new instances (e.g., copying order details to a new case). Data transforms provide a powerful way to define how data should be processed and altered during the lifecycle of a case or data flow.

Certain updates require the capabilities of Dev Studio because of their complexity and the need for custom configuration:

D. A new confirmation view displays a read-only text property. Creating and configuring new UI components, particularly those that involve specific behavior such as displaying read-only properties, typically necessitates using Dev Studio. This environment provides the necessary tools and features to design and implement detailed user interface requirements.

In the Case Designer within Pega, components such as automations and approval decisions can be tagged with a Minimum Lovable Product (MLP) release for project sizing. This helps in prioritizing development tasks: C. Automations are significant because they often represent complex backend processes that can greatly enhance the application’s efficiency and are crucial for an MLP where automated features can define product usability and appeal. D. Approval decisions are key business processes that often require careful consideration and testing to ensure they meet business requirements effectively, making them important to highlight in early releases for user acceptance and feedback.

For enforcing restrictions on income and total liability when applying for an instant loan, a single Validate rule containing two conditions (one for the minimum monthly income of GBP 2000 and another for the maximum total liability of GBP 20000) provides a cohesive validation strategy. This configuration minimizes complexity and ensures that both key financial thresholds are evaluated at the same time, making the validation process more efficient and less prone to errors.

To ensure the accident claim case does not resolve before all associated vehicle claims are resolved, the structure and dependencies between the cases must be clearly defined within the case design.

A. Add each vehicle claim as a child case of the accident claim : This configuration establishes a hierarchical relationship between the accident claim and the vehicle claims. By treating vehicle claims as child cases, their resolution becomes a prerequisite for the resolution of the parent accident claim case. This structural relationship inherently prevents the parent case from concluding before the child cases are resolved.

D. Add a wait step to the accident claim case to wait until all vehicle claims have a status of Resolved : Incorporating a wait step specifically designed to monitor the status of all vehicle claims ensures that the accident claim case only moves forward once every vehicle claim has reached a resolution. This step acts as a checkpoint within the case workflow, enforcing the requirement that all related vehicle claims must be settled before the accident claim can be concluded.

Adding a manual approval step (B) might introduce a review process but does not inherently ensure that all vehicle claims are resolved before proceeding. Similarly, adding an optional process to pause the case (C) provides flexibility in case handling but lacks the direct linkage to the resolution status of all vehicle claims as a condition for the accident claim ' s progression.