📄️ Overview
The Change Management group includes options specific to customizing the change module. It has the following features:
📄️ Change Form
Streamline change management processes by customizing forms to efficiently plan, approve, and track changes within your organization.
📄️ Change Status
Change Status determines the progress of the Change tickets at each stage. Using these statuses, you can see how much work is complete or pending on a ticket and take action accordingly. The system provides default status values that are ready to use.
📄️ Change Custom Rules
The Change Custom Rules page allows administrators to configure compliance checks that govern how changes are processed through their lifecycle. By defining these rules, organizations can ensure that change records are complete, all prerequisites are met at each stage, and proper documentation is maintained.
📄️ Change Form Rule
Change form rules let you make fields (system and custom) mandatory or optional, show or hide them, enable or disable them, set or clear values, and show or hide options based on conditions in the change form. These rules apply when creating a change, editing a change, or both. This helps you collect the required details from the users.
📄️ Change Type
A Change Type determines the kind of change being requested. It is another classification that helps technicians filter changes.
📄️ Change Category
Categories enable you to group similar changes under a single category. This helps technicians filter the required changes quickly from a large list. The system provides the following categories by default:
📄️ Print Templates
Streamline your change management process by generating customized printouts of change requests.
📄️ Change Templates
Templates are ready-made forms that you can use when filling out a change form. You only need to select a template, and the form is filled in automatically. These are convenient when a change is of standard or recurring type. The advantages of using a template are:
📄️ Change Risk
Change Risk shows the risk factors that could adversely affect a change. The system includes predefined risk levels by default that cannot be removed.
📄️ Change Reason
A change can be defined bya specific reason that leads to improvements in existing instances. This development or improvement is called a reason for the change.
📄️ Change Model
A Transition Model describes how a Change Request transitions from one state to another in ServiceOps.
📄️ Target Environment
Organizations typically use multiple environments. In standard practice, a change is first made in the development environment, then the test environment and finally the production environment. You can manage this list of environments. In a change request, the Target environment field is a dropdown and uses only this list.