Skip to main content


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

Materializing interaction history summaries

Updated on December 20, 2021

This content applies only to On-premises and Client-managed cloud environments

Pega Customer Decision Hub 8.6 adds new interaction history summaries, which are shipped without preaggregated data. To save processing time, turn on preaggregation for each interaction history summary by materializing them.

Preaggregated data sets save processing time because they include the latest interactions. Data sets that are not preaggregated do not include the latest interactions and therefore they query the database.

Pega Customer Decision Hub Update Guide
Before you begin: If you use an Oracle database for interaction history, update the column definitions for DateTime properties to use the TIMESTAMP datatype instead of the DATE datatype. For more information, see Modifying column definitions to use the TIMESTAMP data type in an Oracle database.
  1. Log in as an operator with access to the Summaries landing page.
    Access to the Summaries landing page is limited to users whose access group includes the CustomerDecisionHub:DataAdmin user role. For more information, see Granting access to the Data menu, data flows, and interaction history summaries.
  2. In App Studio, click DataSummaries.
  3. On the Summaries landing page, find the data set for which you want to turn on preaggregation, and click MoreMaterialized.
  • Previous topic Modifying column definitions to use the TIMESTAMP data type in an Oracle database
  • Next topic Removing withdrawn data sets from interaction history summaries

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