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 [Editor] 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. |
...
| UI Text Box | ||
|---|---|---|
| ||
Take note that it is possible to create infinite loops when including using a schortcut to the same project as the one you use this container in. This will eventually cause an OutOfMemory exception eventually . |
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