Users Guide

Change Management (Example) | Change Management and Compliance
502 OMNM 6.5.3 User Guide
Editing Compliance Policy Criteria
After clicking Add Criteria , use the pick list on the upper right to select an operation to select a
criteria match type (
Contains, Doesn’t contain, [does not] match Regex (see Regular Expressions
on page 508
), [does not] Match Regex for each line , Count number of occurrences , Perl or Java
(Groovy)
). Specify the match string or regular expression (Regex) in the text editor below the pick
list.
With the
Add Criteria button, you can configure multi-criteria policies with several lines. For
example, configure one saying a maximum of four lines containing
name-server can appear
(<5), in any order (
Match Regex for each line ), and another that says the configuration must
contain
no ip domain lookup [domain] .
Notice the radio buttons
Match Any of the following and Match all of the following . Selecting Any
means that if either of the lines matched the policy would succeed. Selecting
All says that both
lines must pass before the policy is successful.
For more complex scans, you can also enter Perl or Java (Groovy) language policies. See
Perl/Java
(Groovy) Language Policies
on page 510 for details about these. The does not operators are just
the negative of the match without does not.
Click the
Apply green check button to accept your term, or the Cancel button to abandon your
edits.
You can edit already listed compliance tests by clicking the
Edit button (pencil and paper) in the
list row. You can delete them by clicking the
Delete button next to the criterion.
Match Regex for each line
In using this type of term, OpenManage Network Manager processes each line separately,
comparing the input source to the match criteria. This returns a true value only if the criteria find a
match in the source. The order of matching is not important since OpenManage Network Manager
processes each line separately.