Changes in Cumulocity IoT devices are automatically processed by Analytics Builder [PAB-4963]

content/change-logs/analytics/apama-in-c8y-20251127-AB-Processing-DeiviceHirearchy-changes.md

@@ -0,0 +1,20 @@
+---
+date: 2025-11-27
+title: Changes in Cumulocity IoT devices are automatically processed by Analytics Builder
+change_type:
+  - value: change-inv-3bw8e
+    label: Announcement
+product_area: Analytics
+component:
+  - value: component-M5-cepIIS
+    label: Streaming Analytics
+build_artifact:
+  - value: tc-KXXmo2SUR
+    label: apama-in-c8y
+ticket: APMF-94
+version: 26.257.0
+---
+
+Analytics Builder models will now automatically track changes to devices, including additions, deletions, and updates to device, members of Group and Asset. This ensures that any structural or configuration changes are immediately reflected in model processing without user intervention. The earlier requirement was to deactivate and reactivate models to pick up such updates is no longer needed.
+
+For details, refer to [Device Hierarchy changes ](/streaming-analytics/analytics-builder/#device-hierarchy-changes).

content/streaming-analytics/analytics-builder-bundle/models-and-devices.md

@@ -195,3 +195,33 @@ You can combine several values. For example, specify the following if you only w
 The default value of this tenant option is `not has(c8y_IsVirtualDevice)`. As long as you do not change this tenant option, virtual devices are not shown as they would not make sense in an analytic model. If you change the value for this tenant option, make sure to specify all managed objects that you want to see in the search result.
 
 See also [Configuration](/streaming-analytics/analytics-builder/#configuration).
+
+### Device Hierarchy changes {#device-hierarchy-changes}
+
+Analytics Builder models, once deployed, automatically process data from all linked devices. Any changes to device configuration—such as device addition, deletion, metadata updates (for example, device type changes), or updates to group/asset membership—are now detected automatically.
+The affected models immediately reflect these changes without requiring manual deactivation or reactivation.
+
+{{< c8y-admon-info >}}
+[The Smart Rules (NEW) plugin](https://cumulocity.com/docs/streaming-analytics/smart-rules-plugin#what-is-the-smart-rules-plugin), which internally uses Analytics Builder models, behaves the same way. It dynamically responds to updates in the device hierarchy and continues processing data from the updated device set.
+{{</ c8y-admon-info >}}
+
+#### Model Deletion Scenarios.
+Models are automatically deactivated in the following cases:
+
+- If the input device or output device of the modle is deleted.
+- When the parent group or asset configured in the model is deleted.
+
+In such cases, the model is removed and an error message is recorded in the logs.
+
+#### Handling Structural Changes
+Models also automatically adapt to structural changes within a device hierarchy. This includes:
+- Re-arrangement of devices inside groups or assets
+- Addition of new devices
+- Removal of existing devices
+{{< c8y-admon-info >}}
+ When a model is deployed to process a Group, all devices can be removed from the Group, leaving it with zero devices. The model will not be deleted, and it will restart  processing again whenever a device is added back to the Group
+{{< /c8y-admon-info >}}
+
+#### Limitations to these changes.
+
+- Cascade deletion of a Group is not supported (This Case needs a reload of the model to take effect.)