Rulesets allow the administrator to configure the Change Management process. Configurations based on ticket routing, prioritization, and urgency can play a role in change requests. You can configure change request rulesets.
See Configuring change request rulesets
The following table describes the change request rulesets that allow for routing, and prioritization.
Table: Change Request Rulesets
Executed when the CAB approves a change plan and submits it for implementation.
Executed when the system receives a change request.
Use for routing, prioritization, auto-planning, and notification.
Executed when a change has been successfully completed.
Executed when the Planned Start Date for a change has been reached.
Executed when implementer indicates that they were unable to implement the change.
Executed when the change manager (Gatekeeper) approves and submits a change request.
Executed when the CAB rejects a change plan .
Executed when the CM (Gatekeeper) has denied a change request.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.