CDH Impact Analyzer is not working with Live data in pega CDH 24

General
1

Dear Team,

We have enabled CDH Impact Analyzer option in non-prod environment, this is not working with Live data option enablement however its working with demo test data files upload approach. We are not using the OOB interaction history table as configured the separate interaction history table as aper application requirement. Kindly let us know how to make this option works with Live data.

2

I found the following explanation in our documentation:

Discovery Tool

Impact Analyzer

** This answer was generated via an AI search - verify against available docs **

There are different possible solutions. Please verify as the issue could be related to several potential factors:

  1. Configuration Issues: There are specific DSS (Dynamic System Settings) that control Impact Analyzer behavior, particularly around data sources.
  2. Interaction History Configuration: The system relies on proper interaction history configuration, and custom IH tables may require additional setup.
  3. VBD Actuals Synchronization: Impact Analyzer depends on VBD (Visual Business Director) Actuals data, which needs to be properly synchronized with your interaction history.

The root cause is that the Real-time Data Grid (RTDG), which powers Live data analysis, is populated via IH Summaries, and those summaries need to be explicitly redirected to your custom RDBMS table rather than the default stream/file repository.

Here’s what needs to be done:

Step 1 — Reconfigure IH Summaries to read from your custom table

1.1 Enable IH Database Writing
Ensure the following DSS is set to True:

  • Setting: interactionHistory/writeToIH

  • Ruleset: Pega-DecisionEngine

1.2 Set the Aggregation Method
Set the following prconfig entry to CASSANDRA:

  • Setting: prconfig/ih/aggregates/last_customer_update_method/default

  • Ruleset: Pega-Engine

This controls how the system manages the last-record timestamp for customer-level aggregations.

1.3 Update the Data Flow Scheduler
Locate the Data-Admin-DataFlowScheduler-Aggregation record and change the pre-aggregation source from Stream to IH DB.

Step 2 — Generate Data Migration Artifacts

Log in as an operator with Revision Management or Pega 1:1 Operations Manager access, then generate the data migration artifacts from the CDH portal. This ensures your custom table structures are correctly mapped into the analytical grid used by Impact Analyzer.

Step 3 — Verify RTDG and Data Timing

  • Confirm the RTDG is enabled and correctly configured — it’s the core component that drives the Live data capability.

  • Check that your custom IH insertion logic doesn’t introduce a significant delay between pxOutcomeTime and system time. If the gap is too large, records may be skipped during summary processing.

  • After any DSS or prconfig changes, restart all nodes to ensure the new settings are applied across the cluster.

Other suggestions:

  1. Check VBD Actuals Synchronization:
    Verify that your custom interaction history table is properly synchronized with VBD Actuals
    Run the pxSyncActuals activity to manually sync if needed
    Ensure the IHSource parameter is set correctly for your custom table
  2. Verify Interaction History Configuration:
    Check the pyInteractionHistoryConfiguration data transform
    Ensure measurement properties for Impact Analyzer are properly configured
    Verify that your custom IH table has all required fields
  3. DSS Settings Verification:
    Check if there are any DSS settings that need to be adjusted for custom IH tables
    Verify data retention settings that might affect Impact Analyzer data availability
  4. Data Flow Execution:
    Run the IAPopulation outbound data flow to populate data in actuals
    Verify that data is being written to VBD Actuals from your custom IH table