Enabling or Disabling Change Management
The default is that the Change Management workflow is disabled. Users do not need to open tickets and get approval when making configuration changes. If you want to enforce the Change Management workflow, you must enable it globally for the system.
Before you begin
There are several system processes that prevent you from enabling/disabling change management. If any of the following are in process, you need to wait for them to complete before changing these settings: backup/restore; import/export; domain movement; upgrade; Flexconfig migration; device registration; high-availability registration, creation, break, or switch; cluster create, registration, break, edit, add or remove nodes; EPM break out or join.
An access control policy cannot be locked when you change these settings. If a policy is locked, you must wait for the lock to be released before enabling/disabling this feature.
Procedure
Step 1 | Choose System ( |
Step 2 | Click Change Management. |
Step 3 | Select Enable Change Management. To disable the feature, deselect the option. All tickets must be approved or discarded to disable Change Management. You cannot disable Change Management if any ticket is in the In Progress, On Hold, Rejected, or Pending Approval state. |
Step 4 | Select the Number of approvals required, which is how many administrators must approve the change for the ticket to be approved and deployable. The default is 1, but you can require up to 5 approvers per ticket. Users can override this number when creating tickets. |
Step 5 | Select the Ticket Purge Duration, which is the number of days to keep approved tickets, from 1-100 days. The default is 5 days. |
Step 6 | (Optional.) Enter the Reply to Address and the email addresses for the List of Approver Addresses. You must also configure the Email Notification system settings for email to work. |
Step 7 | Click Save. The system adds the Ticket ( |
