Overview
Version
| FineBI Server Version | Functional Change |
6.0 | / |
Application Scenarios
If you are an enterprise user, you may face such a situation where reports need to be generated and published regularly, and have to do repetitive tasks regularly to obtain the required reports.
You may need to send questionnaires to customers regularly, and submit them to the database after customers fill in relevant information.
Functions
FineBI allows you to easily and quickly set up tasks, such as daily, monthly, quarterly, and annual reports.
You just need to set scheduled tasks, and the server will automatically complete the set tasks at the specified time.
FineBI supports scheduled report generation, scheduled data conversion, and scheduled sending of emails, SMS, and app notifications. It also allows specifying templates to generate directories, and viewing report generation results with a Web browser.
Entrance
1. Timer (op = fs)
The admin logs into FineBI, and clicks Manage > Task Schedule to go to the Task Schedule interface.
The admin can access http://{IP}:{port number}/webroot/decision/timer, and enter the admin's account and password to directly access scheduled tasks.
Note:
Execution
The execution process of the scheduled task is shown below:
1. When a scheduled task starts, first a conditional judgment is performed. If the judgment is true, a snapshot is generated. If the judgment is false, the system will check whether a restart has been set.
If restart is set, the scheduled task will be delayed to restart.
If restart is not set, the scheduled task will end directly, and the task execution will fail.
2. If the snapshot is generated successfully, the next step will be the attachment sending. If the generation fails, the system will check if task restart is set.
If restart is set, the scheduled task will be delayed to restart.
If restart is not set, the scheduled task will end directly, and the task execution will fail.
3. Attachment Sending
If the attachment is sent successfully, the scheduled task will be considered successful, and the task will end.
If the attachment fails to be sent, the scheduled task will fail and end.
Index
| Chapter | Section | Explanation |
Setting a Scheduled Task | Task Settings | Detailed introduction to the four operation steps when setting up scheduled tasks |
Task Management | Monitoring and management of execution process and results of scheduled tasks | |
Conditional Judgment | Perform a validation check before executing the scheduled task. If the condition is not met, the task will not be executed or the validation check will be executed again after delaying. | |
Component Warning | If abnormal values appear, the project actively notifies relevant personnel. | |
Expression Setting | Introduction to the cycle of the scheduled task. Supports using cron expressions. | |
Supported Formulas | Detailed introduction to the formulas (used during the process of setting scheduled tasks) and their usage | |
Generated Attachments | Attachments generated after the scheduled task is completed | |
File Processing in Task Schedule | Task Schedule supports multiple file processing methods which require different prerequisites. The task setting process is also different.
| |
Scheduled Calculation | Scheduled calculation is the process of generating result reports (CPR files) and other attachments, which is selected by default and cannot be changed. | |
Mounting Platform | After the scheduled task ends, the generated result report will be mounted to the directory of the decision-making platform. | |
Platform Notification | After the scheduled task ends, the system will push generated result reports to users of the decision-making platform. | |
Email Notification | After the scheduled task ends, the system will push generated result reports and attachments to the mailboxes of users of the decision-making platform. | |
SMS Notification | After the scheduled task ends, the system will send text messages to the mobile phones of users of the decision- making platform to remind them to check. | |
Client Notification | After the scheduled task ends, the system will push generated result reports to the App, HTML5 client, and other clients of users of the decision-making platform. | |
FTP Upload Attachment | After the scheduled task ends, you can upload result reports and attachments generated by the task to the server via FTP Upload Attachment. | |
SFTP Upload File | After the scheduled task ends, you can upload generated result reports and attachments to the server via SFTP Upload File. | |
Custom Attachment Processing | After the scheduled task ends, you can customize the upload method of result reports and attachments. | |
An Example of Task Schedule | Daily Reports of Scheduled Tasks | Generate data at a fixed time interval every day. |
Monthly and Annual Reports of Scheduled Tasks | Sales performance of each branch is recorded on a fixed time period every month, or at the end of the year. | |
Scheduled Data Entry | Scheduled operations of data loading, collection, and entry into the database | |
Scheduled Submission of Reporting Tasks | Push the reporting template to employees regularly, and employees need to manually enter and submit data. | |
Email Preview Report Content Image Display Plugin | After installing this plugin, the report content will be displayed in the email body in image format by default. | |
Permission Control of Task Schedule | Dynamic Email Sending | Regularly send emails with different content to different people. |
CPR File Content Permission Control | Users can only see their own information, for example, they can check their own salary at the end of each month. | |
FAQ of Task Schedule | Common Problems | Introduce some errors and solutions for scheduled tasks. |
Prompts for Abnormal Time Zones | The time zone of the engineering server is inconsistent with that of the browser, resulting in a deviation in the execution time of scheduled tasks. | |
