The Tasks page is a centralized location to find all types of project and release tasks. Tasks can be set up on workflow requests, workflow executions, and pipeline gates/steps.

Users will access the Tasks screen in FlexDeploy by selecting Tasks from the menu.

The Search Tasks search box searches for the given search text in the following fields:

  • Assignee Name

  • Action By Name

  • CMS Ticket Number

  • Gate Name

  • Group Name

  • Override By Name

  • Pipeline Name

  • Project Name

  • Project Version Name

  • Release Name

  • Step Name

  • Task Id

  • Workflow Request Id

  • Workflow Execution Id

Additionally, there are drop down searches for Environment, Task Type, Task Status, and a toggle for My Tasks.

Approval Tasks

When a project request or pipeline gate is in the Pending Approval status, a defined person must approve the request before it is submitted for execution. In such cases, the approving persons are notified via email that they have a pending approval task.

FlexDeploy Administrators will see all approval tasks (even if they are not assigned to their group) and can approve/reject all tasks.

To approve a request, click the Approve or Thumbs up button. To reject a request, click the Reject button. The +Person button assigns the task to yourself.

See also - https://flexagon.atlassian.net/wiki/spaces/FD60/pages/9856634615

Note regarding External Approval Tasks

Approval tasks generated from External Approvals are generally not intended to be approved through FlexDeploy. They are intended to be managed within the external system itself. However, the tasks can be approved here in the event that the linkage is somehow broken with the external system.  Note that approving the task in FlexDeploy will leave the task in the external system as pending approval.

Scheduled Tasks

When an application or project request or pipeline gate/step is in the Scheduled status, the build or deployment has been scheduled for execution at a later date (typically due to a deployment window). In such cases the build or deployment will automatically become eligible for execution when that date/time is reached. However, a person with the required privileges (typically an administrator or someone from the operations team) has the option of releasing the request to occur immediately or cancelling the request.

FlexDeploy Administrators have permission to run or cancel all scheduled tasks.

To force the request to execute immediately, select the corresponding task and click the Run Now button. To cancel a request, select the corresponding task and click the Cancel button. If a task is forced to run now, or is canceled, the associated workflow will continue execution or fail as appropriate.

Human Tasks

When a release has a Human Task step that is waiting on an action, a defined person or persons must complete a task before the release can continue to the next step. In such cases, the approving persons are notified via email that they have a pending human task. Pre-Deploy workflows can also make Human Tasks.

When a release or project executes Pre-deploy, the workflow can create a Review task for a specific FlexDeploy group by outputting a value with code FD_REVIEW_GROUP. These Review tasks will appear as Human Tasks in this screen. Email notifications are sent that they have a pending human task. The intent is to review the output of the Pre-deploy execution by clicking the project name link in the task row. This will show the workflow execution details. The reviewer should view the pre-deploy results. Once reviewed, they will approve or reject the task either in the project (below) or back on the tasks screen (above).

The following macros are not currently supported in the footer:
  • style