Task Schedule- FineBI Help Document FineBI Document

Recent Updates: July 19, 2022

I. Overview

1. Version

FineBI version	JAR package	New functions
5.1	2020-08-04	After the task schedule configured, delete users, roles, departments, and positions from Basic settings in User Management and perform the task schedule again. fanruan.log file displays an error message indicating the error level
5.1	2020-08-04	The Run Monitoring Tab displays the tasks in progress

2. Application scenarios

Enterprise users may face situations where reports need to be generated and published on a regular basis, and they have to do repetitive things on a regular basis to get the reports they need.
Send questionnaires to customers regularly, and customers fill in the relevant information and submit it to the database.

3. Function overview

FineBI supports users to set daily, monthly, quarterly, annual and other tasks easily and quickly.
No extra work is required. After a task schedule is set, the server automatically completes the task at the specified time.
Generates reports periodically, converts data periodically, sends emails, SMS messages, and mobile client information periodically, specifies the report generation directory, and views the report generation results on the Web.

II. Function entrance

There are two entrances for setting task schedule.

1. Timer (op=fs)

2. Timer (Independent timer)

For JAR 2020-09-02 or later, the administrator can access http://IP: port number /webroot/decision/timer, enter the administrator password, and use timer to access the timer.

Note: When independent timer is used to access the timer, the global setting of periodic scheduling is not supported, and the running failure warning cannot be configured. As shown below:

Ⅲ. Implementation

The following figure shows the execution process of task schedule:

1) When a task schedule starts, the system checks the conditions. If the conditions are true, a snapshot is generated. If the conditions are false, the system determines whether restart is enabled.

If restart is enabled, the task schedule starts again in a delayed manner.
If no task restart is set, the task schedule is terminated, and the task execution fails.

2) If the snapshot is generated successfully, the attachment is sent. If the generation fails, determine whether to restart the task.

If restart is enabled, the task schedule starts again in a delayed manner.
If no task restart is set, the task schedule is terminated, and the task execution fails.

3) Attachment sending

If the attachment is successfully sent, the task schedule is successfully executed and the task ends.
If the attachment fails to be sent, the stask schedule fails and the task ends.

2022-07-19_12-04-24_译图.png

Ⅳ. Index

.	Sub Chapter	Introduction	Reference file
task schedule	task settings	A detailed introduction to the four operation steps when setting a scheduled task	Task Schedule Setting
	task management	Monitoring and management of the running process and results of timed scheduling tasks	Task Schedule Management
	Conditional judgment	Perform a verification judgment before executing the scheduled task, if the conditions are not met, it will not be executed or the verification will be executed again after a delay	Task Schedule with conditional judgement
	Component Alert	After abnormal values appear, the project will proactively notify relevant personnel	Task Schedule Support Component Alerts
	Expression setting	Timing scheduling period, supports the use of cron expressions	Expression setting
	Supported formulas	Introduce in detail the formulas that can be used and their usage in the process of setting timed scheduling tasks	Task Schedule Support Formulas
	generated attachment	After the scheduled task is executed, the generated attachment	Task Schedule Generated Attachments
Scheduled file processing	Timing scheduling supports a variety of file processing methods. Different processing methods need to meet different preconditions, and the task setting process is also different.
	Timing calculation	Timing calculation is the process of generating the result report ( .cpr file) and other attachments, it is checked by default and cannot be changed	-
	Mounting platform	After the scheduled task is executed, mount the generated result report to the directory of the data decision system	Scheduled mount platform
	Platform Notification	After the scheduled task is executed, push the generated result report to the users of the data decision system	Scheduled platform notifications
	E-mail notification	After the scheduled task is executed, push the generated result report and attachments to the mailboxes of the users of the data decision system	Scheduled email notifications
	SMS notification	After the scheduled task is executed, send a text message to the mobile phone of the user of the data decision system to remind the user to check	Scheduled SMS notifications
	Client notification	After the scheduled task is executed, push the generated result report to the App, HTML5 client, DingTalk, WeChat and other clients of the user of the data decision system	Scheduled client notification - APP notification WeChat regularly pushes messages Dingding regularly pushes messages
	FTP upload attachment	After the scheduled task is executed, upload the result report and attachments generated by the task to the server through FTP	Schedule FTP to upload attachments regularly
	SFTP upload attachment	After the scheduled task is executed, upload the result report and attachments generated by the task to the server through SFTP	Schedule SFTP to upload attachments regularly
	Custom attachment handling	After the scheduled task is executed, customize the upload method of the result report and attachment	Custom upload files to disk Custom upload files to FTP server
	print documents	After the scheduled task is executed, the set printer will print out the content of the result report.	-
Simple example of timing scheduling	Daily simple example of timed tasks	Generate data for a fixed period of time every day	Daily simple example of timed tasks
	Monthly and annual reports of timed tasks	Count the sales performance of each branch in a fixed period of time every month, or count the sales performance of each branch at the end of the year	Monthly and annual reports of timed tasks
	Automatically fill in regularly	Regularly implement operations such as loading, summarizing, and filling in the database	Automatically fill in regularly
	Scheduled sending of filling tasks	Regularly push the reporting template to the employees, and the employees manually enter the data and submit it	Scheduled sending of filling tasks
	Email body preview report content picture display plugin	After installing this plugin, the email body will preview the report content in image format by default.	Email body preview report content picture display plugin
	Timer export task supports line engine plugin	After installing the secondary plug-in, the scheduled task supports the line engine, and can export attachments in Word, Excel, and PDF formats	Timer export task supports line engine plugin
Timing Scheduling Authority Control	Timed task email sending enables different people to send different content	Send emails with different content to different people on a regular basis	Timed task email sending enables different people to send different content
Timing Scheduling Authority Control	Scheduled task CPR file content permission control	Each user only sees his own information. For example, at the end of each month, the user checks his salary	Scheduled task CPR file content permission control
Scheduled FAQ	Frequently Asked Questions about Scheduled Scheduling	Introduce some errors and solutions in timed scheduling tasks	Frequently Asked Questions about Scheduled Scheduling
	Scheduled time zone exception prompt	The time zone of the engineering server is inconsistent with the time zone of the browser, resulting in deviations in the execution time of scheduled tasks	Scheduled time zone exception prompt
	Scheduled log migration	Reasons and Solutions for the Disappearance of Scheduled Logs	Scheduled log migration

Ⅴ. An error message is displayed when deleting a task schedule

On 2020-08-04 and later JARs, after the task schedule is configured, the user, role, department and position in the "Default User Group" of the Basic Setting are deleted in User Management, and the task schedule is executed again, and the fanruan.logfile displays an error level.

The specific error reporting logic is shown in the table below.

Note: For an introduction to 'Custom Users' see: Basic Setting

Delete content	Specific scenarios	Error alert
User deleted	Platform user： Delete one user: one line with an error Deleting 200 users: one line with an error indicating that all 200 users have been deleted Deleting more than 200 users: one line with an error indicating that only 200 users have been deleted Custom Users: All users that do not match in the field are reported as errors, up to 200	Format: Some users in the default user group do not exist, please check the timed scheduling task: [pp(pp) Example: Some users in the default user group do not exist, please check the timed scheduling task: [Sun Jiancheng (Billy), Wang Guoqiang (Cherry)
Role deleted	Deleting a role: one line with an error Deleting multiple roles: one line with an error	Some roles in the default user group do not exist, please check the task schedule.
Department deleted	Deleting a department: one line with an error Deleting multiple departments: one line with an error	Some departmental roles do not exist in the default user group, please check the task schedule.
Position deleted	Deleting a position: one line with an error Deleting multiple positions: one line with an error	Some departmental roles do not exist in the default user group, please check the task schedule.

Already the First

Already the Last

Helpful
Not helpful
Only read

售前咨询电话

400-811-8890转1

在线技术支持

在线QQ：800049425

热线电话：400-811-8890转2

总裁办24H投诉

热线电话：173-1278-1526

文档反馈

鼠标选中内容，快速反馈问题

鼠标选中存在疑惑的内容，即可快速反馈问题，我们将会跟进处理。

不再提示

10s后关闭

Task Schedule