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 the AQ_GetRequestParameters service.
| 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. |
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 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 | false |
| PortalMessages | Input | Select portal messages to which this widget should react. | GlobalElement - PortalMessage | Multi valued | false |
...
Overview
Content Tools