Instantly download PEGACSSA72V1 training test engine

You are configuring duplicate case search logic in a case type. How do you ensure that resolved cases are not evaluated as potential duplicates?

• A. Add a weighted condition that evaluates the work status of current and existing cases where work status equals "Resolved" and has a weight of "0".
• B. Add a must match condition where the work status of the current case does not contain "Resolved".
• C. Add a must match condition where the work status of potential duplicates does not contain "Resolved".
• D. Add a weighted condition where the work status of potential duplicates does not contain "Resolved".

You are configuring a screen flow as shown below:

• A. Select the Enable navigation link and Only allow navigating back to this step options for both steps four and five.
• B. Select the Enable navigation link option for step four, and the Only allow navigating back to this step option for step five.
• C. Select the Enable navigation link option for both steps, and the Only allow navigating back to this step option for step four.
• D. Select the Enable navigation link option for both steps, and the Only allow navigating back to this step option for step five.

During the development of your application, you created operators for testing purposes. You are preparing to migrate the application to another environment. You do not want to include the operators in the archive file.
Which two options exclude the operators? (Choose Two)

• A. Before you run the Application Packaging wizard, save the operators to an organization ruleset. Select the Exclude non-versioned rules check box in the Product rule.
• B. In the Operators step in the Application Packaging Wizard, clear the check boxes next to the operator names. In the Product rule, clear the Include associated data items check box.
• C. In the Operators step in the Application Packaging wizard, clear the check boxes next to the operator names. In the Product rule, clear the Include data types check box.
• D. Before you run the Application Packaging wizard, remove the associated ruleset from the operator records.

Users create Insurance Coverage Requests cases to authorize insurance payments. Users enter information that includes the name of the patient, the date of the procedure, and the type of procedure. After entering the information, users submit the request for a review of the patient's insurance policy. Because multiple users enter requests, duplicate requests can occur. A request is considered a duplicate if the patient name, procedure type, and procedure date match an existing request. You have been given two requirements:
*Ensure that users can identify duplicate requests.
*If a case is a duplicate, it is not written to the database. Otherwise, write the case to the database.
Which two steps satisfy the requirement that only nonduplicate requests are written to the database? (Choose Two)

• A. Add a Persist Case step to the case lifecycle design.
• B. Add a Persist Case flow action to case lifecycle design
• C. Configure the case type to instantiate temporary cases.
• D. Configure a Create Case step to instantiate temporary cases.

You are working on an update to an application which only affects some rules for a certain case type. The customer has requested that a patch update be released. How do you create the new ruleset version?

• A. Use the Ruleset Maintenance wizard to merge the existing rules in the relevant rulesets to the new version.
• B. Use the Lock & Roll functionality to lock the current ruleset and increment the ruleset version.
• C. Create a branched ruleset, then copy the affected rules into the new branched ruleset.
• D. Use the Ruleset Maintenance wizard to skim the relevant rulesets to copy the highest version of existing rules to the new version.