* Next-Best-Action Framework - This framework in Pega CDH is designed to decide the best action for each customer interaction by evaluating eligibility, suitability, and propensity.
* Complex Eligibility Criteria - To define complex eligibility criteria, modifications are needed within the Next-Best-Action decision strategy to handle multiple conditions and business rules.
* Steps:
* Access the Next-Best-Action Designer.
* Navigate to the decision strategy.
* Add or modify components to incorporate complex eligibility conditions.
* Test and validate the changes using persona tests and simulations.

To update the underlying decision strategy of an engagement policy condition, the change request should be created in the 1:1 Operations Manager Portal. This portal is designed for business users to manage changes and revisions in a controlled environment.
* Understanding the Portals:
* 1:1 Operations Manager Portal: This portal allows business users to manage and implement business changes, such as updating decision strategies and engagement policies.
* Pega Customer Decision Hub Portal: This portal is used for overall customer decision management but not specifically for creating change requests.
* Dev Studio Portal: This portal is more technical and used for developing and configuring applications.
* Development Manager Portal: This is generally used for deployment and managing development pipelines.
* Steps to Create a Change Request:
* Step 1: Log into the 1:1 Operations Manager Portal.
* Step 2: Navigate to the section where you can create a new change request.
* Step 3: Specify the details of the change request, including the engagement policy and the decision strategy that needs to be updated.
* Step 4: Submit the change request for approval and implementation.
* Benefits:
* Using the 1:1 Operations Manager Portal ensures that changes are tracked, reviewed, and approved through a formal process, maintaining governance and control over business operations.
* Example:
* U+ Bank wants to update the decision strategy for credit card offers. A change request is created in the 1:1 Operations Manager Portal, detailing the required updates to the engagement policy conditions.
References:
* Pega-Customer-Decision-Hub-User-Guide-85.pdf: "Managing business-as-usual changes with Pega 1:1 Operations Manager" section.
* Pega documentation on "Revision management and change request process".

To present offers from both groups and arbitrate across the two groups to select the best offer based on customer behavior, you need to map a real-time container to the Top-level or Issue-level in the Next-Best-Action Designer. This mapping allows the system to evaluate and arbitrate offers from different groups based on the defined criteria and customer behavior, ensuring the most relevant offers are presented.

* Set-Property Component: This component performs the calculation of profit for each of the four brands (Nike, Adidas, Puma, Reebok). Since the Set-Property component is configured to calculate profit for each brand individually, it processes four inputs, resulting in four outputs.

* Scorecard Rule - A scorecard in Pega is used to calculate a score based on various customer attributes.
To include a new attribute (customer income), the scorecard rule must be updated.
* Steps to Update Scorecard:
* Navigate to the scorecard rule in Dev Studio.
* Add a new input for customer income.
* Define the scoring logic for the new input.
* Save the updated scorecard.
* Decision Strategy - The decision strategy that uses this scorecard must also be updated to ensure it correctly utilizes the new score calculations.
* Steps to Update Decision Strategy:
* Locate the decision strategy in the Next-Best-Action Designer.
* Ensure the updated scorecard is referenced correctly.
* Adjust any logic or thresholds that depend on the scorecard output.
* Test the strategy to ensure it works as expected with the updated scorecard.