PEGAPCLSA85V1 Lead System Architect (LSA) Pega Architecture Exam 85V1 Questions and Answers

As a final rule

As a case level property

As an enterprise class level property

As a relevant record

Look for the assignment to perform.

If not found, look for other assignment in flows on this case

If not found, look for assignment in flows on the parent case

For each also consider assignments in workbaskets

Define two subreports: one that counts rows in Table B relative to Table A, and on that counts the rows in table C relative to Table A. Only include rows in the main. Report against table A where the table B count is greater that the Table C count.

Join table A to Table B and C using include all rows in this class. Count the Join column from both Table B and Table C. Only include rows where the first count is greater than the second.

Join table A to Table B and C using include all rows in join class. Count the Join column from both Table B and Table C. Only include rows where the first count is greater than the second.

Define two subreports, one where table B users ''Do not Join'', and one where Table C users ''Do not Join'', In the main report count the rows from each subpreport, then only include rows where the count from the Table B subreport than the count from the Table C subreport.

Prior to the first assignment in the ApproveRuleCheckin flow, add a decision shape where one output connector is equivalent to the submitting the SendBack flow action.

Implement a CheckForCustomWarnings activity for each rule included in the requirement. The activity issues a warning whenever the requirement's history tab criteria are not met.

Override the FindReviewers decision tree to invoke a when rule that evaluates the criteria, if the when rule returns true, the decision tree returns SendBack.

Override the SendBack Flow Action adding a pre-ctivity that transfers the assignment to the create operator if the rule's criteria are not met.

Ability to be circumstanced

Ability to be parameterized

Ability to be called directly from a decision table

Ability to be versioned

Use a visible when rule for the properties displaying sensitive information.

Create an access control policy restricting access to the sensitive information.

Configure an access deny rule restricting access to the sensitive information.

Move sensitive information to separate sections and apply a privilege to the sections.

Specialize the data model as little as possible.

Redefine the data model.

Hide the data model with a custom data model.

Hide the data model with an Enterprise service Bus (ESB) dictated data model.

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.

Configure an agent to record monthly case status in a separate table and report on that table.

Configure an activity to generate the data in the clipboard and report using a custom section.

Configure a summary report that leverages sub reports for each month.

Configure a Declare index to record case data to a separate table.

To prevent the browser to load content from untrusted sources

To restrict what data a user can view in a case the user can open

To define security for case attachments

To configure security for the content management integration