Edit each group and define eligibility, relevancy, and suitability conditions for actions associated with this group.
Engagement policies specify the conditions under which an action or group of actions is eligible for a customer. For more information, see Understanding Next-Best-Action Designer engagement policies.
If you have configured a multi-level Context Dictionary, you will see a separate engagement policy section for each context. Each context section allows you to define conditions using that context level and above.
For example, if your Context Dictionary structure is Accounts > Subscribers, the Subscribers engagement policy section allows you to use criteria from both the Subscriber and Accounts entities. There is also an All Actions section, where only top-level criteria are available. The criteria specified in the All Actions section are applied to all actions in the group, regardless of the context of the action.
- In the Pega Customer Decision Hub portal, click .
- On the Engagement policy tab, click the name of a group, or click All groups to define an engagement policy that applies across all groups in your business structure.
- Click Edit.
- Expand the Eligibility, Applicability or Suitability section.
- In the first column, select a field, a strategy, or a when condition from the list.
Note: To make a property, To make a property, when rule, or strategy available for use as an eligibility condition, define it as a Relevant Record for your primary context class, which by default is your Customer class, or for its the parent or child classes.
- In the second column, select a comparator from the list. For strategies, the comparator is always has results for.
- In the third column, select as needed:
- For field conditions, enter a value in the field or select a field by clicking Select values. The system compares the value of this field to the value of the corresponding field or condition in the first column. For example, Status work is equal to Done.
- For strategies, select the required component. The system determines whether there exist strategy results for that component.
- When conditions do not have a third column, because their comparator can only be true or false.
- To specify additional conditions and define the relationships between them, do the
- Click Add a row and add as many conditions as required.
- Use the drop-down lists between each pair of conditions to specify how these conditions relate to each other. You can group conditions with AND or OR operators.
- Use the drop-down list in the upper right corner to specify how condition groupings
should be evaluated.
- Group ANDs - Select this option if you want conditions linked with the AND operator to be evaluated as a group, and conditions linked with the OR operator to be evaluated individually. With this grouping, the grouping of condition 1 AND condition 2 OR condition 3 OR condition 4 is evaluated as (1 AND 2) OR 3 OR 4. That is, either conditions 1 and 2 must both be true, or either one of conditions 3 and 4 must be true.
- Group ORs - Select this option if you want conditions linked with the OR operator to be evaluated as a group, and conditions linked with the AND operator to be evaluated individually. With this grouping, the grouping of condition 1 AND condition 2 OR condition 3 OR condition 4 is evaluated as 1 AND (2 OR 3 OR 4). That is, both condition 1 and one of conditions 2, 3, and 4 must be true.
- Use advanced logic - Select this option if you want to
define a mix of grouping by the AND and OR operator. Use the Logic
string field to specify the condition grouping.
If you change a condition that uses advanced logic back to Group ANDs or Group ORs, all the groupings that you previously defined are reset.
- To save the condition for future reuse, click .The Save to library option is not available if the conditions include either Strategy rules or When conditions with parameters. The option is also disabled for eligibility conditions which include default criteria created with the Use advanced logic option.
- Click Save.
- To test the behavior of each component of the engagement policy, you can run audience simulations and persona tests. For more information, see Simulating Next-Best-Action configuration changes.