PEGAPCDC87V1 Exam Dumps : Certified Pega Decisioning Consultant (PCDC) 87V1

 Understanding the Context: Myco, a telco, wants to introduce new plans without handsets. Currently, their business structure under the sales issue/plans group contains actions that are handsets.

 Business Structure: In Pega Customer Decision Hub, the business structure is organized into issues and groups.

 Action Naming: To reflect the new situation where plans do not include handsets, the term "handsets" needs to be changed.

 Level of Change: The appropriate level for renaming the plans to reflect this new structure is at the Issue level. At this level, the business context for actions is defined, and changes here will apply to all actions under that issue.

 Reference: As per the documentation, changes to business issues and groups should be done at the issue level to ensure that the new context is accurately represented across all relevant actions​​.

To limit the number of emails sent to customers irrespective of past outcomes with a particular offer and customer, you can implement customer contact limits. Customer contact limits are used to control the number of interactions a customer can receive over a specific period on a particular channel, ensuring that customers are not overwhelmed with too many messages.

Aggregation components in Pega Customer Decision Hub provide the ability to make calculations based upon a list of actions. These components are used to perform operations such as summing values, averaging scores, or other statistical calculations that aggregate data from multiple actions. This is crucial for generating insights and making informed decisions based on the collective data of several actions.