[Index]
Tip
Use the Action search to navigate Automate
Overview
Dashboards are a collection of configurable widgets on a single page that can serve as a default landing page and can also be made available on a user menu. The widgets can allow for the easy access of frequently used tasks and for a quick view - as a counter, table or chart - of data in the system.
Note
Where dashboard widgets show data, the hierarchy at which the dashboard containing the widget is displayed, will filter data values and counts accordingly in the respective widgets.
Dashboard fields showing the item hierarchy (similar to Located At) are updated only when a full sync runs. For example, if you've added users to the system and then moved them to a site, any charts, counters, or tables showing a count of users (at that site or at the system level), will only reflect the correct number of users once a full sync runs and not when simply refreshing the dashboard or widget in a real-time sync. In this case, until you run the full sync, the hierarchy fields for these users display on dashboard charts, tables, or widget counters as with no (empty) hierarchy value. See Dashboard Refresh.
Dashboards can also be accessed by URL links containing the dashboard name - in the following format:
/portal/#/admin/dashboard;name=<dashboard_name>
If <dashboard_name> contains spaces, use URL encoded spaces, e.g. :
/portal/#/admin/dashboard;name=Dashboard%20Call%20Groups
This link format allows support for cross-launching from portals where the name of the dashboard is known.
Administrator users with roles referring to access profiles that allow for the creation and update of dashboards, can design and add dashboards to menus. For details, see: the Dashboard Permissions section in Access Profiles.
Note
By default, administrators have permissions to modify their own menu layouts and dashboards. If the assigned menu layout or dashboard is at a higher hierarchy, it can be cloned and modified at the administrator's hierarchy.
Related topics
Conversion of landing pages to dashboards in v24.1
When upgrading to Automate release v24.1, existing landing pages in Automate are converted to dashboards; new data/Dashboard records are created from data/LandingPage records. Additionally:
Landing page welcome headers are converted to a Text widget using Markdown, with the header prefix as ## and the text prefixed with ###.
Landing page Sections are converted to dashboard Links widgets.
Where a landing page link setting had Set default Model Type enabled for a link, this setting is also enabled in the dashboard links widget for each corresponding link.
Long lists of links may result in a scrollbar showing on the widget. In this case, the number of links can divided into multiple widgets by modifying the converted dashboard.
Landing page Counters are converted to individual counters dashboard widgets, grouping 3 counters into a single widget at a time. The counters use Automate models as source.
The layout of the converted counter widgets can be modified as required.
Landing page chart Widgets are not converted.
Examples are:
These can be created and added as a dashboard chart widget if required - see: Automate Dashboards.
Saved searches have been moved to the user's Account page.
For default and custom landing pages in the system, the conversion process retains replaces any landing page indication LP suffix in the name with a dashboard equivalent Dashboard.
For other custom landing pages found on an upgraded system that included landing page conversion, the original landing page names are retained after conversion as instances of dashboards with the same name.
Where landing pages allowed a Condition to be set at section level, the converted Links dashboards only provide conditions for each individual link.
Where landing pages allowed a Condition to be set as well as a Condition at section level, the converted Links dashboards provide both conditions for each individual link - joined with a logical AND.
These dashboards allow for the same functionality as existing landing pages, but have an enhanced editing interface where for example a wide variety of chart widgets can be added to enrich dashboards. It is recommended that the dashboard conversions be inspected and edited if needed.
For details on dashboards, their maintenance and initial sync requirements after the addition of dashboard widgets, see: Automate Dashboards.
A new database and resource model for its data has also been added: Insights reporter resources (data/ReporterResource).
As a part of the landing page to dashboard conversion during upgrade, the following related elements are also migrated:
Tip
Use the Action search to navigate Automate
Overview
Administrators can manage dashboards via the Dashboards link that is a part of the Role Configuration on the Role Management dashboard.
Add or edit a dashboard
Automate provides several configuration options for working with dashboards.
Add or edit
Name: Display name of the dashboard
Description: Provide a description for the dashboard for the Dashboards list view.
Hide Time Picker: By default, a time picker is available to filter dashboard data by start and end date. Any selected dates are reset when you log out. You can't specify a date in the future. Select the checkbox to hide the time picker.
Hide Datasource Selector: This setting applies in the case where multiple instances of a dashboard data type is available. Not enabling the setting on a widget allows for selection of a data source instance and updates widget data based on the selected data source. Enabling the setting implies that the data source set on the widget is always used. Also used with "Insights Netflow" deployment option. For details, contact VOSS.
Default Date Range: Select this option to open the date range picker and to set up a default date range for the dashboard. This range will then apply to widgets on the dashboard that use the date range picker.
Clone: Use the toolbar Clone icon to create a copy of the dashboard you're viewing. The cloned dashboard opens with the breadcrumb name appended with the text, [CLONE], and contains all the widgets of the source dashboard. The cloned dashboard name is the same as the original source dashboard name and can be modified as required.
Note
Dashboards with the same name can be available at different hierarchies. When such a dashboard is referenced, this first one found higher up from the administrator user's login hierarchy is selected.
Refresh Dashboard: Used to update synced data on the dashboard to reflect any system data changes.
Note
Dashboard widgets each also provide a similar Refresh button when hovering over the top bar of the widget - similarly to refresh individual widget data.
Lock: Used to lock the arrangement of widgets
Dashboard Settings: Toggles (shows/hides) the dashboard name, description, and properties.
Undo: Reverts the dashboard to the state of the last unlock. So, if the lock has been used even once on the dashboard, the unlock will always return the dashboard to the state it was after it was unlocked, even if multiple changes were done since. If the dashboard was never locked, Undo will lock it, forcing the user to unlock and create a snapshot point. This snapshot is the same as the uploaded dashboard. Note that the Undo functionality is currently under review.
Export: Exports one or more instances. Refer to Bulk Export of Model Data. Exported dashboards can then be modified and imported at a required hierarchy via the Import menu.
Compact Grid: Automatically optimizes the arrangement of widgets on the dashboard, given their current size.
Paste Widget: Pastes a widget you have selected, using the Copy Widget option on the widget menu, into the current dashboard. This allows you to copy widgets between dashboards.
JSON Edit: Used for editing the dashboard data in JSON. For details, refer to Manage Items.
Export Dashboard Data: Used to export the data available in the widgets of a dashboard: in CSV or MS Excel format. The exported data contain header rows labelled with the friendly names of the data field names and is then available for off-line use.
Where multiple widgets are available on a dashboard, widget data is exported as either a CSV file or as a sheet in a MS Excel workbook. All the CSV files are archived in a .zip file. The export filenames follow the following convention:
Export_<dashboard-name>_data_<all|displayed>_<timestamp>.<zip|xlsx>
The available export options are determinded by the Data Source of the widgets on the selected dashboard:
If there is a widget with Data Source as Automate present, only two export options will be available:
This means that exported data will reflect the displayed records as per current Time Picker interval.
If all widgets have Data Source set to Automate Analyzed , Netflow or Assurance, there will be four export options:
Selecting an "All records" option will include all available data, regardless of the selected Time Picker interval.
Add or edit widgets
When a dashboard is added or updated, widgets can be added, removed or edited.
To add a widget, click the Add Widget toolbar icon; then, on the design form, either select the widget from the toolbar or from the provided list of icons:
To edit a widget on a dashboard, select the dashboard from the list and choose Edit from the widget's menu. The widget menu provides a number of operations.
Edit:
Clone:
Delete:
Copy Widget:
Export data:
Where a widget offers data in a compatible format, the Export data on the widget menu allows for a MS-Excel or comma-separated value (CSV) export to a file, as in the Number Status example below:
Status,Count Used-Utility,6 Cooling,35 Used,63 Reserved,106 Available,3850
Note
Note
Not all widget options and possible combinations are covered in this document. The widget refresh option can be used to inspect the impact of an option. For assistance in creating widgets, you can also contact VOSS support.
Where a widget resource references data over a time period (such as transactions), the widget interface provides a time picker control to indicate and change the interval for the data shown on the widget.
Dashboard sync and refresh
A real-time sync process is running to maintain Automate and Insights databases in sync. After upgrade to release 24.2, dashboard management is available after 30 minutes, since the scheduled delta-sync process initially carries out a full sync and thereafter an incremental resource sync.
See: Insights Analytics in the Platform Guide.
Important
Dashboard fields showing the item hierarchy (similar to Located At) are updated only when a delta sync runs. For example, if you've added users to the system and then moved them to a site, any charts, counters, or tables showing a count of users (at that site or at the system level), will only reflect the correct number of users once a delta sync runs and not when simply refreshing the dashboard or widget in a real-time sync. Until the delta sync runs, the hierarchy fields for these users display on dashboard charts, tables, or widget counters as with no (empty) hierarchy value. See Dashboard Refresh.
Manage value mapping
Automate provides options to allow for custom, alternative field values of resources to be displayed in chart widgets by using the Value Mapping field.
This optional value is applied during the design of a widget and is typically used to present a more user-friendly field value in a chart widget, for example, to map the value of Cisco Codec Mappings originally: 0 to mapped: No Media Established.
The Dashboard Value Mapping page (data model: data/DashboardValueMapping) is available to provider administrators and higher to add, delete and manage mappings. The model contains the default individual mapping value: NO MAPPING.
The design of a mapping allows for the selection of an evaluation operator to apply to the original value as an input condition and then to provide the replaced value in accordance with the evaluation operator test result.
Evaluation operators that can be applied to the original field values are:
Note
Examples:
Manage color mapping
Automate provides options to allow for custom, alternative display colors and icons of Automate Analyze resources to be displayed in table widgets by modifying the Field Type of the resource and by creating instances of a Dashboard Color Mapping. The mapping instance name is then selected in the Text Color Mapping and/or Cell Color Mapping dropdown lists under Table Options > Renderers when desiging a table widget.
The Field Type of the field needs to be set to one of:
Refer to the Format Type of the field in the Table topic above.
This optional mapped value is applied during the design of a widget and is typically used to present a more user-friendly color or icon in a table widget, for example, to map a range of field values to have a specified color.
The design of a mapping allows for the selection of an evaluation operator to apply to the original value as an input condition and then to render the replaced color in accordance with the evaluation operator test result.
Evaluation operators that can be applied to the field values are:
The Dashboard Color Mapping page (data model: data/DashboardColorMapping) or Color Mapping link on the MVS-RoleManagement-Dashboard dashboard is available to provider administrators and higher to add, delete and manage mappings.
Examples:
If a Dashboard Color Mapping instance exists that matches the Regex .*00.*, then render the text as color: #ff0011.
The Render section of a table widget has a field with Field Type set to "Text" and the Text Color Mapping dropdown selection is the created Dashboard Color Mapping.
The table then displays the text the matching text accordingly, acording the selected Dashboard Color Mode (Light/Dark) of the theme that is applied - see: Create a Theme in the Business Admin Portal. The example below shows the Light theme applied.
If a Dashboard Color Mapping instance exists that maps the Regex value Ani, with the color: #fff200 and this instance is applied (selected under Chart Options) to a chart showing user first names that start with An, then names starting with Ani will be rendered in the chart mapping color (example below for Light theme):
Tip
Use the Action search to navigate Automate
Overview
The dashboard widgets support the following chart types:
When a chart widget is selected, it is also possible to switch to another widget format during the edit and design process.
The chart type can be updated from the Widget Type drop down. Changes are reflected in real-time during the design of a widget or by using the widget's Refresh icon.
Chart widget data settings
The table describes the common list of data settings for chart widgets:
Chart widget example
As an example, consider the following column chart values, with charts illustrating various data and chart settings:
Title: CUCM User Departments
Resource: Cisco UCM User
Field Name: Department
Operation: Grouping Count
Shows a column chart with counts of grouped Cisco UCM User departments in columns.
Filter:
Filter:
Filter:
Sorts:
Chart Options:
The examples below show the chart with settings on some of the properties as not set or set, in the example above:
Tip
Use the Action search to navigate Automate
Counters are typically used to provide a quick count of a resource, and have the option to display a list view of the values when selecting the counter.
Note
Counter values reflect the hierarchy at which the counter is viewed.
Condition: The display of the widget on the dashboard can be controlled by entering a condition that resolves to boolean True or False, for example in accordance with enabled features, services, and devices as in the Global Settings. The conditions are in the form of system macros. See for example the macros listed under the Links topic below.
Data Source: Insights or Automate
Resource: only available for Insights
Fields: For Insights resources, one or more instances of Field Name can be selected in counters. These field names will then be shown as individual counters in a set of counters. An Operation can be selected for these in order to modify the counter.
For example, if a Field Type is "Text" and has duplicate values, and the Operation on the field is:
Alternatively, where Resource provides values for Field that have a Field Type of "Integer", additional Operation options are available that apply to integers, for example:
The User Overview dashboard counters can for example be inspected to see the application of operations on integer fields.
Counters can also for example show a count that is grouped by additional fields. Consider a counter with:
The counter displays the number of users as grouped by each Provider-Customer
When a counter widget is selected, it is also possible to switch to another widget format during the edit and design process. The Widget Type can be updated from the dropdown. Changes are reflected in real-time during the design of a widget or by using the widget's Refresh icon.
One or more Filters can be applied to a selected Field Name, using an Operation and Filter Value.
Examples for Resource = "Cisco UCM User":
Settings:
The resulting counter shows grouped counts of the first names of Cisco UCM users where the first name starts with "An" (case-sensitive).
If for Fields above, the Operation was "Count", then a single value of the total of all users with first name starting with "An" (case-sensitive) would display in the counter.
Settings:
Then:
Filters - Field Name: "userid", Operation: "LIKE (Case sensitive)", Filter Value: alf%.
The resulting counter shows a count (4 - see image below) of the userid's that start with "alf" (case-sensitive).
Or:
Filters - Field Name: "userid", Operation: "ILIKE (Case insensitive)", Filter Value: alf%.
The resulting counter shows a count (5 - see image below) of the userid's that start with "alf" (case-insensitive), which is larger, given data as in the example image of userids below.
Note
The Filter Value can contain % characters, indicating variable string values at the position of the % character. For example: %alf% will match norman.alfred; alf% will match alfred.norman and %alf will match norman.fredalf.
Type: only available for Automate resources. This is the selected model type (e.g. data/Countries). A Title, Icon, Field Display Policy, Condition and Configuration Template can also be applied to the selected model type.
Filters: For Insights resources, field names can be selected and a matching operator selected to apply to the name in order to filter a counter value (as in the example under Fields above). For Automate resources, see the topic Fixed and Configurable Filters in Counters and Links - that will then be applied when the counter is selected to open the filtered list view.
Counter Settings: a limit on the value can be specified, prefix and suffix text can be inserted for the value, as well as default values for empty groups.
Links are typically used to offer shortcuts to targets: data or URLs. The data is available from Automate models in the Type drop-down.
Link Text and Icon can be entered to display the link
Condition : a condition that evaluates to true or false, in Automate macro syntax, for example, for enabled features:
{{ macro.is_avaya_enabled }}
{{ macro.is_cisco_ccx_enabled }}
{{ macro.is_cisco_cucm_enabled }}
{{ macro.is_cisco_cucx_enabled }}
{{ macro.is_cisco_microsoft_enabled }}
{{ macro.is_cisco_webex_enabled }}
{{ macro.is_cisco_webex_teams_enabled }}
{{ macro.is_cisco_zoom_enabled }}
{{ macro.is_microsoft_enabled }}
{{ macro.is_pexip_enabled }}
{{ macro.is_session_border_control_enabled }}
{{ macro.is_voss_phones_enabled }}
{{ macro.is_zoom_enabled }}
Where widgets are not shown in accordance with the Condition evaluation of the widget, the dashboard arrangement is updated accordingly to auto compact the visible widgets.
Note
Fixed and configurable filters in counters and links
Fixed Filters
High-level administrators can add and modify pre-defined Fixed Filters to Counters and Links. This option also shows on design input forms and presents the same interface options as Configurable Filters.
These filters will always apply when the widget is used. Fixed filter results can however be filtered further by Configurable Filters.
Configurable Filters
When configuring a widget open the filter configuration dialog, where you can add one or more configurable filters.
Adding more than one filter using the Add option results in a logical AND of the filter application.
The table describes the Configurable Filters fields:
| Filter By | Attributes of the selected Type can be selected from the drop-down list. |
| Filter Type | Select the matching operator to apply when the attribute is matched to the Filter String value:
|
| Filter String | Select the value that the matching operator should match by. |
| Ignore Case | This checkbox defines whether to ignore the case of the Filter String value. |
Once you've applied the configurable filters, selecting the counter or link in the GUI triggers a pop up Filter dialog before rendering the list view, where you can apply or modify the filter before displaying the page related to the counter or link.
If a Filter String value is entered on Configurable Filters, this value can also then be accepted or modified in the Filter dialog.
The list view of the results footer row indicates that a filter has now been applied to the list and this filter can then be further modified and removed from the list view as usual. See Ordering Lists
Overview
Available menus and fields upon Data Source selection:
Automate Analyzed
Resource options available in accordance with the Insights database
Automate provides an additional list of Resource instances that can be used to represent trends on a widget. For details, see Automate Dashboard Trends Resources.
Fields: select fields from the resource to show in the table
Filters: filter field values from the table
Sorts: order the table (ascending, descending) by a selected field value
Automate: Model Type, Field Display Policy, Configuration Template
Assurance: if selected, options are available to choose a Data Source Instance, since multiple instances can be configured. A selection of these can then also be made if Allow Data Source Selection is enabled. For Arbitrator configuration, see: Voss Assurance Arbitrators.
Table Options are available for both data sources.
Drilldown options: see Reference: Drilldown Options and Conditional Syntax
Besides standard menu options, a displayed table can also show additional menu options in accordance with enabled features such as:
When a table widget is selected, it is also possible to switch to another widget format during the edit and design process. The Widget Type can be updated from the dropdown. Changes are reflected in real-time during the design of a widget or by using the widget's Refresh icon.
Table widget example with Select Query and Partition By
The example below shows a table widget configuration using an Automate Analyzed resource, with Select Query and Partition By operations on fields, as well as a Filter on one of the fields. Consider the following Data Settings:
In this case, sites and user first names are selected where first names are used to
Table widget example with drill-down
The example below shows a table widget configuration using an Automate Analyzed resource, the resultant output display and also a drill-down result.
Resource: Cisco CUC User
Fields:
Filters
Sorts: no sorting is done on any column.
Table Options
Other Renderers options:
A field on a table can also be modified if the Resource is Automate Analyze:
Format Type = Default: field type remains as defined (default)
Format Type = Text: field value rendered as text - allows for a default theme-related color mapping of text (Text Color Mapping) and table cell (Cell Color Mapping) to apply.
Contact VOSS if a custom color mapping is required.
The Font Size and Font Weight can also be set here if the Format Type of a field is Text.
Column Alignment: for text - to override the table alignment for the selected field.
Prefix and Suffix: for text and numbers - options to add a string prefix or suffix to the field value.
Format Type = Traffic Light: field value replaced by a "traffic light" colored icon - allows for default theme-related color mapping.
Format Type = Tick Cross: field value replaced by a "cross" (X) colored icon - does not allow for color mapping.
Format Type = Number: number-specific options are available:
Hide Column: hide the field column on a table (e.g. if the field is used for calculation, other purposes)
Note
By default, a number of table colours are matched with the current GUI theme. For details on these colours, see the Branding tab section under Create a Theme in the Business Admin Portal.
In particular:
Drill-down options
Output
The table shows 2 columns:
Drill-down result
Selecting a row link from the table shows the item as listed in the selected Drilldown Options.
Text widgets display text on a dashboard.
The input format can be either HTML or Markdown. The editor Preview menu option allows for a formatted preview of the text format in the Content input box.
Example Text widgets (HTML):
Example Text widgets (Markdown):
Text widgets can be used to create headings, for example:
Design:
Display:
Automate provides a set of dashboards, menu layouts, and field display policies that are used in two sample menu layouts - for use or customization as a Business Administration Portal menu layout to be added to a user's role.
Example dashboards - Business Admin role
Dashboard names grouped by sample menu layout names The following lists are the dashboard names grouped by the provided sample menu layout names.
Automate dashboard trends resources
For the Data Source: Automate Analyzed, Automate provides additional list of Resource instances that can be used to represent trends on a widget.
Note
Trends resources have the following properties:
The available trends resources and their properties are indicated below:
Filter options availability and definitions
The operators below are available as filter options for Insights resource field types:
Chart options availability and definitions
Note
By default, a number of chart colours are matched with the current GUI theme. For details on these colours, see the Branding tab section under Create a Theme in the Business Admin Portal.
In particular:
Chart Option Definitions:
Available Chart Options vary according to the chart type:
| Chart Option | Column Chart | Gauge Chart | Line Chart | Pie Chart |
|---|---|---|---|---|
| Series Limit | X | X | X | |
| Description | X | X | X | |
| Over Time | X | X | ||
| Interval | X | X | ||
| X Title | X | X | ||
| Y Title | X | X | ||
| Is Stacked | X | |||
| Stack Type | X | |||
| Numeric Precision | X | |||
| Is Horizontal | X | |||
| Is 3D | X | X | ||
| Show Labels | X | X | X | |
| Show Legend | X | X | X | |
| Gauge Label | X | |||
| Min | X | |||
| Max | X | |||
| Label Inside | X | |||
| Show Bands | X | |||
| Is Doughnut | X | |||
| Show Numbers | X |
Drill-down options and conditional syntax
Filter Options: apply to field value match of a selection of the chart or table data (IN, REGEX)
For example, if Filter Other Widgets is selected, then IN will match "Ann" exactly in other widgets and REGEX will match "Ann", "Anne", "Annie".
Drilldown Options: the behavior when selecting an item in a chart or table
None (default)
Filter Other Widgets: a selected drilldown item will update any other widget that also references the same data instance.
For example a drilldown on a CUC user table where this is enabled, will similarly impact widgets such as charts, counters and tables related to CUC users, so that these widgets will then reflect data from only the single user from the drilldown.
In the example below, the chart widget called CUCM User count by Dept has the Filter Other Widgets drilldown filter enabled, so that for example selecting a department from the chart also filters the CUCM Users count per site chart to only show users at sites belonging to the selected department. The department filter (here: department contains 'Cats Beauty') is also displayed when the filter is active.
Link to Another Dashboard
Used to open another existing dashboard during drilldown. A Dashboards dropdown shows to select the other dashboard. Navigation can then be carried out from the linked dashboard to the parent dashboard:
Launch Third-party URL
Conditional Drilldown
Provides a Conditional Drilldown input box into which a JSON formatted condition can be entered. For details on the format, see Conditional Drilldown Format below.
Drilldown Fields:
When selecting the Conditional Drilldown option, the condition needs to be entered in JSON format into the input box. This section provides syntax details and examples for this configuration.
If an item matching the condition is selected from the dashboard, the conditional drilldown is then carried out.
The JSON format is outlined below.
If conditions are all met
then carry out actions
else Defaults ("default...")
Structure:
{
"conditions": [],
"actions": [],
"defaultDrilldown": 1,
"defaultDashboardId": "",
"defaultUrl": "",
"defaultFilterFields": []
}
conditions:
conditions: list of conditions on rules.
rules:
rules: list of rules:
ruleid: "integer" - zero-based
field: "integer" - zero-based
Field order in the drilldown tab (0 base)
fieldType: "text", "integer" or "float"
operator: "==", "!=", "<=", ">=", "<", ">" or "regex"
operator: "==", "!=", "<=", ">=", "<", ">" or "regex"
value: value of the field; according to fieldType: "text", "integer" or "float"
actions:
List of actions:
drilldown: "integer"
dashboardid: "text"
The ID is available as dashboard_id URL parameter value when on a dashboard.
url: "text"
The value is a URL containing position variables for filterFields references, whose values in turn are substituted into the URL. The position variables are one based, for example:
"url": "https://{1}/ui/index.html?{2}"
refers to the first and second filterFields list entries, which in turn take the format
"filterFields": [0,1]
The value of the first filterFields entry is therefore for example substituted into the URL variable {1} above.
filterFields: list of fields ("integer" = index number)
Field order in the drilldown tab (0 base)
Defaults:
defaultDrilldown: "integer"
defaultDashboardid: "text"
defaultUrl: "text"
defaultFilterFields: list of fields ("integer" = index number)
Field order in the drilldown tab (0 base)
Drill-down to other widgets
Explanation:
JSON:
{
"conditions": [
{
"id": 0,
"name": "first_condition",
"type": "AND",
"rules": [
{
"ruleid": 0,
"field": 6,
"fieldType": "integer",
"operator": "!=",
"value": "0"
},
{
"ruleid": 1,
"field": 5,
"fieldType": "float",
"operator": "<=",
"value": "0"
}
],
"actions": [
{
"drilldown": 1,
"dashboardid": "",
"url": "",
"filterFields": [
0,
1,
3
]
}
]
}
],
"defaultDrilldown": 1,
"defaultDashboardId": "",
"defaultUrl": "",
"defaultFilterFields": [
0,
1
]
}
Drill-down to other dashboard
Explanation:
JSON:
{
"conditions": [
{
"id": 0,
"name": "first_condition",
"type": "OR",
"rules": [
{
"ruleid": 0,
"field": 1,
"fieldType": "text",
"operator": "==",
"value": "keller, texas"
},
{
"ruleid": 1,
"field": 4,
"fieldType": "text",
"operator": "==",
"value": "TX"
}
],
"actions": [
{
"drilldown": 2,
"dashboardid": "M2OQQMVN3IWI1O2P1686581558847Y2FRT98M8V24GS",
"url": "",
"filterFields": [
0,
1,
3
]
}
]
}
],
"defaultDrilldown": 1,
"defaultDashboardId": "",
"defaultUrl": "",
"defaultFilterFields": [
0,
1
]
}
Drill-down to external link
Explanation:
JSON:
{
"conditions": [
{
"id": 0,
"name": "first_condition",
"type": "OR",
"rules": [
{
"ruleid": 0,
"field": 1,
"fieldType": "text",
"operator": "==",
"value": "keller, texas"
},
{
"ruleid": 1,
"field": 4,
"fieldType": "text",
"operator": "==",
"value": "TX"
}
],
"actions": [
{
"drilldown": 4,
"dashboardid": "",
"url": "https://{1}/ui/index.html?{2}",
"filterFields": [
0,
1
]
}
]
}
],
"defaultDrilldown": 1,
"defaultDashboardId": "",
"defaultUrl": "",
"defaultFilterFields": [
0,
1
]
}
Data model for user dashboards.
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dashboard Settings | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Hide Time Picker |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Hide Datasource Selector |
|
||||||||||||||||||||||||||||||||||||||||||||||||