You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
This container can be used for embedding an external flow from a different Blueriq application.
To have the AQ_ExternalFlow container definition available, please make sure your project references the latest AquimaLibrary version.
Parameters
| Parameter | Description and usage |
|---|---|
| Connection | The expression results in the name of the connection used for configuring the flow on the target runtime. |
| Data Mapping | The Data Mapping used for mapping the data between the source profile (current domain) and the interface profile (contract domain). |
| Contract | The name of the Contract that the container needs to implement. Selecting the Contract triggers the pre-fill of the Contract events in the "Events" tab. |
| Contract events | when opening the "Events" tab, in the "Contract events" group, there are 3 columns :
|
Example for configuring the connection :
blueriq.connection.<connection-name>.external-flow.project=projectname // the REQUIRED name of the project that contains the flow to be started blueriq.connection.<connection-name>.external-flow.version=0.0-Trunk // the REQUIRED version of the project that contains the flow to be started blueriq.connection.<connection-name>.external-flow.flow=flowname // the REQUIRED name of the flow to be started blueriq.connection.<connection-name>.external-flow.channel=channel // the OPTIONAL name of the channel be started blueriq.connection.<connection-name>.external-flow.baseurl=http://<external-url>:<port>/Runtime/server // the OPTIONAL URL of the external host where the target project is on (if omitted the same server is assumed).
The connection name, namely <connection-name> in the example above, needs to match the result of the evaluated expression from the AQ_ExternalFlow_<name> container implementation.
Overview
Content Tools