Users Guide

Change Determination Process | Change Management and Compliance
OMNM 6.5.3 User Guide 523
9 Click Add Action , and click the Custom action alternative, then click Keyword Search and
select Change Determination. That action appears in the drop-down combo box. Notice you
can also select a target in the action selector. By not selecting one, we run change
determination against all Managed Equipment.
10 Click Apply and view the Change Determination action listed in the Actions screen.
Notice that you can add more actions, and edit or delete existing ones with the icons to the
right. Click
Apply once you have selected Change Determination.
11 Click Save to preserve this event processing rule. The rule should now respond to the
configured event, triggering the action you configured.
NOTE:
Backup and Change Determination automates backing up target devices.
Also: Change Determination’s current default is to compare files even if the “Config Change” flag has not
been modified.
Change Determination Defaults
By default, Change Determination can run against all devices without requiring the config change
update flag be set or updated based on events tied to the Update Config Change Flag event
processing rule/action.
To disable the manual run-ability of the Change Determination process, uncomment the property
in
\owareapps\changemgmt\lib\cm.properties (or add it to
\owareapps\installprops\lib\installed.properties ).
#############################################
# Change Determination Flag
# Allows system to be flagged to only run
# change determination against devices we
# have received Config Change Event for.
# Default Behavior is to run change determination
# for All targets (the same as setting the below property = false)
#com.dorado.changemgmt.change.determination.require.config.events=true