Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Defining an alias for a group of actions

Updated on January 22, 2021

By default, Pega Customer Decision Hub for Communications uses the term actions to refer to the engagement messages. If needed, you can change this to a more appropriate term, such as Promotions or Nudges.

To change the terminology, edit the business hierarchy in the Next-Best-Action designer.

Tip: You can use different terms for actions based on the business issue and group to which the product belongs. For example, if your business structure includes a Loans group within the Retention issue, you can rename actions related to that issue and group to Loan Loyalty Program. For other issues and groups, you may use other, group-specific terms, or keep the default name.
  1. In the Taxonomy tab of the Next-Best-Action designer, edit a business group.
  2. In the Action naming (singular) field, enter the singular form of the name which will be given to actions from this group, for example, Promotion.
  3. In the Action naming (plural) field, enter the singular form of the name which will be given to actions from this group, for example, Promotions.
Result: For the selected business group, the terms Promotion and Promotions are now used for actions. For other groups, the default terms are still used. If required, you can edit the other groups and specify a different alias.
  • Previous topic Adding business issues and groups
  • Next topic Configuring the maximum duration setting for Pega Next-Best-Action Advisor

Tags

Pega Customer Decision Hub for Communications 8.5

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us