Skip to content

Commit 6477590

Browse files
authored
Merge pull request #109125 from dominicbetts/vanessa-rule-updates
Update IoT Central rules article
2 parents e3cd443 + b1788b6 commit 6477590

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/iot-central/core/howto-configure-rules.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ manager: philmea
1212

1313
# Configure rules
1414

15-
16-
1715
*This article applies to operators, builders, and administrators.*
1816

1917
Rules in IoT Central serve as a customizable response tool that trigger on actively monitored events from connected devices. The following sections describe how rules are evaluated.
@@ -32,6 +30,12 @@ In the following screenshot, the conditions check when the temperature is greate
3230

3331
![Conditions](media/howto-configure-rules/conditions.png)
3432

33+
### Use a cloud property in a value field
34+
35+
You can reference a cloud property from the device template in the **Value** field for a condition. The cloud property and telemetry value must have similar types. For example, if **Temperature** is a double, then only cloud properties of type double show as options in the **Value** drop-down.
36+
37+
If you choose an event type telemetry value, the **Value** drop-down includes the option **Any**. The **Any** option means the rule fires when your application receives an event of that type, whatever the payload.
38+
3539
## Use aggregate windowing
3640

3741
Rules evaluate aggregate time windows as tumbling windows. In the screenshot below, the time window is five minutes. Every five minutes, the rule evaluates on the last five minutes of data. The data is only evaluated once in the window to which it corresponds.

0 commit comments

Comments
 (0)