Flow-process -> Flow module

Flow process and some other services have been merged into the now-named Flow module.

This was done in order to have greater control over releases and allow us to release everything in one package. There are many benefits to this, like reducing the number of services needed to set up a Flow project and keeping everything up to date. This also accommodates the future module system that should be rolled out later this year.

The Case Manager is not included in the module for now, but as the micro frontend version is released, it will also be a part of the Flow module.

Here is a rough overview of the Flow module with all its components:

You can see version 1.0 of the Flow module as a major version. This means that there will be breaking changes, but also some nice features:

• The Auditlog is now built into Flow, which gives you auditing without any extra setup.
• Improved validation and deployment performance with up to 3x speed.
• Pushing updated dependencies in flow-process now properly restarts flow-process.
• Ecmascript support for handlers.

For the full changelog, you can see it here, and you can find the migration guide here.

When merging everything into one module, we have restructured our documentation to unify it more for the Flow module. This includes a stricter split in categories:

• Concepts - A high-level overview of new concepts you need to be familiar with in the Flow module.
• Guides - Describes how to work with the different Concepts and is structured roughly in the timeline of a project.
• Reference - Description of how each concept works in detail.
• We are still working on fleshing out the documentation, so there will be more information to look out for in the future.