Page History
This AQ_Dashboard_ProjectWidget container starts an exposed flow with interaction of another project that could be placed in a different branch or repository (as long as it resides in the same runtime), 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
...
| UI Text Box | ||
|---|---|---|
| ||
If you want to show the content external applications that are not modelled in Studio, you can use the AQ_ExternalContent container. |
...
service.
Parameters
Name | Direction | Description | Type | Occurrences | Required |
|---|---|---|---|---|---|
| ShortcutName | Input |
...
An expression to determine the shortcut to start. This shortcut must be added to |
...
the application.properties |
...
file. | Expression - String | Single valued | Either |
...
the |
...
or You can not use both in the |
...
same | ||
| ShortcutAttribute | Input | Select a string attribute that holds the name of the shortcut to be |
...
taken. This shortcut must be added to the | Module Element - Attribute | Single valued | ||
| Data | Input | Data of the current application that you want to transfer to the triggered application. This is done using key value pairs. The value is single valued. | Expression - Any; Key-value pair; Multivalued result Although this parameter is multi-valued result, only single-valued data currently works. | Multi valued |
...
| No | ||||
| PortalMessages | Input | Select portal messages to which this widget should react. | GlobalElement - PortalMessage | Multi valued |
...
| No |
| Tip |
|---|
When using this widget, the shortcut property dynamicVersion is considered. for more information about this see shortcut information |
| Info |
|---|
...
If you choose for the |
...
value list, then the runtime validates that each shortcut name exists in the runtime that is defined in the value list. |
...
| type | note |
|---|
| Info |
|---|
Take note that it is possible to create infinite loops when using a |
...
shortcut to the same project as the one you use this container in. This will eventually cause an OutOfMemory exception . |
| Warning |
|---|
Having multiple AQ_Project_Widget containers with the same name on the same page is not supported. |
Security
As a project, you need to be aware of security when
...
Example
...
communication is involved. The
...
communication between the starting and started application is done with server internally in code. This means that it is perfectly secure as no data can be intercepted or changed.
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