Pegasystems PEGACPLSA88V1 - Certified Pega Lead System Architect (CPLSA) Exam 8.8

ï‚· Edit Input Rule: Create an Edit input rule on the customerinfo property. This rule will automatically convert the first and last names to upper case when the data is entered or updated, ensuring consistency.

ï‚· Data Transform: Develop a post-processing Data Transform that converts the names to upper case. This Data Transform can be invoked in the flow action to ensure that the names are converted after the user submits the form.

References:

Pega Academy: Configuring Data Transforms and Edit Input Rules

Pega Documentation: Data Transform Rules

To ensure the performance of a Pega application does not degrade over time, two key recommendations are:

Schedule scripts to maintain frequently fragmented tables (C): Table fragmentation can lead to inefficient database performance. Regular maintenance scripts can help defragment these tables, ensuring that data retrieval remains efficient.

Purge and/or archive records based on the company's record retention policy (D): Over time, the accumulation of records can slow down application performance. Implementing a purge or archive strategy based on the company's retention policy helps manage database size and performance.

References:

Pega Database Management: Best Practices for Database Maintenance

Pega Performance: Improving Application Performance

Graphical user interface, application Description automatically generated

Setting Purpose:

Prepend prconfig/ to the setting purpose and append /default to ensure the dynamic system setting is recognized correctly.

Owning Ruleset:

Set the owning ruleset to one of your application-specific rulesets to maintain proper configuration and versioning.

To implement integration of system of record data for account information in a Pega Customer Service application:

Specialize the Pega Customer Service data pages that use account data to ensure they are tailored to fetch the required data.

Integrate with the system of record to populate an Account data class, ensuring that account information is correctly retrieved and stored.

Create a data transform to map the Account data class to the Pega Customer Service Account class, ensuring that data is correctly transformed and utilized within the Pega application.

ï‚· Test Cases Ruleset Configuration:

If the system cannot save the test definition, it is likely due to a ruleset for storing test cases not being configured. Test cases need to be stored in a specific ruleset that is configured for this purpose.

ï‚· References:

Pega documentation on automated testing and unit test cases emphasizes the need for configuring a ruleset to store test cases.

ï‚· Therefore, the correct answer is:

C. A ruleset to store test cases is not configured.

Identifying and resolving out-of-memory errors in a cluster node involves understanding the alerts that typically precede such conditions.

PEGA0004 – Quantity of data received by database query exceeds limit (Answer A):

Explanation: This alert indicates that a database query is returning more data than expected, which can lead to memory issues as the system tries to handle large data sets.

Define Privilege:

Create a privilege specific to the section containing personal data.

Assign Privilege:

Assign this privilege to roles associated with managers in the HR organization.

The class structure in Pega defines how different case types and sub-cases relate to each other. EventBooking cannot be a subcase of Auto if the business logic does not support such a relationship. Ensuring the correct hierarchy is crucial for maintaining logical and functional consistency in the application.References:

Pega Class Structure Guidelines: Pega Class Structure