Pegasystems PEGACPLSA88V1 Exam Dumps

To design a reporting strategy that displays the number of cases by status at the end of each month for a 12-month period, follow these steps:

Configure an Agent: Set up an agent to run at the end of each month to capture the status of all cases.

Record Data: The agent records the case statuses in a separate table specifically created for this purpose.

Reporting: Generate reports based on the data stored in this table to provide an accurate month-end snapshot of case statuses.

Configuring agents in Pega

Create Decision Table:

Go to Records Explorer > Decision > Decision Table.

Create a new decision table that evaluates LDAP attributes (role and application properties) and maps them to access groups.

Authentication Mapping Configuration:

Go to Designer Studio > Security > Authentication Service.

In the mapping tab, configure the authentication service to evaluate the decision table created.

Testing:

Test the configuration by logging in with different users and verifying that the correct access group is assigned based on the LDAP attributes.

Pega Academy: Authentication and Access Control.

Pega Documentation: Decision Table and LDAP Integration.

Separate Mobile Portal: Creating a separate portal for mobile users ensures that the specific needs of mobile interfaces can be addressed without affecting the desktop version. This separation allows for dedicated customization.

Adjust Responsive Behavior: Fine-tuning the responsive behavior within the application skin ensures optimal viewing on mobile devices. Adjustments can include changing breakpoints, font sizes, and element visibility to enhance user experience on smaller screens.

Non-impactful Changes: Both options focus on optimizing the mobile experience while keeping the desktop experience intact, adhering to Pega's principle of responsive and adaptive design.

Reference: Pega recommends using responsive design techniques and, when necessary, separate portals for different device types to ensure a consistent user experience (Pega Platform 8.7 Documentation, User Interface - Skins).

Scenario testing in Pega is used to create UI-based, end-to-end tests for applications. The following statements are true about scenario testing:

Scenario Tests Can Include Another Scenario Test (A):

Scenario tests can be nested, allowing one scenario test to include another. This enables the reuse of common test steps and enhances the modularity of test cases.

Scenario Tests Do Not Support File Uploads or Downloads (C):

Scenario tests are designed to simulate user interactions but do not support file uploads or downloads as part of the test execution. This limitation ensures tests focus on UI interactions and business logic.

Scenario Tests Support the Setup or Cleanup of Test Data (E):

Scenario tests allow for the setup or cleanup of test data before or after the test execution. This capability ensures that the test environment is correctly prepared and that any test data is appropriately managed.

Pega Scenario Testing Guide

Pega Platform Test Automation Documentation

To address performance issues and ensure optimal application performance, the following actions are recommended:

Dedicated a node to background processing (Answer A):

Review application environment sizing (Answer B):

Review selection criteria of agent activities (Answer E):