Page Comparison

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 adhoc execution or within a pipeline
• Incident Management - Automatically create incidents whenever a deployment or pipeline stage fails 

Features and Use Cases

The next generations of Change Management Systems page, which can be accessed through the Administration - Integrations - Change Management Systems menu, System integration was introduced in FlexDeploy 5.6.0.0, which provides rich features and enables a number of powerful use cases to further integrate and automate the DevOps lifecycle.

• Out of the box integrations with a few popular change management systems
• Associate existing CMS tickets with deployment requests or pipeline stage executions
• Automatically create change tickets (whether for adhoc deployment requests or as part of a pipeline)
  • Define the ticket fields and map their values to provide context
• Bind deployment request approvals or pipeline approvals to the status of the linked ticket(s).  Automatic approval in FlexDeploy when the linked ticket in the CMS is approved. 
• Use one ticket per release, one ticket snapshot, or even one ticket per project/package in the snapshot.
• Propagate the ticket numbers across pipeline stages to avoid duplication data entry by users.
• Utilize Outgoing Webhooks to automatically create Service Management Incidents when deployments or pipeline stage executions fail.
• Deployment report data is tied back to the CMS ticket number for auditing
• Framework to include to enable all these features or other CMS Systems via custom integrations. 

Global Configuration

The global configuration for change and incident management systems can be accessed using the  Administration -> Integrations -> Change Management Systems menu.  This page allows management of integrations into third-party change service management systems. FlexDeploy currently provides out of box deploy-time integration with ServiceNow for tying change tickets to deployment requests, and/or creating incidents upon deployment failure. You can define custom implementation using either Java class or Groovy script.Here is , BMC Remedyforce, Freshworks Freshservice, and Jira ITSM.  You can also define custom integrations implemented using either Java or Groovy.

Here are the out of box change management systems. To configure, select ServiceNow a name link or select a row and click the Edit button. Change Management System screen allows you to view the details on our out of box ServiceNowproviders. FlexDeploy comes up with Java Implementation to integrate with ServiceNowout of box providers. For these, you are not allowed to change implementation class and change or add new properties. You can create additional Change Management System as necessary using the Create button.

Image RemovedImage Added

Terminology

• If you want to configure ServiceNow, BMC Remedyforce, Freshworks Freshservice, or Jira ITSM, use the Configure Change Management Systems to make any changes to properties or other configurations
• For adding a custom change management system, follow the steps described in Custom Change Management System
• Once the Change Management System properties are configured, create an instance to integrate with FlexDeploy. Configure Change Management System Instance shows how to setup set up the instance by providing the server and credential informationsinformation
• The next steps after creating and testing the instance is to Configure Change Management. Here you can choose out of box ServiceNow, BMC Remedyforce, Freshworks Freshservice, Jira ITSM, or any other custom system configured
• Change Requests are verified/created when a project is deployed. Associate Change with Deploy describes how FlexDeploy handles the Change
• Follow the necessary steps to configure Freshservice, BMC Helix Remedyforce, ServiceNow, or Jira ITSM.