This section contains information for administrators.
- Service and data health limits for Pega Customer Decision Hub on Pega Cloud
Pega Customer Decision Hub deployed in Pega Cloud has limits in place that constrain certain elements of the service and its use to ensure high quality of service for your team.
- Adding new response outcomes
You can add new, customized response outcomes of customer interactions by configuring the Contact policy and Update Status shape in action flows.
- Pega Customer Decision Hub Interaction History data model
Pega Customer Decision Hub stores all customer responses to specific actions in Interaction History database tables. The recorded interactions can then be used to train adaptive models through delayed learning, or to create business intelligence reports.
- Exporting interactions and decision results
Export interactions and decision results in real time to a file repository by using the export infrastructure that Pega Customer Decision Hub provides out of the box. You can analyze the exported interactions in business intelligence (BI) tools to gain insights, and audit exported decision results to meet contractual requirements.
- Pega Customer Decision Hub dynamic system settings
Pega Customer Decision Hub uses dynamic system settings to manage various configurable items. Most of these settings are owned by the PegaMKT-Engine and PegaMKT-Install rulesets. In addition, some settings are owned by the PegaMKT-Install, PegaMKT-Portal, and PegaMKT-PushNotification rulesets. Administrators can edit these settings to modify the behavior of various elements.
- Pega Customer Decision Hub access roles and privileges
Pega Customer Decision Hub uses access privileges to manage various access rights for operators. As an administrator, you can add or remove privileges to or from access roles to manage the access rights for various access groups in your application.
- Disabling the Decision Data Store as action state storage on Pega Cloud
New deployments of Pega Customer Decision Hub on Pega Cloud services are configured to use the Decision Data Store (DDS) to store action state. The DDS data sets manage large and active data from different sources and make it available for real-time and batch processing.
- Pega Customer Decision Hub agents
On top of the standard Pega Platform agents, exist a set of agents that manage the different aspects of Pega Customer Decision Hub. Review and monitor these agents on a regular basis to ensure that your application is running optimally. In the event of a failure in any of the agents, understanding the agent's role helps to assess the impact of the failure on the application.
- Managing Decision Data rules in Pega Customer Decision Hub
Pega Customer Decision Hub uses Decision Data rules as the backing of several types of artifacts, such as treatments, Next-Best-Action taxonomy or Context Dictionary definitions, and others. You can view, manage, and define these Decision Data rules directly in the Pega Customer Decision Hub portal.
- Creating and Configuring a Supporting Decision
Perform the following steps to create and configure a supporting decision:
- Using a Configuration Modal Window
The configuration modal window is utilized in multiple places within Pega Customer Decision Hub. This appendix outlines the components of a configuration window and how to use the window to select items.
- Application configuration
This appendix outlines the various configuration options that are available for the administrator to configure the application. These settings should be configured as part of setting up the application and can be adjusted later, as the need arises.
- Pega Community Wiki
Learn more out-of-the-box capabilities and ways to address common design patterns of Pega Platform and Applications such as Pega Customer Decision Hub on the Pega Community Wiki.