Pegasystems PEGACPLSA88V1 Exam With Confidence Using Practice Dumps

Configure Authentication Activity:

Go to Records Explorer > Security > Activities.

Create or configure the authentication activity to map the authenticated user to the operator ID in Pega.

LDAP Attributes Mapping:

Go to Designer Studio > Security > Authentication Service.

Configure the LDAP attributes to map to Pega operator properties, ensuring that attributes like cn, sn, mail, etc., are correctly mapped.

Validation:

Test the Single Sign-On (SSO) setup to ensure the authentication and attribute mappings work correctly.

Verify that users can log in using SSO and their LDAP attributes are correctly reflected in Pega.

References:

Pega Academy: Single Sign-On Configuration.

Pega Documentation: LDAP and SSO Configuration.

To create custom workspaces for different user roles and display custom formatted properties:

Separate Portals and Harnesses: Define separate portals, harnesses, and sections for each access group (managers and customer service representatives). This approach allows you to tailor the user interface and functionality according to the specific needs of each role.

Specialty Components and XML: Use Specialty Components to create custom formats for properties. XML can be used to pass data in and out of these components, allowing for complex and specialized data handling.

References: Pega Platform documentation on portals, harnesses, and using Specialty Components with XML.

 Extending Core Pega Classes:

Extending existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal ensures that the application adheres to standard Pega data models.

Persisting instances of these extended classes in the PegaData schema aligns with best practices for data persistence and reuse.

 References:

Pega Lead System Architect documentation on data modeling recommends extending core Pega classes to maintain consistency and leverage built-in functionalities.

 Therefore, the correct answer is:

A. Extend existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal, persisting instances of the extended classes in the PegaData schema.