Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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.

FlexDeploy Administrators will see all Human tasks and can approve/reject all tasks.

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:

  • Approval Group Name

  • Assignee

  • Action By Name

  • CMS Ticket Number

  • Gate 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.

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).

  • No labels