Page History
A DCM Dashboard application is very easy to configure and to maintain. It consists of two main elements: pages and menus.
...
Page
In a DCM Dashboard application there are two ways in which navigation can occur:
...
Per widget some settings have to provided:
Setting | Setting options | Description |
---|---|---|
Type | Flow | This setting allows you to configure which exposed flow from a Blueriq project will be started in this widget. |
Task | Starting the task will be done by the Case Engine in cooperation with the Runtime. The start task event type will provide the case and task ids, via its parameters, to the Case Engine. | |
Reference | Shortcut | Preferred setting for production mode. This allows you to reference to a shortcut that you configured in the properties of the Blueriq Runtime. |
Development | This option allows you to quickly change between flows and/or versions during development time. By referencing to the project name, the branch name and the exposed flow name. | |
Roles | - | The roles are available from the globals in the dashboard project. These can be shared via a library and be included via project structure. |
Environment override | - | In order to run dashboard widgets on different environments you can optionally configure the baseUrl path which is specified as the environment override in the model per widget. More information about how to configure this can be found here. |
...
Menu
Configuring the menu is very straight forward. Different menus can be created. Each menu consist of one or multiple menu item. For each menu item only three things have to be configured:
- The display text that has be shown in the application during execution
- The Dashboard page that is referenced to
- If there are any roles applied
Overview
Content Tools