Certified Lead System Architect (CLSA) PEGAPCLSA86V2 Updated Exam

add a data transform to the pyCaseManagementDefault work parties rule

Ensure the addparty user action is available as a local action

add the addworkObjectparty activity to the assigments

select the VOE? option on the pyCaseManagementDefault work parties rule

Case-specific rulesets make it easier to rebase ruleset versions.

Each branch ruleset can be associated to case-specific user stories.

The ruleset can be added to the ruleset stack for multiple applications.

The case type might be converted to a component application in the future.

Use the optimistic locking option on the case types.

Create a Registration subcase configured to run in offline mode.

Leverage the default object lock contention requeuing capability.

Override DetermineLockString to use .AccountID instead of .pyID as the lock string.

Each access group can use separate portals, harnesses, and sections. Use Specialty Components and use XML to pass data.

Level age the Case Manager and Case Worker as reference points to create new portals, if required. Use Special Components and use JSON to pass data.

Create different harnesses for each user's workspace. New portal rules are not needed. Define Specialty Components and use JSON to pass data.

Identify the functionality required for each portal. Customize the portal either by modifying the section or harness. Use Specialty Components and use XML to pass data.