An asterisk (*) indicates a mandatory field. |
Field | Description |
---|---|
Name | A free-text field specifying the name of the Rule. |
Description | A free-text field providing a description of the Rule. |
Rule generates an alarm of severity | Select the check box for the Rule to generate an Alarm of a particular severity. In the adjacent drop-down list, select the applicable Alarm severity: • Warning • Minor • Major • Critical • Information See also: Rules & Alarms. |
Field | Description |
---|---|
Timezone | Specify the time zone that applies to the Rule. |
Rule Activation Type | This field determines whether the Rule is activated for a specific time period or based on a schedule, as follows: • Period – Specifies the time period when the Rule is active. The condition(s) of a Periodic Rule are only checked during the particular days and times that you specify. If they are met, then the action defined for the Rule is triggered. For this type of Rule, each time an event arrives within the defined time period that crosses the threshold specified in the Rule’s condition, the Rule is activated. |
• Schedule – For a Scheduled Rule, you specify the frequency, day(s) and exact time when the Rule’s condition(s) are checked. If the conditions are met at this exact time, then the Rule action is triggered. If no condition(s) are defined the Rule action will be triggered at the scheduled Set Hour. Setting this rule to be active Daily, Weekly or Monthly means that the condition(s) is checked Daily, Weekly or Monthly. You can add additional times when the Rule is meant to be active by clicking the button, and then specifying the time in the new Set Hourrow. | |
Daily In the following example, the condition(s) are checked once a day at 10:00. Weekly In the example below, the condition(s) are checked on Sundays and Tuesdays at 10:00 and 11:00. Monthly In the example below, the condition(s) are checked on the first of the month for January, March and May at 10:00 and 11:00. | |
• Relative - For a Relative Rule, select the device(s) which contain the booking information in the Get Data From field (devices with the Calendar tab) and specify the time relative to the booking in which the action is to be triggered. Example: Fifteen minutes before start of meeting. Get Data From – Specify the calendar device, and the rule apply to (All the meetings will be taken from the device calendar). Activate Rule – Specify when to run the rule. You can trigger the rule X minutes before or after meeting (Apply for all the meetings). |
An asterisk (*) indicates a mandatory field. |
Field | Description | ||
---|---|---|---|
Condition Name | Specifies a name for the condition. | ||
Condition Level | Specifies the type of entity on which the Rule’s action is to be performed such as; an Application, Device or Product. Note that some condition types only apply to the specific entities. For more details. | ||
The Condition Level for the Threshold with Duration, In Geofence with Duration and Out of Geofence with Duration condition types can be set for the: • Application • Device • Product • Digital Twin • Group template The Condition Level for the Threshold with Duration, In Geofence with Duration and Out of Geofence with Duration condition types can also be set for multiple devices simultaneously. • Devices – Specifies the Device(s) on which to apply the condition. • Data – Specifies the property or Event identifier (Event Name plus Type Code) that triggers the Rule. The properties in the drop-down list vary, depending on the Condition Level selected (see above). For example, if the Condition Level is Application, then only properties of an Application will display. The Events in the drop-down list specify the name of the Event for the Application ID/Product/Device on which to apply the condition. IoT Platform works on a combination of the Event Name and Type Code to uniquely identify an Event.
• Operator - Specifies the operator to apply to the data selected in the Data. The options that display in the drop-down list vary, depending on the data selected in the Data field. • Value - Specifies the value that triggers the condition. |
An asterisk (*) indicates a mandatory field. |
Field | Description |
---|---|
Condition Name | Specifies a name for the condition. |
Condition Level | Specifies the type of entity on which the Rule’s action is to be performed, such as an Application, Device or Product. |
Readings | Specifies the reading that triggers the event. |
Field | Description |
---|---|
Condition Name | Specifies a name for the condition. |
Device | Specifies the device to apply the condition. |
Device Reading | Specifies the device reading for the condition. |
Operator | Specifies the operator to apply to the data selected. |
Difference | Add operation for the second device reading value , (i.e. Difference Multiply 2 will be equal to Temperature from room 1 is greater than twice the temperature in room 2). |
Field | Description |
---|---|
To | Clicking in the To field allows you to specify the recipient(s) for receiving the SMS. Here, you can select: • Users to send the notification to individual people by selecting the application users, or by adding a specific phone number/address. • Roles to send the notification to a group of people. • A combination of the above (Users & Roles). |
Message Content | Specifies the content of the SMS message to be sent. The system automatically populates the keywords and the message content according to the Rule you have defined. You can manually add text and keywords, or edit the message, as needed. Alternatively, you can select from the available keywords in the system by typing a curly bracket ({ ), and then selecting a relevant keyword in the drop-down menu that displays, as shown below: |
IoT Platform keywords can be included in the message inside brackets {}. These keywords enable you to include information retrieved by IoT Platform in the message. 1. Restore to Default Message – Click this button to restore the Message Content to its default message. 2. Rule action will repeat – Specifies the number of times to repeat the Rule action and the interval between repetitions. 3. Rule Description – Provides a free-text description of the Rule. |
Field | Description |
---|---|
Method | Specifies the method of the web service: • GET • POST • PUT • PATCH • DELETE • HEAD |
URL | Specifies the URL to which to send the call. |
Headers | Click the plus button to add the key and value properties of the header. These are the key/values that are sent as HTTP headers. The key becomes the header key and the value becomes the header value |
Body | Specifies the body of the HTTP call. You can click the Test button after filling in this field to perform a live test. |
Response | Specifies the response received to the HTTP call. You can view the response after doing a live test (see above). |
Rule Description | Free text describing the Rule. |
Field | Description |
---|---|
Devices | Specifies the Device to which to send the command. |
Commands | Specifies the command to send to the Device. |
Rule actions will repeat | Specifies the number of times to repeat the Rule action and the interval between repetitions. |
Rule Description | Provides a free-text description of the Rule. |
Field | Description |
---|---|
Devices | Specifies the Device whose settings are to be changed. |
Settings | Specifies the setting to change on the Device. |
Value | Specifies the new value to assign to the setting on the Device. You can add “ +, -, * ,/ ” so that the property will increment by. |
All other action types are not currently supported. |