DataWorks:Create a data push node

Step 1: Create an SQL query node or an assignment node

A data push node receives the output parameters of its ancestor nodes and uses the output parameters as the input parameters of the data push node to push data to specific destinations. Before you create a data push node, you must create an SQL query node or an assignment node as the ancestor node of the data push node.

Step 2: Create a data push node

1. Double-click the created workflow. On the configuration tab of the workflow, click the icon. Then, click Data Push in the General section. In the Create Node dialog box, configure parameters and click Confirm. The following table describes the parameters.

   Parameter	Description
   Node Type	The type of the node. Select Data Push from the drop-down list.
   Path	The path that stores the node. The path must be the same as that of the node created in Step 1.
   Name	The name of the data push node. You can specify the name based on your business requirements.

2. Double-click the created data push node. The configuration tab of the node appears.

3. Add the SQL query node created in Step 1 as the ancestor node of the data push node. In the right-side navigation pane of the configuration tab of the data push node, Click Properties. In the Dependencies section, select Node Name from the drop-down list below Parent Nodes, enter the name of the SQL query node in the field, and then click Create.

4. In the Resource Group section of the Properties tab, configure the Resource Group parameter. You must select a serverless resource group that was created after June 28, 2024, which is the release date of the data push feature. If the resource group was created before June 28, 2024, submit a ticket to upgrade the resource group.

5. Add the outputs parameter of the SQL query node created in Step 1 as the input parameter of the data push node. On the Properties tab, click the drop-down arrow to the right of Input and Output Parameters. Click Create to the right of Input Parameters. Then, enter a parameter name in the Parameter Name column and select the outputs parameter from the drop-down list in the Value Source column. Close the Properties tab.

6. Configure the Destination, Title, and Body parameters for the data push node.

   1. Destination: Select a destination from the Destination drop-down list. If no destination is available, click Create Destination to create a destination. The following table describes the parameters for creating a destination.

      Parameter	Description
      Type	Select a push channel. DingTalk, Lark, WeCom, Microsoft Teams, and Email are supported.
      Destination Name	Enter a name based on your business requirements.
      WebHook	Enter the chatbot of DingTalk, Lark or WeCom or webhook URL of Microsoft Teams. You must obtain the chatbot and webhook URL of the related push channel in the corresponding platform. You can also obtain the SMTP of Email in the corresponding platform. Note For more information about how to obtain the webhook URL of Lark, see Use the webhook trigger. For more information about how to obtain the webhook URL of Teams, see Create incoming webhooks with Workflows for Microsoft Teams.

      Create and manage a destination in DataService Studio:

      1. Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose Data Analysis and Service > DataService Studio. On the page that appears, select the desired workspace from the drop-down list and click Go to DataService Studio.

      2. In the lower-left corner of the Service Development tab of the DataService Studio page, click the icon. On the page that appears, click the Destination Management tab. On the tab, you can click Create Destination to create a destination and manage existing destinations. For more information, see the Create a webhook destination section in the "Data push" topic.

   2. Title: Enter a title for the data push node in the related field based on your business requirements.

   3. Body: Click Add and select Markdown or Table to configure the content that you want to push. For more information, see the Configure the content to push section in the "Data push" topic.

      Note

      • Take note of the following items when you use an SQL query node as the ancestor node of the data push node:

        • If you select Markdown to configure the content to push in the Body section, you can directly use the field names that are queried by the SQL query node as placeholders to obtain the output parameters of the SQL query node. The placeholders must be in the ${Field name} format.

        • If you select Table to configure the content that you want to push in the Body section, you can add the fields that are queried by the SQL query node as input parameters to obtain data.

      • If you use an assignment node as the ancestor node of the data push node, you must use the names of the input parameters of the data push node as placeholders to obtain the output parameters of the assignment node. The placeholders must be in the ${Input parameter name} format.

7. In the top toolbar, click the icon to save the configurations.

Step 3: Test data push flows in the workflow, commit the workflow, and then deploy nodes in the workflow

After you configure all data push flows in the workflow, double-click the workflow. On the configuration tab of the workflow, test all data push flows. If all data push flows run as expected, commit the workflow and deploy nodes in the workflow.

1. On the configuration tab of the workflow, click the icon to run the workflow.

2. After appears next to all nodes in the workflow, click the icon to commit the workflow.

3. In the Commit dialog box, select the nodes that you want to commit, enter a description, and then select Ignore I/O Inconsistency Alerts.

4. Click Confirm.

5. Deploy nodes. For more information, see Deploy nodes.