This is a features in progress. It means that it is not intended for production use. The feature is not finished. It is not stable. The implementation may contain bugs, the configuration may change at any moment without any warning and it may not work at all. Use at your own risk.
MidPoint 4.2 and later
Here we describe configurable dashboard and report, which is generated from a dashboard.
For whole sample please see dashboard-system-status.
Dashboard is new configurable object in midpoint, which show basic information about state of Midpoint. Dashboard contains name, display with label and widgets.
In 4.2 dashboards are shown automatically when defined. Since 4.3 there is a need for configuration to define which dashboards should be shown in the left (sidebar) menu. The configuration is show bellow:
Following configuration available since 4.3
The example above show how to configure dashboards to be shown in the left (sidebar) menu. Property display defines the name of the link which is shown in the menu. If it isn't defined, the display property of referenced DashboardType is used. Property configurableDashboardRef is used to reference specific DashboardType. If it isn't defined, midPoint ignores the whole configuration. For visibility settings, since 4.3 use visibility property in configurableUserDashboard instead of visibility in DashboardType.
We have two kinds of widgets, widget for objectCollection and widget for objectType.
Widget contains three basic variable.
Display properties of the widget. Variables:
|label||String||Displayed name of Widget.|
|String||Defaul color of background for widget.|
icon -> cssClass
CssClass for widget icon for example "fa fa-user".
|cssStyle||String||CssStyle for widget for example "color: #444 !important" for change of font color.|
Data which widget display. We have two kinds of data for objectCollection or for objectType. Variables:
Type of widget content data source. It is an identifier that specifies the type of the information (content) of the widget. This specifies type of data source for the widget content. This is enumeration type and posible values is objectCollection (content of widget is based on object collection), auditSearch (content of the widget will be based on data from special object collection with audit trail search) and object (content of the widget will be based on data from a single object)
|Specification of an explicit or implicit object collection that will be used as data source for the view. Contains variable collectionRef, which is reference to object collection is displayed in widget.|
Specification of a single object as a widget data source.
Example of widget data source for object collection:
Example of widget data source for object type:
Presentation define how will be data presented. We define four basic kind of presentation percentage (50%), separated with slash (5/10), separated with "of" (5 of 10) and only value (5). Presentation contains three variables.
First is dataField, which is properties of a specific widget data field. Note that the order of dataField elements is NOT significant. The field order is given by specific presentation style. Variables for dataField:
Type of the field. We support value 'value' and 'unit' now. 'value' is data field, which define displaying basic information, so number. "unit" define units for number.
Expression that produces value to display in the field.
For fiedType "value", we define new type of expression ProportionalExpressionEvaluatorType "proportional" with variable style. Variable style is enumeration type with value "percentage" (for example 50%), "value-slash-domain" (for example 5/10), "value-of-domain" (for example 5 of 10) and "value-only" (for example 5).
Next presentation variable is variation. Conditional variation in the way how the widget is displayed. Variations may change colors or icons of the widget based on a condition. Variables for variation:
Condition for the variation. The variation will be active if the condition evaluates to true.
|Display properties to apply in case that the condition is true. Those display properties specify only those presentation aspects that are different from the usual presenation. This is supposed to be merged with the primary display properties of the widget. E.g. if the variation only changes widget color, only color needs to be specified here. Icon and other styles are taken from the primary widget display properties.|
Condition can get three variables:
|Name||Type||Description||sourceType in data of widget|
Integer stat (statistic) entry. This entry contains stat value, together with domain value.
|Collection<String>||Colection of policy situations.||objectCollection|
|base on displayed object in widget||Processed object.||object|
Last variable of presentation is view, this variable is processed for report and we will look on it below.
Example of presentation:
You can see basic configuration for objectCollection on Object Collection. For dashboard we can use policyRule with policyTreshold for define some policySituation. Example of object collection for resource, which have status UP:
Variable domain is a set of object that is "all the things" for this collection. For example collection of "up resources" will have a domain "all resources". In this example we use policyRule with policySituation, which we can check in variation of widget presentation. When policyTreshold is met policySituation from policyRule is presented in variation. policyThreshold have two important variables for us, lowWaterMark and highWaterMark.
lowWaterMark is lower bound of the threshold. Lowest value for which the policy rule is activated. The policy rule will be triggered for all values starting from this value up until the high water mark (closed interval). If no low water mark is specified then the policy rule will be activated for all values up to the high water mark. Policy rule with a threshold that does not have any water marks will never be activated.
highWaterMark is upper bound of the threshold. Highest value for which the policy rule is activated. The policy rule will be triggered for all values starting from low water mark up until this value (closed interval). If no high water mark is specified then the policy rule will be activated for all values that are greater than or equal to high water mark.
Both variables are WaterMarkType type, which contains variables count and percentage.
We have special object collection for widget, which use audit records. You have to define sql select for audit records in object collection for audit search.
Object collection for audit records variable auditSearch and it have variables:
|SQL query for audit records. Defines which audit records belong to the collection.|
|SqlQuery for audit records. Defines a set of object that is "all the things" for this collection.|
|Defines what old records will be displayed.|
When we create new dashboard, than we can see it in midpoint gui. Next screenshot is displayed dashboard-system-status.
You may generate HTML report from the dashboard. Following code shows how to do it.
Some export configuration (for example html) create report with table of widgets and tables for objects from each widget and variable showOnlyWidgetsTable define that created report contains only table for widgets. For report is important view variable in widget presentation. Specifies a view for report of an object collection that is the result of the widget. Defines columns of table in report. When we don't use view, report will be contained default columns. In expression of column you can use variable 'object' which represent searched object or object defined in tag path. For more information about view configuration please see Views.
Definition of view is EXPERIMENTAL. It works only for some case, some parts are hardcoded, untested or do not even work at all. Use at your own risk. But it is perhaps best not to use this at all until the code stabilizes.
Final view is result of merging of defaultView in objectCollection object, view in dashboard for current widget and view in report for same type of objects as is in widget. Example of view in report:
Example of usecases
For whole sample please see dashboard-system-status.