Operational rules
What is an operational rule?
An Operational Rule executes one or multiple CM functions on specific devices or device groups in the defined order.
An Operational Rule contains:
- Steps: a series of commands executed by the CM agent
- a schedule: defining the execution of the Operational Rule
- assigned objects: devices on which the Operational Rule is to be executed
- packages (optional): software to be installed via a step
- dependencies (optional): execution of the Operational Rule depends on other Operational Rules
What can I do with operational rules?
With operational rules you create dynamic scenarios that define how groups of client systems are to be managed today, and how they should automatically adapt to any changes in the future.
By applying these rules to groups of end-users, CM ensures that the users' devices are automatically provisioned with the right tools at the right time.
What is the process of working with operational rules?
The three steps of working with operational rules
Working with operational rules consists of three steps:
- Creating operational rule : adding steps, packages, dependencies
- Distributing operational rule : selecting assigned objects, defining the assignment and execution schedule
- Monitoring operational rule : following the execution progress and results, getting noticed by events that are triggered by the Operational Rule
Are there different types of operational rules?
Several different types of operational rules are differentiated in the Console by an icon:
General Operational Rules | Any operational rule performing any type of action without installing a package | |
Software Distribution Rules | Operational rules installing any type of package with the exception of patch packages | |
Patch Distribution Rules | Operational rules installing a patch package | |
Quick Link Rules | This type of operational rule can only be published on MyApps and only contains a clickable link. |