Skip to main content


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

Issue: Data sets that need to be reset

Updated on August 4, 2022

Use the following troubleshooting tips to help solve issues with data sets that need to be reset.

Pega Customer Decision Hub

Cause: There is a data left in customer journey data set

To reset journey data, three data sets must be truncated. This is an all-or-nothing process, because leaving data in any data set will result in corrupted data for the customer journey feature.

Important: There is no possibility to remove specific journey data from the data sets. Removing any journey data requires removing ALL journey data.

The three data sets that you must reset are:

LastInteraction
Stores the information for the stages that a customer has interacted with, but does not store customer information. This data set is used to populate the nodes in the Journey Visualizer.
SequenceOfInteractions
Stores the connections between the stages of the journeys that the customers have moved through, but does not store customer information. This data set is used to populate the links between nodes in the Journey Visualizer.
JourneyStages
Stores a record for each journey stage with which a customer recorded an interaction.

Solution: Truncate the data sets

    Reset a data set by performing the following steps:

  1. Click Actions in the toolbar and select Run.
  2. In the Operation drop-down menu, select Truncate, and then click Run.
  • Previous topic Issue: Customer journey results may not be appearing as expected in the Journey Visualizer
  • Next topic Issue: The same stage is being output for each interaction

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