You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
External flows are flows that can be started via a Container type: AQ_ExternalFlow container, which can be part of a different Blueriq Application.
The data transfer between the container and the external flow is done via an intermediary profile, which is defined in a Contract module by creating entities, attributes, relations and value lists.
The communication between the AQ_ExternalFlow container and the external flow is done via the events which are defined in the Contract module, and these events should be mapped both in the container and the flow.
When selecting the flow type External, a new tab with name External appears.
In this tab you can define:
- The configuration module in which the data mapping is defined.
- The data mapping which is used to map the domain of the contract module to the domain of the current module. Therefore, the mapping you are selecting should have the contract module as the source and the current module as the target, otherwise you will get a validation error.
- The contract module that defines the contract between both Blueriq applications.
- Upon selecting the contract module, events which are defined in the contract module (if any), will be displayed in a list. All the events from the contract should be mapped to a named exit event of the flow you are modelling, otherwise you will get a validation error.
Overview
Content Tools