Rule filters: empty-value operators and system uptime
Two specific improvements would make device-targeting rules easier to use:
1. Empty and non-empty text values
Add explicit is empty and is not empty operators for text fields in the visual rule editor. Text fields can already be compared with an empty string in the advanced editor; dedicated operators would make this directly accessible without writing a query.
2. System uptime as a rule criterion
Allow rules to compare the time since a device last booted against a configurable duration, such as a number of days.
Example: select Windows workstations with system uptime greater than seven days for a scheduled automation that prompts the user to restart.
Log in to comment and vote
Comments4
Aquamarine Cookie
Nov 6
In addition, it would also be useful to have more criteria available for designing rules. 😉🐙
Erdinc Akay
Nov 6
Hi @Kevin ENGEL , I adjusted your Feature-Request to be more specific :)
Aquamarine Cookie
Nov 6
Many thanks @Erdinc Akay ! 🙌🏻🐙
Aquamarine Cookie
Oct 19
Hello, in addition, it is really necessary to have greater access to variables when designing rules.
For example, in an automation workflow, I want to suggest a restart to the user if their workstation has been online for more than seven days. When designing rules for scheduling, I do not have access to the device’s uptime.
It is essential to have as many variables as possible to design highly granular rules. Just like in Datto RMM. 😜
Merci! 🙌🏻