Skip to main content


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

Using data sources

Updated on January 29, 2021

Pega Customer Service uses data source rules extensively throughout the system. Data sources are used to abstract class, clipboard references, and other parameters to simplify the configuration.

Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide

Adding data sources

A new data source rule is required if you create a new data type and want to use the related fields in the application, such as for interaction driver tasks and suggestions, composite displays, data references within dialog scripts, and portal search data retrieval and display.

  1. In the navigation pane of Dev Studio, click RecordsDataCustomer Service Datasource.
  2. Create a new data source. For more information about creating a new data source, see Data Set rules - Completing the Create, Save As, or Specialization form.
    After creating a data source, complete the fields described in the following steps to save the instance to your ruleset.
  3. In the Detail tab enter the following details.
    1. Click the Source list and select one of the following from the list.
      • Clipboard Page to specify the associated Page, Class, and related Property fields information required for this data source (see associated fields below).
      • Data Page to refresh the rule form and display the Data Page field (Smart Prompt) to specify the desired data page rule for this data source.
    2. Click the Page field and enter the name of the clipboard page to use for this data source.
    3. Click the Class field and enter the class of the clipboard page given in the Page field.
    4. Enter .pxResults in the Property field, if you selected List in the Type field.
    5. Enter the class of the .pxResults list in the Property class field, if you selected List in the Type field.
    6. Click the Type list and select an option.
    7. To indicate that the data source can be used for data references within dialog scripts, select the Dialog data source check box.
      This field is evaluated to populate the data source selection field when configuring dialog scripts using the Configuration Tools wizard.
    8. To indicate that the data source can be used for data references within Chat phrases, select the Phrase Data Source check box.
      Properties defined in this data source are available in the Configure Phrases capability in the Manager Tools page (requires the PegaCA:Manager role).
    9. To indicate that the data source can be used as a security question during customer verification, select the Enable for verification check box.
      This field is evaluated to populate the Source field when configuring Customer verification in App Studio. For more information about customer verification, see Omni-channel features.
    10. Click the Default interaction container field and specify the name of the class to use as the default interaction class when a user selects a result from the portal search results list.
    11. Click the Interaction Flow field and specify the name of the interaction flow that describes the starting flow to launch a Research interaction.
  4. In the Properties tab, enter the appropriate value in the Property field.
    Properties included on this tab are used to populate the list of available fields that users can insert into dialog scripts using the Configuration Tools wizard. These properties are made available wherever the data source is referenced, such as dialog scripts and chat phrases.
  5. In the Search tab, enter the following details.
    1. Select the Use in portal search? check box to indicate that this data source should be searched as part of a portal search.
    2. Select the integration activity to use to perform the search operation in the Search activity field.

Editing data source rules

You can personalize and edit the dialogs and common phrases for the data source rules and their related fields during a customer interaction.

  1. In the navigation panel of App Studio, click Data > Data objects and integrations to view the list of current data types in your application.
  2. Click a data type that you want to edit.
    For example: Account
  3. Click the Settings tab.
  4. Click Data source options.
  5. In the Data source options drop-down list, click the data source rule for which you want to personalized and edit the dialogs and common phrases.
    For example:
  6. To edit the associated fields, such as dialogs, common phrases, and customer verification, of a data source, select the data source from the Select the data source category list.
  7. In the Enable the following fields to be referenced in section, specify whether you want the fields listed on this page to be available for use in dialog, common phrases, customer verification, or all by selecting the following check boxes.
    • Select Dialog if you want to display the fields listed in this page to be used as dialog.
    • Select Common phrases if you want to display the fields listed in this page to be used as common phrases.
      Note: The data source rules that are configured specifically for dialog cannot be used for common phrases. For such data types, the common phrases check box is unavailable.
    • Select Enable for verification if you want to populate the data source value in the Source field when configuring Customer verification in App Studio. For more information about customer verification, see Omni-channel features.
  8. To remove a pre-configured field from the list of fields that you want to make available when you are editing common phrases or dialogs, click the Delete icon to remove a field.
  9. To add a field, click Add new and select a field name from the list.
  10. Click Save.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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