Introduction
The external flow is a concept that allows embedding and starting a flow from a (remote) project, without the use of Portal Messages.
The value of this functionality is to get:
- a good design of the solution:
- Structure your application
- Make your solution scalable
- a good application UX:
- The end user directly see which information is loaded and what not
- a good application model:
- Modelling is more explicit which brings clarity in the model
Conceptually it works as depicted in the following figure.
This container will replace the AQ_Dashboard_FlowWidget and AQ_Dashboard_ProjectWidget.
See also external flow [editor] for detailed information.
Architecture
The architecture of the EFC looks like the following:
Elements
To be able to use this functionality a new container type is to be used: the AQ_ExternalFlow.
Also the concept of a contract is needed: see Contract module.
Limitations
- Running the external flow using host and target runtimes with different major and minor versions is not supported.
Pros
xxx
- To split up large applications
- In control
- Short release cycle
- Release part is small
- Target inactive ...
- Docker ??
Pitfalls
xxx
- This construction should not be used as a "doel an sich"
- There is a chance of circular reasoning
- Sessions can break
- Datamapping ...
Configuration
For configuring this functionality see External Flow [Editor].
Overview
Content Tools