Skip to main content

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

Configuring the Context

Updated on May 20, 2020

In this task, editing the context of the entities and their associated data is explained. Using multiple data contexts allows you to better target your marketing efforts at multiple levels, e.g. across account level, customer level and household level. These are common levels in both the FS and Comms industry.


Task IDTask-040504
Primary roleSenior System Architect
Secondary roleSenior Decisioning Architect
Tertiary roleN/A

Use App Studio > Settings > Context Dictionary to review or update the default contexts, configure a different primary context, or add an additional customer context.

The Context Dictionary identifies the customer entities, the relationships between these entities, and any associated data to be used by Customer Decision Hub. By default, the primary context is Customer, mapped to the <your organization name>-Data-Customer class, and the prospect context is Prospect, mapped to the <your organization name>-Data-Customer-Prospect class. Additionally, the Account context is mapped to <your organization name>-Data-Customer.

To support adding associations to the context dictionary, you will need to create the Association rule for your two related classes. An example of an Account association rule is shown below:



The Class join type in most cases must be specified as “Include all rows in…”


In the conditions you should specify primary and foreign keys for the parent and child classes appropriately.

After defining your association rules, follow these steps to add the association to your context dictionary.

  1. In the App Studio navigation panel, click Settings Context Dictionary.
  2. Review the primary context.
    1. Click the Configure icon by the name of a context.
    2. Review the available properties.
    3. If you defined a new extended customer class, select it in the Class field.
    4. Review the associated data. If you defined additional associated data for your base customer class, click + Add associated data to enable it.
  3. Optional: To add a new customer context, click Add context and specify the name, customer class, and optional exclusion list. If you defined additional associated data for your new customer class, click + Add associated data to enable it.
  1. Optional: To set your new customer context as the primary Context, click Change primary and select the context in the Select Primary Context dialog box.


CAUTION: Changing the primary context affects all artefacts which use it, including decision strategies and outbound artefacts. If you have already defined these artefacts, please be sure to re-point each of them separately to the right level in the context hierarchy again. 

  1. Optional: Click the Configure icon by the name of the prospect context. If you defined a new extended prospect class, select it in the Class field.
  2. Optional: Change the context storage in the Context storage section.

By default, the data resides in a relational database supported by Pega Platform in the form of a database table. If you plan to use segmentation, all data must be synchronized between the decision datastore and relational tables.

  1. Click Save.

For more details here, refer to the  Configuring your Customer Class chapter of the Customer Decision Hub Implementation Guide.


Typical FS Contexts




A new feature introduced is the association of NBA Designer categories to attributes. This feature allows you to bring categories up in the NBA Designer UI, by selecting the right associated category (displayed below, on the Relevant Records page).


Associate to NBAD Category


Once you configured your Context Dictionary, you can use your customer data available for NBA interaction across the defined levels of the context hierarchy.


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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us