Branch node

Create a branch node

1. Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.

2. Hover over the icon and choose Create Node > General > Branch Node.

   Alternatively, you can open the target workflow, right-click a blank area, and choose Create Node > General > Branch Node.

3. In the Create Node dialog box, enter a node name and select a path.

4. Click Confirm.

5. Define the branch logic.

   1. On the Definition page, click Add Branch.

   2. In the Branch Definition dialog box, configure the parameters.

      Parameter	Description
      Condition	Specifies the condition for the branch. Keep in mind the following rules: You can only use Python comparison operators to define the logical condition. If the expression evaluates to true at runtime, the corresponding branch condition is met. If an error occurs while parsing the expression at runtime, the entire branch node fails. You can use global variables and parameters defined in the node context in branch conditions. For example, ${input} can be an input parameter defined on the branch node.
      Associated Node Output	Defines the output used by downstream nodes for dependencies: Downstream nodes use this output to establish dependencies. When a branch condition is met, downstream nodes that depend on the associated output run, provided their other upstream dependencies are also met. If a branch condition is not met, the downstream nodes that depend on the corresponding output do not run. DataWorks sets these nodes to the Not run because the branch condition is not met state.
      Description	Enter a brief description of the branch. For example, you can define two branches with the conditions ${input}==1 and ${input}>2.

      The following example shows how to configure the Associated Node Output parameter.

      For example, a branch node has two downstream nodes named qqqq and wwww. When the branch condition is 1, the logic of the qqqq node runs. When the branch condition is 2, the logic of the wwww node runs. When you configure the branch node, you can set the node outputs as required. For example, if the output for Branch 1 is 1234 and the output for Branch 2 is 2324, both are used as output names for this branch node. The downstream qqqq node must reference the output name 1234, and the wwww node must reference the output name 2324.

   3. Click OK.

      After you add a branch, you can Edit or Delete it.

      • Click Edit to modify the branch settings. DataWorks updates the related dependencies accordingly.

      • Click Delete to remove the branch. DataWorks also updates the related dependencies.

6. In the right-side pane, click Scheduling Settings to configure the scheduling properties for the node.

   After you define the branch conditions, DataWorks automatically adds the output names to the Output Name of Current Node section on the Scheduling Settings > Scheduling Dependency tab. Downstream nodes can use these output names to declare dependencies.

   Note

   • Because the dry run property propagates to downstream nodes, do not place self-dependent tasks on a branch path. For more information about whether to inherit the dry run property from an upstream node, see Inherit the dry run property from upstream nodes.

   • If you create a dependency by drawing a line to establish a node context and the output name does not appear in Scheduling Settings, you must manually enter the output name.

7. Commit and deploy the node.

   1. Click the icon on the toolbar to save the node.

   2. Click the icon on the toolbar to commit the node.

   3. In the Submission dialog box, enter a Change Description.

   4. Click OK.

   If you use a workspace in standard mode, you must deploy the task to the production environment after you commit it. Click Deploy Task in the upper-left corner of the top menu bar. For more information, see Deploy tasks.

8. View scheduled tasks.

   1. In the upper-right corner of the editor, click O&M Personnel to open the production environment's Operation Center.

   2. View the scheduled tasks that are running. For more information, see Manage scheduled tasks.

   To view more details about scheduled tasks, click Operation Center in the top menu bar. For more information, see Operation Center overview.

Example: Downstream node dependency

Supported Python comparison operators