In a manually triggered workflow, all nodes must be manually triggered, and cannot be scheduled. Therefore, you do not need to specify a parent node or output for a node in a manually triggered workflow.

Create a manually triggered workflow

  1. Go to the DataStudio page.
    1. Log on to the DataWorks console.
    2. In the left-side navigation pane, click Workspaces.
    3. In the top navigation bar, select the region where the target workspace resides. Find the target workspace and click Data Analytics in the Actions column.
  2. On the left-side navigation submenu, click the Manual business process icon.
    You can click the Show icon icon in the lower-left corner to show or hide the left-side navigation submenu.
  3. On the Manual business process tab, right-click Manual business process and select New business process.
  4. In the Create Workflow dialog box that appears, set the Workflow Name and Description parameters.
  5. Click Create.

GUI elements

User interface
The following table describes the icons and tabs on the configuration tab of a manually triggered workflow.
No. Icon or tab Description
1 Submit Commit all nodes in the manually triggered workflow.
2 Run Run all nodes in the manually triggered workflow. Nodes in this workflow do not have dependencies, and therefore they can be run at the same time.
3 Stop running Stop all running nodes in the manually triggered workflow.
4 Publish Go to the Deploy page. On this page, you can deploy specific or all nodes that are committed but not deployed to the production environment.
5 Go to operations Go to the Operation Center page.
6 Box selection Draw a box to select a group of nodes to form a node group.
7 Refresh Refresh the configuration tab of the manually triggered workflow.
8 Automatic Layout Sort the nodes in the manually triggered workflow.
9 Zoom in Zoom in the directed acyclic graph (DAG) of the manually triggered workflow.
10 Shrink Zooms out the DAG of the manually triggered workflow.
11 Query Search for a node in the manually triggered workflow.
12 Full screen Displays the configuration tab of the manually triggered workflow in the full screen.
13 Display engine information/Hide engine information Show or hide engine information.
14 Process Parameters Set parameters for the manually triggered workflow. Parameters set on this tab takes priority over those set on a node configuration tab. If the same parameter is set for both the workflow and a node, the parameter setting on the Workflow Parameters tab takes effect.
15 Operation History View the operation records of all nodes in the manually triggered workflow.
16 Version View the deployment records of all nodes in the manually triggered workflow.

Composition of a manually triggered workflow

Note We recommend that you create no more than 100 nodes in a manually triggered workflow.
A manually triggered workflow can contain a variety of nodes. After you create a manually triggered workflow, you can create nodes in the workflow. For more information, see Overview.
  • Data integration

    In the Manual business process section, click Data Integration under a manually triggered workflow. All the Data Integration nodes in the workflow appear.

    Right-click Data Integration under the manually triggered workflow. Choose New > Offline synchronization to create a batch sync node. For more information, see Batch Sync node.

  • MaxCompute
    Notice The MaxCompute folder appears under a manually triggered workflow only after you bind a MaxCompute compute engine to the current workspace on the Workspace Management page. For more information, see Compute Engine section.
    The MaxCompute compute engine allows you to create Data Analytics nodes, such as ODPS SQL, SQL Snippet, ODPS Spark, PyODPS, ODPS Script, ODPS MR, and PyODPS 2 nodes. You can also create and view tables, resources, and functions.
    • Data Analytics

      Click MaxCompute under the manually triggered workflow and right-click Data Analytics to create a data analytics node. For more information, see ODPS SQL node, SQL script template, ODPS Spark node, PyODPS node, Create a PyODPS 3 node, ODPS Script node, and ODPS MR node.

    • Table

      Click MaxCompute under the manually triggered workflow and right-click Table to create a table. You can also view all the tables created for the current MaxCompute compute engine. For more information, see Table.

    • Resource

      Click MaxCompute under the manually triggered workflow and right-click Resource to create a resource. You can also view all the resources created for the current MaxCompute compute engine. For more information, see Resource.

    • Function

      Click MaxCompute under the manually triggered workflow and right-click Function to create a function. You can also view all the functions created for the current MaxCompute compute engine. For more information, see Function.

  • EMR
    Notice The EMR folder appears under a manually triggered workflow only after you bind an E-MapReduce compute engine to the current workspace on the Workspace Management page. For more information, see Compute Engine section.
    The E-MapReduce compute engine allows you to create Data Analytics nodes, such as EMR Hive, EMR MR, EMR Spark SQL, EMR Spark, EMR Shell, EMR Spark Shell, EMR Presto, and EMR Impala nodes. You can also create and view EMR resources.
    • Data Analytics

      Click EMR under the manually triggered workflow and right-click Data Analytics to create a data analytics node. For more information, see EMR Presto node, EMR HIVE node, EMR SPARK SQL node, EMR SPARK node, and EMR MR node.

    • Resource

      Click EMR under the manually triggered workflow and right-click Resource to create a resource. You can also view all the resources created for the current E-MapReduce compute engine.

    • Function

      Click EMR under the manually triggered workflow and right-click Function to create a function. You can also view all the functions created for the current E-MapReduce compute engine.

  • Algorithm

    Click the manually triggered workflow and right-click Algorithm to create an algorithm. You can also view all the PAI nodes created in the current manually triggered workflow. For more information, see Machine Learning experiment node.

  • General

    Click the manually triggered workflow and right-click General to create relevant nodes. For more information, see OSS Object Inspection node, for-each node, do-while node, MERGE node, Branch node, Assignment node, Shell node, Zero-load node and Cross-tenant collaboration node.

  • UserDefined

    Click the manually triggered workflow and right-click UserDefined to create relevant nodes. For more information, see Create a Data Lake Analytics node and Create an AnalyticDB for MySQL node.