Rule Configuration:

Set the availability of the data transform rule to " Blocked " .

Testing with Previous Versions:

This allows you to save and check in the record despite validation errors and lets previous versions of the rule execute during testing.

To ensure the performance of the Pega application does not degrade over time, consider the following recommendations:

Maintain Fragmented Tables: Schedule scripts to regularly maintain and defragment tables that are frequently updated. This helps in optimizing database performance.

Purge and Archive Records: Implement purging and archiving strategies based on the company ' s record retention policy. This practice helps in managing data growth and ensures that the system remains performant over time.

References:

Database Maintenance

Data Archiving

To expose a set of services for your application, with each service exposed as a separate WSDL:

Create a separate service package for each WSDL (Answer A) :

Explanation : Service packages in Pega allow you to group related services and generate WSDL files for them. By creating a separate service package for each WSDL, you can manage and expose each service independently.

 The decision table provided in the question lists rules for segmenting customers based on their credit score and average balance.

 For a customer with a credit score of 240 and an average balance of 35000:

The first rule checks if the credit score is > = 400 and < 600, and average balance > = 30000. This rule doesn ' t apply as the credit score is 240.

The second rule checks if the credit score is > = 200 and < 400, and average balance > = 20000. This rule applies since the credit score is 240 and average balance is 35000.

 According to this rule, the result is " Fair " .

 Therefore, the label returned for a customer with a credit score of 240 and an average balance of 35000 is " Fair " .

Creating a Separate Ruleset:

It is considered best practice to isolate customizations in a separate ruleset to simplify future migrations and upgrades.

Benefits of Separate Ruleset:

Easier to identify and manage customizations.

Simplifies the process of moving custom rules between environments.

Reduces the risk of conflicts during upgrades.

Implementation:

Define a new ruleset specifically for the custom GetNextWork functionality.

Override the necessary rules within this ruleset.

References:

Pega Best Practices Guide

Pega Academy Course on Rule Management and Versioning

 Situational Layer Cake™ Concept : This approach allows for different rules to be applied based on varying contexts like geography, business unit, or product line, without duplicating logic that remains consistent across layers.

 Base Layer for Common UI Rules : Placing the UI rules in the base layer ensures that common interface elements are shared across all divisions, promoting reusability and consistency.

 New Layer for Division-specific Rules : Creating a new layer for the payment rules specific to each division allows customization without affecting other parts of the application. This structure enables the organization to handle division-specific requirements (like different payment methods) efficiently.

 Reference : According to Pega’s best practices for layering, it is advised to place common elements in a shared layer and division-specific elements in their respective layers. This method optimizes rule inheritance and specialization (Pega Platform 8.7 Documentation, Layering and Class Structure).

To help users find rules from the BCO-Data-Quote class when working in APP Studio, follow these steps:

Relevant Records: By selecting each rule you want to reuse as a relevant record, you make these rules available and easily accessible in APP Studio.

Configuration: In the application, configure the data type and select the necessary rules as relevant records, ensuring that these rules are visible and usable in the required contexts.

References:

Using relevant records in App Studio

 Setting pxThread.isWebMashup :

In the pyDefault Data Transform for a case, setting pxThread.isWebMashup to True ensures that App Studio users see the same views displayed by a Mashup interface.

 Associated Privilege Visibility Conditions :

Using associated privilege visibility conditions allows App Studio users to view and configure sections only shown to external personas at design time.

 References :

Pega documentation on Mashup interface development in App Studio outlines these practices to ensure seamless integration and development.

 Therefore, the correct answers are:

B. In the pyDefault Data Transform for a case, set pxThread.isWebMashup to True by using an Application Setting. App Studio users then see the same views that are displayed by a Mashup interface when it is configured to use the Create a case option.

C. Use associated privilege visibility conditions. At design time, an App Studio user is able to view and configure sections that are only shown to external personas.

Text, letter Description automatically generated

To meet the requirement that only the work group manager can read and write purchase request cases when the total amount exceeds USD 10,000, the following configurations can be used:

Reads Access Control Policy : Use a reads access control policy with a condition that checks if the amount is less than USD 10,000. This restricts access based on the purchase request amount.

Conditional Access in Access Manager : Configure conditional access in Access Manager to allow read and write permissions for purchase request cases only when the amount is less than USD 10,000. References:

Pega Documentation on Access Control Policies: Access Control Policies

Pega Access Manager: Access Manager