I’ve created a custom process analytics dashboard widget in Creatio 8.3 to track KPI metrics from our custom process log entity. The widget displays fine, but the data aggregation isn’t working - it shows zero values even though the custom process log entity has plenty of records.
The widget data source is configured to query our CustomProcessLog entity with a COUNT aggregation function. Here’s the entity schema configuration:
EntitySchema: "CustomProcessLog"
Aggregation: "COUNT"
GroupBy: "ProcessType"
Filter: "Status = 'Completed'"
I suspect there’s a mismatch between how the aggregation function expects data versus how our custom entity stores it. The process log entity has standard columns (ProcessType, Status, CompletedDate) but the widget keeps returning null aggregates. Has anyone successfully connected dashboard widgets to custom process log entities?
The inheritance issue is definitely part of it, but there’s more to configure. Process analytics widgets use a specific aggregation pipeline that requires certain entity columns to be marked as ‘ProcessMetric’ type. Your CompletedDate column should be DateTime with ProcessMetric flag enabled. Also, the widget data source config needs to specify the aggregation context - check if you’ve set the ‘AnalyticsContext’ property in your widget schema. Without it, the aggregation function won’t execute properly even if the entity is correct.
Thanks Marco. I checked and the entity does inherit from BaseEntity but not BaseProcessLog. Would that cause the aggregation to fail completely? The widget can see the entity in the data source dropdown, so I assumed it was properly registered. I’ll try changing the inheritance, but wondering if there are other configuration requirements for the widget data source that I might be missing.
I’ve encountered this exact scenario. Beyond the entity inheritance and column configuration, verify that your widget’s data source is using the correct entity schema name. In Creatio 8.3, custom process log entities need to be referenced with their full schema path in the widget config: ‘UsrCustomProcessLog’ not just ‘CustomProcessLog’. The aggregation function mismatch you’re seeing is likely because the widget is trying to aggregate on a non-existent entity path.
Check if your CustomProcessLog entity is properly registered in the process analytics module. Dashboard widgets expect process log entities to implement specific interfaces for aggregation. Your entity needs to inherit from BaseProcessLog or implement IProcessLogEntity interface. Without this, the aggregation functions won’t recognize the entity as a valid process data source.
All good points above. Also check your ESQ query configuration in the widget - the aggregation might be failing at the query level before it even reaches the widget rendering. Try testing your aggregation query directly in the ESQ debugger to see if it returns data. If the ESQ query works but the widget doesn’t display it, the issue is in the widget’s data binding configuration rather than the entity setup.