Certified Pega System Architect (CPSA) 23V1

To configure cascading approvals in a scenario where approvals move up through an organizational hierarchy (user to loan officer to director to vice president), two effective methods include using an Authority Matrix in conjunction with a Decision Table and leveraging the reporting structure with conditional logic. A Decision Table allows for the definition of approval rules in a structured, tabular format, which is ideal for setting different approval thresholds based on the purchase amount. Using the reporting structure with "when" conditions allows the system to dynamically determine the next approver based on the employees direct reporting line, ensuring that each approval level is adhered to according to organizational hierarchy.

For managing process steps based on customer card types in a credit limit increase application: B . In the Employment Information process add a custom condition to start the process by testing the card type. This task involves integrating a condition right at the start of the Employment Information process to determine the type of credit card a customer has. If the card type is platinum, the condition ensures that the Employment Information process is bypassed, streamlining the application process for customers with this card type. This approach efficiently tailors the workflow to customer segments.

RuleSet names may be up to 64 characters long, but normally are less than twenty characters long. See System limits and maximums

Pega Mobile Preview is a tool within the Pega Platform that facilitates mobile app development by allowing developers to view how applications will look and behave on mobile devices: A . Pega Mobile Preview simulates the application user interface for various mobile devices. This feature allows developers to test and refine the user interface of their applications by providing a simulated environment that replicates how the app will appear and function on different mobile devices, helping ensure that the UI is optimized for mobile usage.

Simulating integrations in Pega is particularly useful when:
A. External services exhibit slow response
times, affecting development and testing cycles. Simulation allows for testing without delays. B. The external service or API is not yet available, but development needs to proceed. Simulation provides a way to develop and test the integration points based on expected behaviors without the actual service being live.

To enforce restrictions that an applicant must be older than 21 and have a monthly income of at least USD 2000 for an instant loan qualification, using a single Validate rule that includes both conditions is efficient.
This method consolidates the validation logic into one rule, making the process streamlined and easier to manage and update, should the criteria change in the future.

For the requirement that a credit check must be completed for a credit card to be approved, incorporating the credit check as part of the credit card application process is necessary. The most straightforward way to model this is by using case type relationships.
C . Make credit check a child case of credit card request: This configuration establishes the credit check as an integral step within the credit card request process, ensuring that the credit check is completed before the credit card can be approved. Making the credit check a child case means it is directly associated with and dependent on the parent credit card request case, aligning perfectly with the requirement. Making both the loan request and credit check top cases (A) does not establish the necessary dependency. Creating a spin-off case (B) suggests a parallel or subsequent process not inherently dependent on the completion of the credit check for the credit card request, which could misalign with the requirement. Making the credit card request a child case of credit check (D) inverts the intended relationship and does not accurately represent the process flow described in the requirement.
Pega's case management documentation provides insights into designing case hierarchies and relationships, including the use of child cases to model dependent processes within an overarching case.

Dynamic UI behavior in Pega is exemplified by interactions that adjust in real-time to user input or conditions: A . Display a message upon form submission that a date field must be in the future. This is a validation feature that dynamically checks the validity of date inputs against the condition set (future date) at the time of form submission. C . Automatically calculate order total when users change quantities. Dynamic UI behavior includes recalculating values in real-time as users adjust input parameters, like quantity in this case, enhancing the interactive experience. E. Display a shipping address section when users select the 'Different than billing address' checkbox. This functionality shows additional UI components based on user selections, which is a key feature of dynamic UIs, allowing for a responsive and adaptive user interface.

In a hiring application that includes tasks performed by different teams"HR creating and sending the offer letter, IT assigning the workstation, and Facilities assigning the work desk"the personas to be created correspond to each team handling specific responsibilities. Each persona represents a user or team involved in the process with distinct roles and access requirements. Therefore, the personas for HR, IT, and Facilities should be created to accurately reflect the workflow and ensure that system permissions and interfaces are appropriately configured for each group's tasks.

To identify the cause of an error in an email confirmation from the employee training portal, it's crucial to replicate the scenario and verify that the correct data is being collected and processed. Creating a test case specifically for the employee portal provides a structured approach to test the entire process flow, including form submissions and email outputs. Adding UI assertions ensures that the interface elements are correctly capturing and displaying the data as expected. Running a new Enrollment case allows for end-to-end testing in the real application environment, ensuring that all components interact as intended and the email confirmation is generated correctly.