Configuration of the Missing Original Policy for Personalized Charts
You can configure the missing original policy to retain or drop the personalized charts.
The following property sets missing original policy choices relating to personalized charts.
be.agent.dashboard.mal.missing.original.element.loading.policy
To understand how to set this property, you must first understand what happens when a Dashboard user personalizes a chart, for example by applying a filter to it.
Suppose a Dashboard user personalizes a chart called SaleStats by filtering it to show Western region data.
At the back end, the dashboard agent copies SaleStats and stores details for the user’s personalized chart in the internal database.
Suppose that a developer then deletes or edits the original SaleStats chart, and restarts the application.
(The developer in this example would delete or update only the chart itself, and not the chart’s metric or data source. If a metric or data source are deleted from the project, errors are thrown.)
Next time the user logs on to Dashboard, what will happen? It is possible that the user’s personalized chart will continue to work correctly, but it is also possible that the project changes might result in some problem, perhaps due to related changes such as a missing referenced datasource or metric, for example.
When the Dashboard user logs on, the dashboard agent to which that client is connected reviews that user’s settings and notes that the user has personalized the original SaleStats chart that was deleted (or edited). The agent then acts according to the missing original policy that you had set, using the following dashboard agent property:
be.agent.dashboard.mal.missing.original.element.loading.policy
The following sections explain the effect of the policy values: drop, retain, and exception (the default).
Drop Policy
If set to drop, the dashboard agent drops the personalized chart. The agent writes a log message indicating that it could not find original element SaleStats for the user’s personalized chart. (It does this every time the dashboard user logs on.)
Retain Policy
When set to retain, then the agent retains the personalized chart. The Dashboard user is not aware of any change, unless there is a problem in displaying the chart. For example, exceptions may occur due to unresolvable child references.
Exception Policy
When set to exception, the dashboard agent throws an exception immediately when the user logs on, and displays a message to the Dashboard user indicating that their role is unusable. The user can log on using a different role, if one is available, or must contact their system administrator. The administrator can delete the personalized chart in the agent’s file system.