Using Notification to push data to WeCom groups allows the system to notify users who have not uploaded store data daily, reminding them to submit data.
This document explains how to send notifications via email.
Store data should be submitted daily. If the responsible person fails to submit data, the system will automatically send a reminder via email.
For example, the system identified that Rachel, the responsible person of the H store, failed to submit data on June 5th and automatically sent a notification email to Rachel.
Identify stores and responsible persons who have not submitted data for the day based on daily sales data and store names, and use the Parameter Assignment node to output the information as parameter values.
Obtain the email addresses of those who need to be notified using the company’s user information table and the list of responsible persons who have not submitted data, and use Parameter Assignment to output them as parameter values.
Use the Notification node to send emails about the missing store data to the responsible persons.
Prior to task configuration, you are required to set up the email sender in FineDataLink. For details, see Mailbox.
You can download the example data: Daily_Sales_Summary.xls, Store_Name_Summary.xlsx, User.xls.
1. The Store_Name_Summary table records information of responsible persons of different stores, as shown in the following figure.
2. The Daily_Sales_Summary table records the total daily sales data of each store, as shown in the following figure.
3. The User data table records basic information of the responsible persons, including their email addresses, as shown in the following figure.
1. Drag a Parameter Assignment node onto the page and configure it to extract the information of stores and responsible persons that do not appear in the Daily_Sales_Summary table on the current day from the Store_Name_Summary table. This operation is to retrieve the information of stores and the responsible personnel who have not submitted data that day, as shown in the following figure.
The SQL script is as follows:
select Store, Responsible_Personfrom `fdldemotest`.`Store_Name_Summary`where Store not in ( select distinct Store from `fdldemotest`.`Daily_Sales_Summary` )
2. Set a parameter Store whose values are the obtained store names. This parameter will be used in the notification title.
Set a parameter Name whose values are the obtained responsible persons. This parameter will be used as the filtering condition for obtaining the email addresses of recipients.
1. Drag in a Parameter Assignment node and configure it to obtain the recipients' email addresses based on the Name parameter (whose values are the responsible persons who have not unsubmitted sales data) set in the "Retrieving Recipients and Store Information" section for subsequent email notifications, as shown in the following figure.
select * from `fdldemotest`.`User`where Name in ('Name')
Set a parameter Email, which can be used in the Notification Object field for email delivery, as shown in the following figure.
Drag in a Notification node, select Email from the drop-down list of Notification Channel, set the sender, tick Custom Recipient in Notification Object, enter the parameter ${Email}, and then fill in Sales data of the ${Store} store has not been submitted in the Subject input box, as shown in the following figure.
Save and run the task. The page is shown in the following figure.
The received email is as shown in the following figure.
Click Publish to publish the task to Production Mode, as shown in the following figure.
To ensure daily scheduled execution, you can set a scheduling plan, as shown in the following figure.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy