Notifying Multiple People with One Notification Message

Application Scenario

You have set an alert threshold for key business indicators for monitoring. You want the system to quickly alert responsible personnel via channels such as WeCom and DingTalk if the threshold is reached to shorten the business decision cycle.

• You want to use channels such as Email and WeCom to distribute information and notify members of specific tasks. 

• In the example of this document, the system alerts multiple people via a single notification message, as shown in the following figure.

Note:

For the solution where each notification message corresponds to one person, see Sending Individual Messages to Multiple Recipients in a Single Batch.

Implementation Method

This solution is implemented using the Parameter Assignment, Conditional Branch, and Notification nodes.

1. Use the Parameter Assignment node to extract data of the notification content and the responsible personnel, output the extracted data as parameter values, and pass these parameters to the Conditional Branch node.

Note:

This document uses WeCom as an example of notification via a group chatbot. The data of the responsible personnel must be the user ID or mobile number of the WeCom member, so that the WeCom group chatbot can correctly recognize the member. For details, see the "WeCom Chatbot" section in Notification.

2. Use the Conditional Branch node to determine whether notification content exists: If it exists, run the Notification node to remind the responsible person; otherwise, skip the Notification node.

3. Configure a scheduling plan to execute the task periodically.

Effect: On March 31, 2023, reminders were sent to the responsible persons who had not uploaded the store sales data. Thereafter, a reminder will be automatically sent to the WeCom group every day if the data of a store is not uploaded.

Scenario Description

Store managers are required to upload the day’s sales data to the headquarters by 6:00 PM daily. If the data of a store is not uploaded on the day, the store manager is expected to receive a reminder in the WeCom group at 7:00 PM.

You can download the example data: Daily_Sales_Summary_1.xls, Store_Name_Summary_1.xlsx.

1. The data in the Store_Name_Summary_1 table is shown in the following figure.

In the example of this document, the WeCom group chatbot configured in the Notification node identifies members and sends notifications via their user IDs, where the names of store managers are in one-to-one correspondence with their user IDs in WeCom.

In practical scenarios, the Store_Name_Summary_1 table must include the user IDs or mobile numbers of the responsible personnel to enable the WeCom group chatbot to identify group members and send notification messages in subsequent steps.

2. The data in the Daily_Sales_Summary_1 table is shown in the following figure.

Solution Description

1. Drag a Parameter Assignment node and configure it to extract the data of stores that failed to submit sales data on the day and their corresponding responsible personnel, output the extracted data as parameters, and pass these parameters to the Conditional Branch node.

Note:

The data of the responsible personnel must be the user ID or mobile number of the WeCom member, so that the WeCom group chatbot can correctly recognize the member. For details, see the "WeCom Chatbot" section in Notification.

2. Use the Conditional Branch node to determine whether to run the Notification node based on the parameters: If the sales data of a store is not uploaded today, run the Notification node to remind the responsible person to upload data; if data of all stores is uploaded today, skip the Notification node.

3. Configure a scheduling plan to run the task daily, ensuring reminders are sent daily to responsible persons who have not uploaded store data.

Filtering Data and Outputting it as Parameter Values

1. Create a scheduled task.

2. Add a Parameter Assignment node and configure it to filter data, obtaining the information of stores whose data has not been uploaded today and the responsible personnel, as shown in the following figure.

select Store, Responsible_Person
from
 `fdldemotest`.`Store_Name_Summary_1`
where
  Store not in (
    select
      distinct Store
    from
      `fdldemotest`.`Daily_Sales_Summary_1`
  )

Click Data Preview, as shown in the following figure.

In the example of this document, the values in the Responsible_Person column correspond one-to-one with the user IDs of WeCom members.

2. Set two parameters, with the names of stores whose sales data has not been uploaded and the responsible persons as parameters values, respectively.

Note:

 For the configuration of each setting item in the Parameter Assignment node, see Parameter Assignment.

Configuring the Conditional Branch Node

1. Add a Conditional Branch node and connect it to the Parameter Assignment node; add a Notification node and a Virtual Node, and connect them to the Conditional Branch node, as shown in the following figure.

2. Configure the Conditional Branch node: If the sales data of a store is not uploaded today, run the Notification node to remind the responsible person in the WeCom group to upload data; if data of all stores is uploaded today, run Virtual Node, as shown in the following figure.

Configuring the Notification Node

For descriptions of each configuration item, see Notification. The following figure shows the specific settings.

Setting a Timed Scheduling Plan

Configure the scheduled task to run daily at 7:00 PM in Scheduling Plan, as shown in the following figure.

Effect Display

If the sales data of a store is not uploaded on the current day, a reminder will be sent in the WeCom group, as shown in the following figure.