I. Overview
1. Version
| Report server version |
|---|
| 11.0 |
2. Function introduction
When selecting Report Templatein Task Schedule>Dispatcher Object>Object Type, after the scheduled task is executed, the report project%FR_HOME%/webapps/webroot/WEB-INFA directory will be generatedschedulefolder. The folder stores the Accessory Archive generated after the scheduled task is executed.
The content of attachments and email attachments generated by timed tasks can be different according to different users, so as to realize the distribution of corresponding user data reports to different users.
II.Folder hierarchy
1. JAR packages before 2020-01-15
JAR package before 2020-01-15, the hierarchy structure of the schedule folder is described in the following table:
| Level | Folder name | Remarks |
|---|---|---|
| Level one | schedule | -- |
| Level two | Scheduled task name | Example: GettingStartedEN |
| Level three | Task execution date | Example：2021-02-01 |
| Level four | Task execution time | Example：1458 |
| Level five | 「General result」or User name | If checked In addition to the general results, members of the default user group will receive individual resultsin「Dispatcher Object」, when executing a timed task, the selected user filtering will be implemented in the timed task template, and create a folder namedUsername naming. |
| Level six | Name all the parameters in「Set Parameter」 | If the Set Parameter is in the "Dispatcher Object"，itwill havethis folder. Naming rules: parameter names and values are connected by underscores, and different parameters are connected by semicolons. Example：Region_East China；time_2019-12-04 00:00 Note: The JAR package is 2020-03-25 and later, the naming rule is to randomly generate UUID |
| Level seven | Result file: Including result report (CPR or FRR), Doc, PDF, XLS, XLSX, PNG (required for mail) | If you check 「Clearing at the end of the task」 in the Dispatcher Object step, there will be no 「Result File」. |
2. 2020-01-15 and later JAR packages
JAR package after 2020-01-15, the hierarchy structure of the schedule folder is described in the following table:
Note: The JAR package is 2020-01-15 and after the schedule folder hierarchy, only the 「Level six」 is different from the previous version.
| Level | Folder name | Remarks |
|---|---|---|
| Level six | UUID | If the 「Set Parameter」 is in the Dispatcher Object, there will be this folder. Naming rule: no longer adopt the method of splicing parameters, but generate UUID Example：be918527-2ed8-4c6f-87bd-0e72df8522f5 Note: The relationship between UUID and the set parameters is stored in the fine_schedule_task_param table of FineDB. |
III. Example
1. JAR packages before 2020-01-15
1) If the Set Parameteris in the Dispatcher Object, the schedule folder structure is shown in the following figure:
2) If checked In addition to the general results, members of the default user group will receive individual resultsin「Dispatcher Object」, the schedule folder structure is shown in the following figure:
2. 2020-01-15 and later JAR packages
1) If the Set Parameter is in the Dispatcher Object, the schedule folder structure is shown in the following figure:
2) If checked In addition to the general results, members of the default user group will receive individual resultsin「Dispatcher Object」, the schedule folder structure is shown in the following figure:
Previous：Timed Tasks Push Messages To APP
