Discovery and sharing of flows or inspiration for flows.
Feedback and change management.
Versioned staging scheme.
Documentation of processes and their flow implementation.
A typical process would be:
2 primary modes of publishing a flow.
An upgradable self-contained, pre-packaged read-only flow which cannot be edited on the local distribution. Extension points are used to provide a mechanism for local adaptation. Flows can be upgraded. An automated disclosure note is generated describing which API’s the flow use. This is considered the most safe for consumers of flows but requires the producer of the flow to expend some effort making the flow re-usable.
A collection of flow/field/service/table publishes a collection of things which may be modified to suit local needs. Updates overwrite local changes. This is a publishing a sort of example which can be tailored to consumer to more closely fit his/her needs.
A published flow can and should be augmented with:
The hub is also a way to run a controlled staging process. You can then;
This proces can also be used on a local hub - you don’t need the replication scheme.
# Architecture