You need to create custom workspaces for the manager and for the Customer service representative (CSR), Also, you are asked to display some properties in custom formats that arc not supported by Pega.
Which approach satisfies these requirements?

• A.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.
• B.Create different harnesses for each user's workspace. New portal rules are not needed. Define Specialty Components and use JSON to pass data.
• C.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.
• D.Each access group can use separate portals, harnesses, and sections. Use Specialty Components and use XML to pass data.

Comment: *

Name: *

Email: *

Verification: *

XYZ Corporation wants to ensure that every attempt by a developer to check a rule into a certain ruleset version is reviewed before that rule is allowed to be checked in. The rule should be automatically sent back to the developer without being checked in if all warnings are not justified and the fields on the history tab are not complete.
How do you address this requirement?

• A.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.
• B.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.
• C.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.
• D.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.

Comment: *

Name: *

Email: *

Verification: *