PEGACPLSA88V1 Exam Dumps : Certified Pega Lead System Architect (CPLSA) Exam 8.8

A System Architect should create a When rule in Dev Studio and reference the ClaimBenefit Clipboard page on the Pages it Classes tab. They define and implement the required criteria, because it is not possible to make it available for Citizen Developers.

A System Architect should create a property BenefitType in the work class and copies the BenefitType property value from the ClaimBenefit Clipboard page to pyWorkPage. Citizen Developers can check the criteria on work class BenefitType property.

A Citizen Developer uses any existing property and informs the system architect to implement a constraint rule. The System Architect marks the constraint rule as a relevant record, to make it visible to the Citizen Developer.

A System Architect should create a When rule in Dev Studio and reference the ClaimBenefit Clipboard page on the Pages file Classes tab. They mark the rule as a relevant record so that the rule becomes available to Citizen Developers.

Define case type views using *\ page, property" syntax for the majority of the- fields.

Drag-and-drop a Field Group when defining a case view.

Create a data type that corresponds to each case type.

Pre-define properties, sections, and relevant records that are applied to Work-Cover'.

Add an embedded Page property to the case type.

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

Extend existing core Pega Platform classes such as PegaData-Contact, PegaData-Organization, and PegaData-Address, persisting instances of the extended classes in the CustomerData schema.

Create the minimum number of properties necessary to describe a person, organization, and address within the ORG-Data class. Share the ORG ruleset with other applications.

Define new Person, Organization, and Address Data classes that extend ORG-Data. Persist Person in the PegaData schema, and Organization and Address in the CustomerData schema.