FlexDeploy provides integration with various Service Management tools for both Change Management and Incident Management
Change Management - Create new change tickets or link to existing change tickets, and bind them to an automated approval for ad-hoc execution or within a pipeline
Incident Management - Automatically create incidents whenever a deployment or pipeline stage fails
Change Management System Instance is configuration details to connect with specific change management system like ServiceNow, BMC RemedyForce etc. This information is used to manage tickets and incidents.
To create a Change Management instance, select the Change Management tab, and click the create plus button. To edit an existing instance, click on the name of a specific CMS Instance from the list.
Enter values for the fields as described in the table below.
...
Field Name
...
Required
...
Description
...
Instance Name
...
Yes
...
Long display name for the instance.
...
Instance Code
...
Yes
...
Short name for the instance.
...
Change Management System
...
Yes
...
Jira, BMC Remedyforce, Freshservice, and ServiceNow are the supported out-of-box change management systems. Any custom Change Management Systems you create will also appear as an option here. Once the Change Management Instance is saved, this cannot be modified.
...
Description
...
No
...
A description of the instance.
...
Active
...
Yes
...
Whether or not the instance is active in the system. Defaults to "Yes".
...
Properties
...
No
...
If the selected Change Management System has any properties defined, then you must set up values for those properties based on the property key definition.
...
Features and Use Cases
The Change Management System integration provides rich features and enables a number of powerful use cases to further integrate and automate the DevOps lifecycle.
...
FlexDeploy Term | Description |
|---|---|
Change Management System | Defines the system used to ensure that changes are managed in a cohesive way, ensuring frequent checks and balances around user impact, corporate policies, regulatory compliance, security, etc. and to establish and support the implemented enterprise operational model. ServiceNow, BMC Remedyforce, Freshworks Freshservice, and Jira ITSM are available out of box, but you can add a custom integration using a Java or Groovy implementation. |
Change Management System Instance | Instance represent the physical connection details of the Change Management System. |
Property | Properties are used to define the inputs necessary to connect to the system, |
...
If you want to configure ServiceNow, BMC Remedyforce, Freshworks Freshservice, or Jira ITSM then you can use out of box change management systems, otherwise you need to define Custom Change Management System.
Configure Change Management System Instance, which allows for configurations like server, credentials, etc. to interact with specific change management system.
If you want to deploy projects individually with change management integration,
Create external approval requirement on necessary folder, configurations will be inherited by all projects under this folder and it’s sub-folders. See Change Management Approvals on Folders.
Now you are ready to submit deployment for project. See how to submit executions with change tickets.
Otherwise, you can also configure change management at Release level and use External Approval Gate in specific stage of pipeline. When using pipelines, the CMS configuration defined on folders is ignored, since the configuration from the External Approval Gates themselves is used . See Creating/Editing a Pipeline Version for details regarding the External Approval Gate.
...