Analytics Builder 10.15.0 | Using Analytics Builder for Cumulocity IoT | Release Notes | What's new in version 10.15.0
 
What's new in version 10.15.0
*Additional Analytics Builder samples are now available in the model editor. The provided samples now cover all of the smart rules from Cumulocity IoT.
*Detailed descriptions have been added for the Analytics Builder samples. You can see the first lines of such a description in a tooltip when you move the mouse over the card for a sample, or you can see the full description when you view a sample (or create a model from the sample) and then open the Model Configuration dialog box.
*It is now possible to search for Analytics Builder samples with specific words in their names and to filter them by tags.
*In the previous version, the template parameter names in the Analytics Builder samples were only available in English. As of this version, translations are available for the supported languages.
*The Alarm Output and Measurement Output blocks now have a new Params Fragment parameter and a new Properties input port. These can be used to set custom properties, similar to the already existing functionality of the Event Output block.
*The Alarm Output block now has a new Create Asynchronous Output parameter. It is not selected by default which reflects the block's previous behavior. When selected, alarms can now be created and cleared asynchronously.
CAUTION:
Special care must be taken when using the Create Asynchronous Output parameter. This may result in infinite loops during model execution (for the same model or across multiple models), leading to performance degradation or the application running out of memory.
*Analytics Builder now supports the globalTitle branding option for the category names in the model editor. See also Branding and language customization in the Cumulocity IoT documentation.
*As announced in What's new in version 10.14.0, the frgment property has been removed in 10.15. If you have not already done so, you must now change frgment to fragment in all of your blocks (for example, the value of the Property Path parameter in the Extract Property block).