Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Select the Environment, and a Default Approval Group who can approve this request in FlexDeploy should the external system be unavailable. Next, select the External System Type of Issue Tracking or Change Management.  Based on the type of external system type, select the external system which will manage the approval (available options are JIRA for issue tracking, and ServiceNow for change management.

Click the Save button to save the changes.

...

For Change Management Systems, the approval is created based on the ticket(s) associated to the deployment request.  This association is either through a reference on the deployment request (either through the FlexDeploy application UI, or via the REST API), or due to auto-creation configured at either the global, folder, application, or project level.  When the ticket is approved in the external system, the FlexDeploy approval task is automatically approved.Image Removed 

 Image Added

Pipeline Approvals

Similar configuration can defined for External Approval Gates within a pipeline. When using pipelines, the CMS configuration defined on folders, applications, or projects are ignored, since the configuration is used from the External Approval Gates themselves.  See Creating/Editing a Pipeline Version for details regarding the External Approval Gate.