PEGACPSA23V1 Exam Dumps - Pegasystems Pega CSA Questions and Answers

When development teams are working on separate enhancements with uncertain release dates, it is practical to: A. Create a new ruleset version for each team, allowing them to manage their versions independently, ensuring that their changes are isolated and do not impact other teams. B. Set up a branch ruleset for each team, which is ideal for supporting parallel development efforts. Branch rulesets enable teams to work in isolation, merging their work back into the main application ruleset once their individual enhancements are complete and ready for integration.

To fulfill the requirement that all managers must be able to view the Employee vacation requests report in their Manager portal dashboards, the report must be made readily accessible in a manner that integrates seamlessly with the existing portal structure.

• D. Add the report to a public category, and then add the out-of-the-box Reports landing page to the portal: This approach ensures broad accessibility by placing the report within a public category, making it available to all managers. Integrating the Reports landing page into the portal provides a centralized location for managers to access this and potentially other relevant reports directly from their dashboard, enhancing the usability and efficiency of the portal.

Creating a new landing page (A) specifically for the new report may not be necessary if the existing Reports landing page structure can accommodate the report, and it may introduce unnecessary complexity. Adding a report widget and publishing it to the default (B) or without specifying the target audience (C) might not ensure the report's visibility to all managers as required.

For time-off requests requiring multiple levels of approval based on the duration of the request, combining a cascading approval process with an authority matrix and custom approvals configured in the reporting structure is effective. The authority matrix can define different approval rules based on the length of the time-off requested, while custom approvals allow for the inclusion of additional approvers, such as HR, when the request exceeds a specific threshold (e.g., three weeks). This ensures that all necessary approvals are obtained in a structured and hierarchical manner.

For a scenario where account information is recorded at the time the case is created and does not update when the case is further processed, while also being stored in an external system and accessed by a data page, the appropriate configuration is:

• D. Select copy from a data page on the page property: This configuration ensures that when the case is created, the account information is fetched from the external system via the data page and then copied to the page property on the case. This copy is static and remains unchanged regardless of any updates to the external system or the data page after the case creation. This approach meets the requirement of capturing account information at case creation that remains constant throughout the case lifecycle.

Option A, B, and C involve referencing the data page directly in various ways, which would not fulfill the requirement for the account information to remain static after the case is created, as any updates to the data page would be reflected in the case.