Process analytics dashboard not updating after bulk data import via integration

BPM Creatio
, , , , , , , ,
1

We have a scheduled integration that imports completed process instances from an external system into Creatio 8.3 nightly. The data appears correctly in the process tables, but our process analytics dashboards show stale data - they don’t reflect the imported records until we manually trigger something.

The integration uses the Integration Connector to POST process data via REST API. We’re mapping fields correctly:

{
  "ProcessName": "OrderFulfillment",
  "StartDate": "2024-12-07T00:00:00Z",
  "Status": "Completed",
  "Duration": 14400
}

The records insert successfully into SysProcessLog and related tables. But when users check the Process Analytics dashboard in the morning, it still shows yesterday’s metrics. If we manually run any process instance through the UI, then suddenly all the imported data appears in the dashboard.

Is there a separate refresh mechanism for process analytics that doesn’t automatically trigger on bulk inserts? The dashboard widgets are configured to show real-time data, but something about the integration bypass normal refresh logic.

2

Process analytics dashboards in Creatio rely on a data mart that’s separate from the operational process tables. When you insert directly via API, you’re writing to the transactional tables but not triggering the ETL process that populates the analytics data mart. That’s why manual process execution makes it appear - it triggers the data mart update as a side effect.

3

That makes sense. Is there a way to manually trigger the data mart rebuild after our nightly import completes? Or should we be writing to different tables?

4

Thanks everyone. I’ve configured the post-import trigger and it’s working now. The dashboard updates correctly each morning after the import completes.

5

You can trigger the data mart rebuild programmatically. There’s a system process called “Update process analytics data” that you can call via API after your import. Alternatively, schedule it as a separate process to run shortly after your integration completes. The data mart rebuild is incremental by default, so it won’t reprocess everything - just new records since the last update.

6

I had this exact scenario. The data mart rebuild can be scheduled in System Designer under Process Analytics settings. You can set it to run every hour or on a custom schedule. Much cleaner than calling it programmatically after each integration run.