Wiki source code of Create Scheduler Event
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
9.1 | 1 | Table of contents: |
| |
3.1 | 2 | |
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| |
9.1 | 7 | The template defines **what** will be in the report, while the scheduler determines **when** and **to whom** it will be delivered. |
| |
3.1 | 8 | |
| |
9.1 | 9 | In this guide, we'll walk through the basic steps of using Reporting in ThingsEye , and create a report template with automated delivery configured for two different customers. |
| |
3.1 | 10 | |
| |
5.1 | 11 | = **1. Create the report template** = |
| |
3.1 | 12 | |
| |
5.1 | 13 | **默认你已知晓如何创建报告模板，如果不清楚请查阅这个WIKI：[[Create report>>doc:Main.Report Guide.WebHome]]** |
| |
3.1 | 14 | |
| 15 | |||
| |
5.1 | 16 | ---- |
| |
3.1 | 17 | |
| |
5.1 | 18 | = **2. Scheduling the report for customers** = |
| |
3.1 | 19 | |
| |
5.1 | 20 | **正确调度的要点** |
| 21 | |||
| 22 | 为确保正确生成报告并包含准确的数据，您必须指定： | ||
| 23 | |||
| 24 | * **报告收件人** – 将接收生成报告的用户（例如，经理或客户）。 | ||
| 25 | * **用户帐户** – 将用于生成报告的帐户。这定义了应用于报表的数据范围和权限。 | ||
| 26 | |||
| 27 | 例： | ||
| 28 | |||
| 29 | * 如果报告应仅包括**客户 A** 拥有的设备，则必须在计划报告时将**用户**字段设置为属于客户 A 的用户的电子邮件地址。同样，要为**客户 B** 收件人安排报告，请在**用户**字段中使用客户 B 用户的电子邮件地址。 | ||
| 30 | |||
| 31 | **这可确保报告仅显示该特定用户可访问的设备和数据。** | ||
| 32 | |||
| |
3.1 | 33 | ---- |
| 34 | |||
| |
7.1 | 35 | == **2.1 Scheduling a report for CustomerA users** == |
| |
3.1 | 36 | |
| |
5.1 | 37 | 首先，我们将为所有客户 A 用户设置自动发送报告。 该报告将代表该客户的管理员 Alec 生成。 |
| 38 | |||
| 39 | * 转到“**报告**”页面上的“**计划**”选项卡。 | ||
| 40 | * 点击右上角的“**+ 计划报告**”以创建新的计划程序事件。 | ||
| 41 | |||
| |
6.1 | 42 | [[image:1757991254381-634.png||height="721" width="1107"]] |
| |
5.1 | 43 | |
| 44 | ---- | ||
| 45 | |||
| 46 | * 在**计划**对话框中，提供以下详细信息： | ||
| |
6.1 | 47 | * 为您的日程安排事件指定一个清晰的**标题**，例如：(% style="background-color:inherit; color:inherit; font-size:inherit" %)Report for CustomerA |
| |
5.1 | 48 | * **事件类型** - 始终设置为**“创建报表**”。 |
| 49 | * **报告模板** – 选择之前创建的每日设备警报报告模板。 | ||
| |
6.1 | 50 | * **用户** – 指定将代表其生成报告的用户帐户：**Alec@thingseye.io** （Alec— 客户 A 管理员）。 |
| |
5.1 | 51 | |
| |
6.1 | 52 | [[image:1757991512124-527.png||height="723" width="1110"]] |
| |
5.1 | 53 | |
| 54 | ---- | ||
| 55 | |||
| 56 | * 设置**收件人**： | ||
| 57 | ** 在“**收件人**”字段中，单击**新建**以创建新的收件人组。 | ||
| 58 | *** 输入通知接收方组的**名称**。 | ||
| 59 | *** 选择**客户用户**筛选器。 | ||
| 60 | *** 将**客户**设置为**客户 A**。 | ||
| 61 | *** 单击“**添加**”。 | ||
| 62 | |||
| |
6.1 | 63 | [[image:1757991797040-630.png||height="723" width="1111"]] |
| |
5.1 | 64 | |
| 65 | ---- | ||
| 66 | |||
| |
6.1 | 67 | * **通知模板**和发送方式： |
| 68 | ** 选择现有通知模板（定义报告的传递方式）并对其进行编辑。 | ||
| 69 | ** 将**电子邮件**添加为**与 Web** 一起的传递方式。单击“**下一步**”。 | ||
| 70 | ** 添加将附加 **PDF 报告**的**电子邮件通知**的**主题和正文**文本。单击“**保存**”。 | ||
| |
5.1 | 71 | |
| |
6.1 | 72 | [[image:1757991868588-546.png||height="722" width="1112"]] |
| 73 | |||
| 74 | [[image:1757992829865-745.png||height="722" width="1112"]] | ||
| 75 | |||
| 76 | [[image:1757992985183-979.png]] | ||
| |
7.1 | 77 | |
| 78 | ---- | ||
| 79 | |||
| 80 | = **3. Set up the schedule** = | ||
| 81 | |||
| 82 | * ((( | ||
| 83 | Go to the **Schedule** tab. | ||
| 84 | ))) | ||
| 85 | * **Start time** – set the date and time of the first run. | ||
| 86 | * **Time zone** – choose the applicable time zone. | ||
| 87 | * Enable **Repeat**: | ||
| 88 | ** **Interval** – select **Daily**. | ||
| 89 | ** **End date** – set an end date or leave blank for ongoing delivery. | ||
| 90 | * Finally, click “**Create**” to save and apply the scheduler event. | ||
| 91 | |||
| 92 | Now, every day at the scheduled time, all Customer A users will automatically receive a report with the latest information about their device alarms. | ||
| 93 | |||
| |
8.1 | 94 | [[image:1757994096517-904.png||height="720" width="1118"]] |
| 95 | |||
| 96 | |||
| 97 | ---- | ||
| 98 | |||
| 99 | = **3. Scheduled events result** = | ||
| 100 | |||
| 101 | Each user from customerA receives their own individual report containing only the entities they have access to. | ||
| 102 | |||
| 103 | The system automatically sends the reports daily at the scheduled time, without any manual intervention. | ||
| 104 | |||
| 105 | At the time specified in the scheduled events, all users of Customer A will receive notifications along with the generated report on their device alarms. | ||
| 106 | |||
| 107 | Notifications will be delivered through two channels: | ||
| 108 | |||
| 109 | **~1. Web UI notification** | ||
| 110 | |||
| 111 | * A notification about the generated report will appear in the ThingsEye Web UI. | ||
| 112 | * Tenant Users can open the report directly within the ThingsEye interface. | ||
| 113 | |||
| 114 | (% class="box" %) | ||
| 115 | ((( | ||
| 116 | **Important:** | ||
| 117 | |||
| 118 | * Only Tenant Users can view generated reports directly in the ThingsEye Web UI. | ||
| 119 | * Customer users do not have access to reports in the Web UI — they can only receive them through **Email** or **Slack**. | ||
| 120 | If your recipients are customer users, make sure at least one of these delivery channels is selected. | ||
| 121 | ))) | ||
| 122 | |||
| |
9.1 | 123 | [[image:1757994928716-266.png||height="373" width="1098"]] |
| |
8.1 | 124 | |
| 125 | ---- | ||
| 126 | |||
| 127 | **2. Email notification** | ||
| 128 | |||
| 129 | * An email will be sent to the user with the subject and message you configured in the notification template. | ||
| 130 | * The email will have the report attached as a PDF file, which can be opened and viewed in the browser or downloaded. | ||
| 131 | |||
| 132 | [[image:1757995049919-870.png||height="670" width="1095"]] |