FineBI version
Functional changes
5.1.10
-
5.1.11
When it is not a component alert, the "Text Preview Component" button is not displayed
5.1.12
When the component alert task is executed, the tasks are executed one by one according to the user
When users make components, they often analyze data outliers to guide business development.
However, the efficiency of manually finding outliers is too low, and users expect that the project will proactively notify relevant personnel after outliers appear.
Through the early warning judgment in the timed scheduling task, it is possible to actively push the abnormal value of the component to the user, which is convenient for timely processing/optimization.
1) "Alarm Judgment" only supports table components in BI templates, and does not support chart components or non-BI templates.
2) "Warning Judgment" supports setting early warning conditions for the result fields involved in the analysis in the component.
2) "Early Warning Judgment" supports "Email Notification" and "Client Notification".
The administrator logs in to the data decision system and clicks "Manage> Task Schedule > Add a Task", as shown in the following figure:
Set the "Task Name" and "Default User Group", click "OK", and click "Next", as shown in the following figure:
For details of scheduling objects, see: Scheduled Task Setting Steps
This article only describes the settings related to the "early warning judgment" task.
setting item
Precautions
object type
"BI Template" must be selected, otherwise the "Alarm judgment" task cannot be set
Choose a template
"Alarm judgment" is only valid for the table component in the dashboard, please select the dashboard with the table component
Scheduling result
Not checked by default
1) If it is not checked, according to the data permission of the owner of the component, determine whether to send an alert to the entire user group
2) If it is checked, it will be judged whether to send and alert to a certain user according to the respective data permissions of the members of the user group
After checking this button, different data results can be sent to different users according to the set row and column permissions .
For details of the scheduling period, see: Scheduled Task Setting Steps
execution frequency
In order to ensure the efficient availability of early warning tasks, it is recommended that the scheduling period of early warning tasks be no less than 1 hour.
execution condition
premise
Select "Warning Judgment"
select components
1) The component options include all table components with data permissions in the dashboard, sorted by component creation date.
2) A task can only make early warning judgments for one form component, and does not support multiple selections
3 ) When the component has been selected, add the warning condition, switch the component at this time, the warning condition will be cleared
Note: "Alarm Judgment" only supports table components in BI templates, and does not support chart components or non-BI templates.
Warning condition
Supports selection of result fields for table components, including dimensions and metrics
1) Dimensions
Displays grouped result values and other ungrouped original values
The date field is the original value grouped by year-month-day
The same fields are displayed in the order in which they are displayed in the analysis area
2) Indicators
Displays the result value, excluding the total row and the total within group row
3) Result filters, table properties, and hidden fields do not support settings
condition invalid
1) Reason for failure
When the field is lost, the field will be marked in red and it will prompt "The current field has been lost"
When the corresponding user does not have the permission for this field, the field will be marked in red and it will prompt "No permission for this field"
Note: When the grouping type of the field is changed, it will not affect the execution of the user's warning task.
If the corresponding warning conditions can still be matched before and after the grouping is changed, the corresponding warning will still be triggered.
2) Condition type
Or condition: a single warning condition is invalid, does not affect other conditions, and still takes effect
And condition: If there is an "and" type of early warning condition in the scheduled task that fails, the scheduling task fails to execute, and prompts "The warning condition is invalid and the task execution fails".
The user can set to check the alert notification in two ways: "Email Notification" and "Client Notification".
For details on file processing, see: Scheduled Task Setting Steps
notification method
E-mail notification
theme
If not filled, the default content is: task name
content of email
If not filled, the default content is:
The set warning condition (dimension name, indicator name + corresponding condition) triggers the warning, please check it in time: link (the preview link of the dashboard, you need to log in to view)
Body preview component content
It is selected by default, and after "Text preview component content" is checked :
1) If "Text preview template content" is checked at the same time , the component content will be displayed first in the text, followed by the template content.
2) If "Use Attachment" is checked at the same time , the component content will be displayed in both the email body and the attachment
3)
Versions prior to 5.1.11, if "Alarm judgment" is not checked in the scheduling cycle, even if "Text preview component content" is checked, there will be no component related content in the received email.
5.1.11 and later, if "Alarm judgment" is not checked in the scheduling cycle, the "Text preview component content" option will not be displayed.
Client notification
content
5.1.12 and later BI projects, when the warning task is executed:
First, determine whether the warning condition is abnormal (such as field permission loss, field loss, etc.).
If the warning condition is abnormal, the warning task fails to execute.
If the warning condition is normal, the warning task continues to execute.
After the early warning conditions are judged to be normal, the corresponding early warning judgments are performed in sequence according to the task user group.
If the execution of user A is abnormal, it will be skipped, and the skipped user will be marked in the task execution details.
If user B executes successfully, an early warning notification will be sent.
Execute in sequence until the task execution is completed, and the failure of a single user to execute does not affect the remaining users.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy