What's new in version 10.9.0
A new application called
Streaming Analytics is now available in the
Cumulocity IoT application switcher.
Analytics Builder is now part of this new Streaming Analytics application, together with EPL Apps. See also
Starting
Analytics Builder.
The following new blocks are now available:
Smart rule behavior:
KPI (this block implements the core part of the "On measurement threshold create alarm" smart rule; see also
Smart rules collection in the Cumulocity IoT
User guide)
Position and geofence support:
Non-device inputs and outputs (see also the "On alarm send SMS" and "On alarm send email" smart rules under
Smart rules collection in the Cumulocity IoT
User guide):
Constant Value (see also the list of new input and output ports on existing blocks below)
More calculations and aggregates:
Utilities and flow manipulation to give more flexibility in writing models:
Set Properties (see also the list of new input and output ports on existing blocks below)
Switch (this block is intended to be used with template parameters)
Additions and changes to existing blocks:
The
Property Name parameter is now optional. If not set, any update to a managed object generates an output.
The
Property Name parameter is now optional, allowing several properties to be updated in one go (for example, using the new
Set Properties block).
New
Time input port.
New
Properties input port (see also the new
Set Properties block).
New
Properties input port (see also the new
Set Properties block).
The
Severity parameter is now optional. The severity of the alarm can now be set either via the
Severity parameter or the new
Severity input port. One of the input port and parameter must be connected or set.
The
Severity input port (but not parameter) also supports a CLEARED value to clear the alarm instead of creating or changing the severity of an existing alarm.
The
Message parameter is now optional. The message of the alarm can now be set either via the
Message parameter or the new
Message input port. One of the input port and parameter must be connected or set.
New
Time input port.
New
Clear Alarm input port.
The
Property Type parameter now supports a new option:
Properties. This is intended to be used with the following block types:
Operation Output (the
Properties input port),
Event Output (the
Properties input port), and
Managed Object Output (the
Value input port).
The
Property Name parameter is now optional so that the
Properties Type is able to just pass through the properties (see also the new
Set Properties block).
The input blocks are now able to distinguish between create and update events. For this purpose, a new
Notification Mode parameter is now available in the block parameter editor. This is helpful, for example, if you are only interested in new alarms being created and you are not interested in models being activated when the same alarm is updated. This new parameter is available for the input blocks of type
Alarm Input,
Event Input,
Operation Input, and also for the new
Position Input type. It is not available for input blocks of type
Measurement Input as measurements cannot be updated. See the
Input category in the Block Reference for more information.
A new
chain_diagnostics parameter for monitoring periodic status is now available. It provides diagnostic information about model chains, such as the time when the chain was created or the number of times the chain has been evaluated. See
Monitoring periodic status for more information.
A new
block_promise_timeout_secs key for configuring model timeouts is now available. This tenant option defines the timeout in seconds to wait for
Promise values returned by block actions like
$validate to be completed. The default is 60 seconds. See
Keys for model timeouts for more information.
Objects containing the
c8y_Kpi property are now treated as broadcast devices in addition to
pas_broadcastDevice. See
Broadcast devices for more information.
Analytics Builder now supports the standard user interface languages of
Cumulocity IoT. See
Available languages in the
Cumulocity IoT documentation for more information.
Detailed documentation is now available which covers the distinctions between value types representing continuous-time and discrete-time values, and the
pulse type. It also covers some of the details of block implementations around windowing and when blocks generate output. See
Details of Values and Blocks.