You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
This AQ_Dashboard_ProjectWidget container starts an exposed flow with interaction of another project that could be placed in a different branch or repository, and displays the pages of the other flow in this container. Communication to the other project is possible in two ways. When the AQ_Dashboard_ProjectWidget container is rendered on the page, data can be send to the other project using the Data parameter. Once the page is done loading, information can be submitted using Portal Messages. In both cases can the data be retrieved in the other project by using the AQ_GetRequestParameters [Editor] service.
If you want to show the content external applications that are not modelled in Studio, you can use the AQ_ExternalContent container.
Parameters
Name | Direction | Description | Type | Occurrences | Required |
|---|---|---|---|---|---|
| ShortcutName | Input | The shortcut name which refers to an URL of the application to start. This shortcut must be added to the aquima.properties file. | Expression - String | Single valued | false |
| ShortcutAttribute | Input | Select a string attribute that holds the name of the shortcut to be used. | Module Element - Attribute | Single valued | false |
| Data | Input | Data of the current application that you want to transfer to the triggered application. This is done using key value pairs. | Expression - Any; Key-value pair; Multivalued result | Multi valued | false |
| PortalMessages | Input | Select portal messages to which this widget should react. | GlobalElement - PortalMessage | Multi valued | false |
Either the ShortcutName or ShortcutAttribute are required. You can not use both in the same service call. An error occurs at runtime when unknown is submitted in these parameters.
If you choose for the ShortcutAttribute parameter an attribute that has a Value list, then the runtime validates that each shortcut name exists in the runtime that is defined in the value list.
Example
The above container uses an attribute with a value list of possibly case types. Depending on the type of subsidy, a different application is opened that is responsible for handling that type of subsidy cases. The application is opened in the widget and important information is passed to the other application using the Data parameter. This information is the subsidy ID and a string to indicate what dashboard page to open. The flow in the other application has a split node in the flow, which uses this string to determine to what page to flow. If a user wants to open another subsidy case from within another widget on the dashboard, the portal message is passed to this widget which can refresh its content with the new ID, which is passed as data in the portal message.
Overview
Content Tools