Workflow Definition

Create workflow definition

• Click Project Management -> Workflow -> Workflow Definition, enter the workflow definition page, and click the "Create Workflow" button to enter the workflow DAG edit page, as shown in the following figure:

  

• Drag from the toolbar to the canvas, to add a shell task to the canvas, as shown in the figure below:

  

• Add parameter settings for shell task:

1. Fill in the "Node Name", "Description" and "Script" fields;
2. Check “Normal” for “Run Flag”. If “Prohibit Execution” is checked, the task will not execute when the workflow runs;
3. Select "Task Priority": when the number of worker threads is insufficient, high priority tasks will execute first in the execution queue, and tasks with the same priority will execute in the order of first in, first out;
4. Timeout alarm (optional): check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds timeout period, an alert email will send and the task timeout fails;
5. Resources (optional). Resources are files create or upload in the Resource Center -> File Management page. For example, the file name is test.sh, and the command to call the resource in the script is sh test.sh;
6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.

• Set dependencies between tasks: Click the plus sign on the right of the task node to connect the task; as shown in the figure below, task Node_B and task Node_C execute in parallel, When task Node_A finished execution, tasks Node_B and Node_C will execute simultaneously.

  

• Delete dependencies: Click the "arrow" icon in the upper right corner , select the connection line, and click the "Delete" icon in the upper right corner , delete dependencies between tasks.

  

• Save workflow definition: Click the "Save" button, and the "Set DAG chart name" window pops up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to global parameters), click the "Add" button to finish workflow definition creation.

  

For other types of tasks, please refer to Task Node Type and Parameter Settings.

Workflow Definition Operation Function

Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown below:

The following are the operation functions of the workflow definition list:

• Edit: Only "Offline" workflow definitions can be edited. Workflow DAG editing is the same as Create Workflow Definition
• Online: When the workflow status is "Offline", used to make workflow online. Only the workflow in the "Online" state can run, but cannot edit
• Offline: When the workflow status is "Online", used to make workflow offline. Only the workflow in the "Offline" state can be edited, but cannot run
• Run: Only workflow in the online state can run. See 2.3.3 Run Workflow for the operation steps.
• Timing: Timing can only set to online workflows, and the system automatically schedules to run the workflow on time. The status after creating a timing setting is "offline", and the timing must set online on the timing management page to make effect. See 2.3.4 Workflow Timing for timing operation steps
• Timing Management: The timing management page can edit, online or offline and delete timing
• Delete: Delete the workflow definition
• Download: Download workflow definition to local
• Tree Diagram: Display the task node type and task status in a tree structure, as shown in the figure below:

Run the Workflow

• Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button to make workflow online.

• Click the "Run" button to pop up the startup parameter setting window, as shown in the figure below, set the startup parameters, click the "Run" button in the pop-up box, the workflow starts running, and the workflow instance page generates a workflow instance.

Description of workflow operating parameters:

  * Failure strategy: When a task node fails to execute, other parallel task nodes need to execute this strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks execution, and terminate the entire process
  * Notification strategy: When the process is over, send the process execution result notification email according to the process status, options including no send, send if sucess, send of failure, send whatever result
  * Process priority: The priority of process operation, divide into five levels: highest (HIGHEST), high (HIGH), medium (MEDIUM), low (LOW), and lowest (LOWEST). When the number of master threads is insufficient, high priority processes will execute first in the execution queue, and processes with the same priority will execute in the order of first in, first out;
  * Worker group: The process can only be executed in the specified worker machine group. The default is `Default`, which can execute on any worker
  * Notification group: select notification strategy||timeout alarm||when fault tolerance occurs, process result information or email will send to all members in the notification group
  * Recipient: select notification policy||timeout alarm||when fault tolerance occurs, process result information or alarm email will be sent to the recipient list
  * Cc: select notification policy||timeout alarm||when fault tolerance occurs, the process result information or warning email will be copied to the CC list
  * Startup parameter: Set or overwrite global parameter values when starting a new process instance
  * Complement: two modes including serial complement and parallel complement. Serial complement: within the specified time range, the complements are executed from the start date to the end date and N process instances are generated in turn; parallel complement: within the specified time range, multiple days are complemented at the same time to generate N process instances.
* You can select complement time range (only support continuous date) when executing a timing workflow definition. For example, need to fill in the data from 1st May to 10th May, as shown in the figure below:

![workflow-date](/img/new_ui/dev/project/workflow-date.png)

Serial mode: the complement execute sequentially from 9th May to 10th May, and the process instance page generates 10 process instances;

Parallel mode: The tasks from 9th May to 10th May execute simultaneously, and the process instance page generates 10 process instances;

Workflow Timing

• Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, make the workflow online, click the "timing" button , the timing parameter setting dialog box pops up, as shown in the figure below:

  

• Choose the start and end time. In the time range, the workflow runs at regular intervals; If not in the time range, no regular workflow instances generate.

• Add a timing that execute 5 minutes once, as shown in the following figure:

  

• Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.

• Click the "Create" button to create the timing. Now the timing status is "Offline" and the timing needs to be Online to make effect.

• Timing online: Click the "Timing Management" button , enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow makes effect regularly.

  

Import Workflow

Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, click the "Import Workflow" button to import the local workflow file, the workflow definition list displays the imported workflow and the status is offline.