An approval is a mechanism to block execution of a workflow deploy or utility execution request until the required approval is (s) are granted. Approvals can be configured on folders. A deployment of a project requires any approvals defined on the nearest folder in the hierarchy which is overriding approvalsApprovals required for Project can be seen on parent folder’s Approvals tab. If parent folder does not override approval setup, then it’s parent folder is examined till folder overriding approvals is found. Approvals set at lower levels in the folder hierarchy override(replace) approvals setup on higher - level approvalsfolders. Approvals can be configured by environment at each level, providing ultimate flexibility. Approvals can be internally managed in FlexDeploy or can be delegated to external change management system. In addition, approval can be configured to automatically create change ticket with underlying change management system.
Approvals only applies to deployments submitted for individual Projects, and does not apply to executions initiated by Release Pipeline. Please note that Pipeline provides continuous delivery capabilities and it has various gates to control approval, schedule etc.
There are two types of approvals.
Approvals which generate tasks for users to manage inside of FlexDeploy.
External Approvals which are tied to tasks/tickets in external systems. These approvals are tied to a Change Management System.
To add an approval to a folder, open a folder.
...