Skip to main content
LinkedIn
Copied!

Table of Contents

Interaction History component processes data longer than expected

Version:

Only available versions of this content are shown in the dropdown

The Interaction History component in a strategy takes more time to process data than expected.

Cause

This behavior can be caused by one or more of the following conditions:

  • The FACT database table contains an excessive number of records. As the transactional data in this table grows, processing time slows down.
  • The database that stores interaction history records is not optimized for quick retrieval of data.

Perform one of the following steps to increase the speed with which the Interaction History component processes data:

Solution

  • Use the pxOutcomeTime property to archive old FACT records.

    You can archive all FACT records that are older than 31 days if your decision logic indicates that insurance policies become invalid after one month. For more information, see Applying sample scripts for archiving and purging.
  • Improve the data retrieval from the data set that contains the interaction history:

    1. Retrieve the interaction history SQL queries so that you can analyze their format and estimate the processing time. For more information, see Starting a database trace.

    2. Based on the retrieved queries, create a database index on only the problematic columns to quickly locate data without having to search every row in a database when that database is accessed.

Related Content

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us