Migrating engagement health configuration to calculated metrics<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Overview Starting with Customer Success Management 5.7.6, the Calculated Metric data source can be used to determine the health score for an engagement. As part of this update, the Engagement Health Definition and Health Metric Configuration tables have been deprecated. This KB article provides guidance for existing customers on how to handle the migration from the legacy tables to the new Calculated Metrics framework. For Existing Customers During the upgrade, the system will set the property: sn_acct_lc.use_calculated_metrics_for_health = False This will mark the Engagement Health Definition and Health Metric Configuration tables as “Deprecated”. At this point, the data has not yet been migrated to the new model. Customers will need to manually run the migration script to move the Health Definition data into the Calculated Metrics framework, ensuring compatibility with your existing data. We recommend running the script immediately to get the latest data, model updates, and the new approach applied. Please note that the migration won’t take effect until the script is run. If the script is not executed, there will be no immediate impact on the current data. Migrating Legacy Data To migrate data from the legacy Health Definition and Health Configuration tables into the Calculated Metrics framework, customers can run the provided migration utility via a Background Script: new sn_acct_lc.MigrateHealthDataUtil().markHealthTablesDeprecated(); This script performs the following actions: Create a new Calculated data source for health: Engagement Health Score Migrates Health Definitions → Breakdown Segments Migrates Health Configurations → Segment Configurations Migrates Color Bandings → Segment Configurations Transitions PA Indicator data → Data Context Engine (DCE) Deactivates the following scheduled jobs: PA Indicator Engagement Health Score After migration, the property sn_acct_lc.use_calculated_metrics_for_health will be set to true Create and Associate the Visualization After creating the calculated data source, users must create a new DCE Visualization that references this data source: Navigate to:All → Data Context Engine → Visualizations Click New and configure the visualization to reference the newly created Health Score data source (Engagement Health Score). Save the visualization. Link Visualization to Insight Item Navigate to DCE Visualizations to review all available visualizations. Open the “Health Score” DCE Insight Item. Add an entry to the Visualization M2M (many-to-many) records, selecting the new visualization. This ensures your custom Health Score visualization appears correctly within the DCE Health Score Insight Item. Troubleshooting: Problem: Delays or gaps in the Engagement health score calculation.Solution: Update the Engagement Health Score Calculation scheduled job to run at 2 o'clock instead of the default run time. This helps ensure more timely score updates, especially in environments with higher data volume.