Versions Compared

Old Version 16

changes.mady.by.user Unknown User (d.necas-niessner)

Saved on

compared with

New Version 17

changes.mady.by.user Unknown User (d.necas-niessner)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Table of contents

Table of Contents


Image Modified

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:

Image Modified

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.

Considerations

This new functionality 

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].

Table of contents

toc