Space banner This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Examples of Operational Rules

Creating Operational Rules consists of putting together steps. Following you can see examples of Operational Rules with their respective steps to help understand how to combine steps.

ConfigFiles.cst

This predefined Operational Rule updates the Patch Knowledge Base of a device if its operating system is any version of Windows. It consists of the following two steps:

Step 1: Check Operating System

This step checks the Operating System of the device . After the check it proceeds in two different ways depending on the Stop Condition:

  • if an operating system such as Windows XP (value = Yes) is detected, the Operational Rule proceeds with Step 2.
  • if an operating system such as Linux (value = No) is detected, the step failed and the Operational Rule stops.

Related topics

Getting-started-with-operational-rules

Adding-packages-to-operational-rules

Adding-dependencies-to-operational-rules

Advertising-an-Operational-Rule

Assigning-Targets-to-Operational-Rules

Parameter

Value

Stop Condition

The rule fails

Windows XP, Windows 2003, ... Windows 8 (64 bit)

Yes

Linux, Mac OS X, ...

No

Step 2: Install Package

In this step, Install Package the included package ConfigFiles.cstis checked for the correct checksum and installed on the device.

Parameter

Value

Package Name

ConfigFiles.cst

Package Checksum

0af1231f5c247cbad3df26c3abfc5946

Package 1: ConfigFiles.cst

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*