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.
The Application landing page is available only to administrators with access to App Studio, and lists various configuration options. This landing page is accessible in App Studio via.
To change any of these settings, click the Edit button on the particular setting's landing page. In edit mode, click Save to save and apply your changes to the settings; or click Cancel to discard your changes.
This landing page contains settings pertaining to the overall execution infrastructure.
|Outbound Default Data Source||Displays the database instance where the customer table resides and where the application will store execution data (such as data pertaining to Segment and Campaign execution).|
|Outbound DB Preview File Size||Displays the number of records displayed in the preview file when previewing the contents of the data written for a Database Template.|
|Batch Size||Displays the size (number of records) into which back-end processing is batched, in order to leverage performance improvements from vertical and horizontal scalability.|
|Delete Campaign Run data older than X days||Displays the threshold (in number of days) for purging Campaign execution data. This only applies to data for Campaign Runs where all actions are complete.|
|Output File Date Format||Displays the default format to be applied to date fields in a File Template.|
|Global Exclusion List Segment||Displays the Segment that represents the global exclusion list. Customers in
this list will be excluded from outbound communication. When no value is specified,
the exclusion list feature is disabled.|
|Use Simulation Data||Specifies whether Dashboard widgets should use simulated data. Enable this setting to review the Dashboard and its capabilities in the absence of real data.|
|Use Decision Data Source|
Specifies whether a decision data store (such as Cassandra) should be utilized to retrieve any customer-centric data which is not required for segmentation.
Using decision data sources requires the configuration of a DNode in your system. Review the Pega 7 DNode Cluster Management landing page help topic for details.
This landing page contains settings pertaining to the behavior and display of artifacts.
|Disable campaign action validation||Specifies whether Campaigns should validate the existence of Action rules utilized by the Campaign Strategy .|
|Require key codes||Specifies whether key code entry is required for artifacts (such as campaigns, actions, and treatments). If this setting is enabled, it will over-ride the user preference for specifying key codes.|
|Number of runs to schedule at a time for open-ended campaigns||Displays the number of Campaign Runs that the system will schedule at a time for open-ended Campaigns (i.e. those Campaigns where an end date is not set).|
|Campaign contacts edit mode||Determines the mode to use when managing contacts in Field Campaigns. This setting is only visible if the application includes Pega Field Marketing.|
|Default Response Page||Displays the Rule-HTML-Section rule that will be used as the default response page for Email responses.|
|Default Action Expired Page||Displays the Rule-HTML-Section rule that will be used as the default page for Email responses to expired actions.|
|Default Action Not Available Page||Displays the Rule-HTML-Section rule that will be used as the default page for Email responses to actions that are no longer available.|
|Mapping License Key||Displays the license key to use for the Google Maps mapping service.|
|Default Customer Location Properties||Displays the properties on the customer class to be used as the defaults for the customer’s location (latitude and longitude) when filtering on Geofences in Strategies.|Previous topic Using a Configuration Modal Window Next topic Pega Community Wiki