Available through Axeda® Platform Web Services only!
A Threshold Rule provides a way for your devices (or the Axeda® Platform) to evaluate conditions and run actions for conditions that evaluate to true. As opposed to Expression rules, threshold rules support a discrete, defined set of conditions and actions. The resulting threshold rules are of a fixed format, enabling manufacturers to configure their devices to support running these rule types. Threshold rules are saved to the Platform and sent to devices for running, if supported by their defined device profiles.
Each threshold rule defines a pairing of a threshold condition and a threshold action. For example, for a threshold rule that creates an alarm, AlarmX with severity 250, when the value of data item, "temp" is above 100, the threshold action creates an alarm and the threshold condition is "AboveLevel". For details about threshold rules, refer to the Axeda® Platform Web Services Developer's Reference Guide.
If a device does not support running and evaluating rules, rules for those devices can be run at the Platform as with other rules.
As part of configuring your threshold rules, you need to apply each threshold rule to the model related to that rule so that data items for that model are available for definition in the threshold condition. For details about applying threshold rules to devices, refer to the Axeda® Platform Web Services Developer's Reference Guide.
For information about security for these objects, refer to Security for Objects in Axeda® Connected Product Management Applications and for information about security for these objects when Delegated Administration is enabled, refer to Security for Objects in Delegated Administration Units.