How aggregations will run
Creating or updating data (ContainerSX replacement)
• Instead of running automatically on every save of the definition, a new action will be used:
◦ BOMCreateUpdateAggregationDataRecords
◦ Label: Create/Update aggregation data records.
• This action can be called explicitly or scheduled (for example via Alert conditions).
Implication
• Data creation/refresh will be more controlled: no unexpected long runs when simply saving a definition.
• You (or an admin) can trigger updates at the right moment (e.g. nightly, or before reporting).
Filling the aggregated results (ReportSX replacement)
• Report logic will still be triggered by status changes on the aggregation definition.
• The system will no longer try to run the logic on every save, but only on the defined status change.
• If there are no data records yet, the logic will simply do nothing and not give an error, same as today.
Implication
• You will still use status changes (and possibly scheduled actions) to run aggregations.
• Behavior around which data records may be updated (based on their status) remains the same as in the current solution.
Further details and configuration examples are described in: