Understanding configuration errors and warnings
The following table explains the scenarios that contribute to the Configuration Errors and Configuration Warnings lists.
Pega Customer Decision Hub
| Failure Scenario | Use Source link to… |
| Public Link URL is not specified. | Open the Resource URLs landing page. Administrators should set this URL if their application utilizes the Email channel. |
| The required mapping License Key for Google Maps is not specified. | N/A |
| The specified default destination ruleset version is locked. | Open the access group. Administrators should update instance to reference an unlocked ruleset version. |
| The selected customer Email property used to determine the recipient's email address does not have external mapping. | Open the Customer class defined on the Application Settings page. |
| The selected prospect Email property used to determine the recipient's email address does not have external mapping. | Open the Prospect class defined on the Application Settings page. |
| Outbound Default Data Source is not configured or doesn’t exist in the system | Open the Configuration Settings landing page tab. Administrators should update the settings to point to a valid data source. |
| The Outbound Default Data Source fails to connect. | N/A |
| The default destination ruleset for an access group is not specified. | Open the access group. Administrators should set the Default destination ruleset to their application’s artifacts ruleset. |
| The default destination ruleset for an access group is not locked and no open versions exist for the ruleset. | Open the ruleset. Administrators should add a new unlocked version and update the access group to reference this new version. |
Previous topic Understanding channel errors and warnings Next topic Understanding runtime errors and warnings