You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
This AQ_Dashboard_ProjectWidget container will start another application that could be placed in a different branch or repository, and show the contents of the other application in a widget. You can submit data to the other application and the data can be retrieved in the other application by using the AQ_GetRequestParameters [Editor] service. Portalmessages can also be send to the application running in this widget, and can be received from the application that is running in this widget. Data from such a portal message can be read in the other application using the AQ_GetRequestParameters [Editor] service.
Parameters
Name | Direction | Description | Type | Occurrences | Required |
|---|---|---|---|---|---|
| ShortcutName | Input | The URL of the application to start. | Expression - String | Single valued | false |
| ShortcutAttribute | Input | Select a string attribute that holds the name of the shortcut to be taken. | Module Element - Attribute | Single valued | false |
| Data | Input | Submit data to the new application 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