Diagram Types for Visualizing Statistics
There are several diagram types available for visualizing statistics.
Bar Chart
A bar chart can be used to visualize comparisons between measurements. The actual measurement of the column ElementValue and the identifier for column ElementName are used to label the diagram.
Figure 33: Bar Chart Example
Pie Chart
A pie chart can be used to visualize the measurements as a percentage of the base measurement. The actual measurement of the column ElementValue and the identifier for column ElementName are used to label the diagram.
Figure 34: Pie Chart Example
Line Diagram
A line diagram can be used to visualize a data sequence over a specified time period. The time axis is scaled in proportion to the time scale given in the statistic definition. The number of measurements in the line diagram results from measurement runs to archive given in the statistic definition. Click with the mouse on a point of measurement and a tooltip showing the measurement is displayed.
Figure 35: Line Diagram Example
Traffic light
A traffic light diagram can be used to visualize the state of the system. The state is indicated by the color. The threshold factors given in the statistic definition determine when which status is reached.
| Color | State |
|---|---|
| Green | correct |
| Yellow | acceptable |
| Red | unacceptable |
The actual measurement of the column ElementValue and the identifier for column ElementName are used to label the diagram.
Figure 36: Traffic Light Example
Tachometer
A tachometer diagram can be used to visualize the state of the system in more detail than in a traffic light diagram. The base measurement is also displayed. The state is indicated by the color. The threshold factors given in the statistic definition determine when which status is reached. The actual measurement of the column ElementValue and the identifier for column ElementName are used to label the diagram.
Figure 37: Tachometer Diagram Example
Thermometer
A thermometer diagram can be used to visualize the state of the system in more detail that in a traffic light diagram. The state is indicated by a color scale on the side of the diagram. The threshold factors given in the statistic definition determine when which status is reached. The actual measurement of the column ElementValue and the identifier for column ElementName are used to label the diagram.
Figure 38: Thermometer Diagram Example
Table
This diagram type can be used to visualize the measurements in table form. Enter a number of archived measurements runs in the statistic definition, to present the data over a specified time period.
Figure 39: Table Example
Examples of Statistic Definitions
Example 1:
The number of people in the company should be displayed in the statistics. This statistic should be calculated daily. The statistics definition could look like:
| Statistic: | CountEmployees |
| Display name: | Number of employees |
| Description: | Finds the number of employees in the company on a daily basis. |
| Calculation schedule: | Calculate statistics |
| Measurements query: |
select 'Employees' as ElementName, count (*) as ElementValue from Person |
To display the statistics in the Manager in the category Employees | Info system, the following menu item is created:
| Menu item: | Person.InfoSystem.CountEmployees |
| Item type: | Statistics |
| Sort order | 1 |
| Statistic: | Number of employees |
| Diagram type: | thermometer |
The menu item is assigned to the application "Manager" and to an application role and then it can be displayed in the Manager.
Figure 40: Displaying the statistics in the Manager
Example 2:
The number of external employees in the company should be displayed in the statistics. This statistic should be calculated weekly. If more than 20% of employees in the company are externals, the info system should display the state as acceptable instead of a correct. If more than 80% are externals the state should be unacceptable.
| Statistic: | CountExternalEmployees |
| Display name: | Number of external employees. |
| Description: | Find the number of external employees in the company on a weekly basis. |
| Calculation schedule: | Calculate weekly statistics |
| Measurements query: |
Select 'Employees' as ElementName, Count (*) as ElementValue from Person where IsExternal = 1 |
| Base measurements query: |
Select 'Employees' as ElementName, Count (*) as ElementValue from Person |
| Threshold green: | 0.2 |
| Threshold red: | 0,8 |
To display the statistics in the Manager in the category Employees | Info system, the following menu item is created:
| Menu item: | Person.InfoSystem.CountExternalEmployees |
| Item type: | Statistics |
| Sort order | 2 |
| Statistic: | Number of external employees. |
| Diagram type: | Traffic light |
The menu item is assigned to the application "Manager" and to an application role and then it can be displayed in the Manager.
Example 3:
The number of employees, for which the current user is entered directly as manager, should be represented in a statistic. Restrictions to the values for the current user are made though a condition.
| Statistic: | CountEmployeesPersonHead |
| Display name: | Supervised employees |
| Description: | Finds the number of employees for which the manager is responsible on a daily basis. |
| Calculation schedule: | Calculate statistics |
| Measurements query: |
select XObjectKey as ElementObjectKey, 'Employees' as ElementName, Count (*) as ElementValue from Person where IsExternal = 1 Group by XObjectKey |
| Condition: |
ElementObjectKey in (select XObjectKey from Person where uid_PersonHead = '%useruid%') |
Configure the web project in the Web Designer, to display statistics in the Web Portal info system.
Example 4:
Internal and external employees, which the current user supervises as department manager, should be represented in a statistic. Departments are added here separately to determine clear results for displaying the measurement because a department manager might be responsible for more than one department.
| Statistic: | PersonCountInternalExternal_By_Department |
| Display name: | Number of internal and external employees |
| Description: | Finds the number of internal and external employees per department on a daily basis. |
| Calculation schedule: | Calculate statistics |
| Measurements query: |
select d.XObjectKey as ElementObjectKey, 'Internal' as ElementName, count(p.uid_person) as ElementValue from Department d Left Outer Join Person p on p.UID_Department = d.UID_Department and p.IsExternal = 0 Group By d.XObjectKey UNION ALL select d.XObjectKey as ElementObjectKey, 'External' as ElementName, count(p.uid_person) as ElementValue from Department d Left Outer Join Person p on p.UID_Department = d.UID_Department and p.IsExternal = 1 Group By d.XObjectKey |
| Condition: |
ElementObjectKey in (select d.XObjectKey from Department d join helperheadorg hpo on d.UID_Department = hpo.UID_Org where hpo.UID_PersonHead = '%useruid%') |
| Aggregate function | SUM |
Configure the web project in the Web Designer, to display statistics in the Web Portal info system.
Example 5:
Ten employees with the highest risk index should be found and displayed in a statistic. They should be sorted by measurement unit.
| Statistic: | Top10ActivePersonByRiskIndex |
| Display name: | Top 10 active employees by risk index |
| Description: | Find ten active employees with the highest risk indexes on a daily basis. |
| Calculation schedule: | Calculate statistics |
| Measurements query: |
select top 10 p.InternalName as ElementName, Round(100 * IsNull(p.RiskIndexCalculated, 0), 0) as ElementValue, p.XObjectKey as ElementObjectKey, ROW_NUMBER() over (order by IsNull(p.RiskIndexCalculated, 0) desc, p.InternalName) as ElementOrder from Person p where p.IsInActive = 0 order by ElementOrder |
Configure the web project in the Web Designer, to display statistics in the Web Portal info system.
Extending the Launchpad
Extending the Launchpad
The Launchpad is the central tool for starting administration tools and One Identity Manager configuration tools. Use the Launchpad to check the existing One Identity Manager installation and start One Identity Manager tools for executing individual tasks.
The Launchpad can be customized. You can define your own menu items and action for the Launchpad in the Designer.
You can control how and where menu items are displayed in the Launchpad. You use the menu hierarchy and the different types of menu items to do this. For more detailed information about the structure of a menu hierarchy and the individual menu items and their properties, see User Interface Navigation.
One Identity Manager supplies a list of Launchpad actions that you can use to start applications. You can also start your own applications over the Launchpad.
Figure 41: The Launchpad User Interface
Recommendations on extending the Launchpad
- To create a new category in the Launchpad navigation on the left-hand side, use the menu item of type "Menu category". The items are shown with their display text.
- To group tasks in the Launchpad main view, use the menu item of type "task category" The items are shown with their display text.
- Apply the entry types "Tasks", "Fixed menu item" or "Data dependent menu item" to each Launchpad task. The items are shown with their display text and description.
- Specify the order for displaying the menu items.
- To display the task status, enter an overlay icon definition on the menu item in VB.net syntax. Use the NavigationNodeState class.
Syntax:
public NavigationNodeState(string state, string imageUidOrName, string description)
public NavigationNodeState(string state, string imageUidOrName, string description, bool enabled, bool visible, int count)
Table 172: Parameter of the script NavigationNodeState Parameter
Description
State
Status, returned, for example "Info", "Ok", "Error", "Warning".
ImageUidOrName
UID or nameof the icon to display.
Description
Text, which is displayed as a tooltip.
enabled
Specifies whether the start button for the action is set or not.
visible
Specifies whether the task is shown or not.
count
Number of affected objects.
Calling example:
Value = New NavigationNodeState("Ok", "QBM-33228392E9863141A9306B38ADF3D502", #LD("Project is completed.")#)
Value = New NavigationNodeState("Error", "QBM-a486f0eabf674392bbbdf8572453258c", #LD("Project is not completed.")#)
- You can use the condition to specify whether the task is only available for a direct database connection or a connection over an application server. To do this, use the variable SessionType.
Examples of conditions
Only direct database connection: '%SessionType%' = 'Direct'
Only connection through application server:'%SessionType%' = 'AppServer'
If no condition is given, the task is always available.
- If an action is going to be run from a task, link an Launchpad action to the menu item.
This displays the Start button for the task. The Launchpad action's description is displayed in the button's tooltip.
To extend the Launchpad
- Create a new menu item for the Launchpad.
- Select the category User Interface | User interface navigation | Launchpad in the Designer.
- Start the User Interface Editor using Edit navigation for application 'Launchpad' in the task view.
- Create the menu item.
- Assign the menu item to the application "Launchpad".
- Assign the permissions group menu items to the "QBM LaunchPad".
- Assign the Launchpad actions to the menu items.
- Select the category User interface | Launchpad actions in the Designer.
- Select the menu item View | Select table relations... and enable the table DialogTree.
- Select the Launchpad action and assign the action to the menu item on the Menu items tab.
Related Topics
Launchpad Actions
Launchpad Actions
One Identity Manager supplies a list of Launchpad actions that you can use to start applications. You can also start your own applications over the Launchpad.
At the start an application, you can pass calling parameters, tasks and task parameters which the application can identify. Variable are permitted in this case. Supported are:
- Environment variables with the syntax %variable%
- Navigation variables with the syntax %variable%
- Columns of the object passed in $ notation.
To display Launchpad actions
- Select the category User Interface | Launchpad actions in the Designer.
- Select the Launchpad action The following master data is required for a Launchpad action.
Table 173: Properties of an Action Properties Description Description Detailed description of the action. The description is displayed in the tooltip. Executable file Full name of the executable file. Execution parameter Additional calling parameter for starting the application. Action Name of the action. Administrative context Specifies whether the application can only be started by an administrator. The application expects authentication as an administrator. Task Task that must be passed additional as a start parameter.
Task parameter Additional parameter for the task.