Environments & Subscriptions

Environments

Projects vary in size and complexity, but the recommended setup is to have a TEST environment and a PROD environment where flows are shared via a subscription from Test to Prod.

• Flow Prod is connected to PROD ERP and/or PROD transactional databases.

• Flow Test is connected to TEST ERP and/or TEST transactional databases.

Larger projects can also include one or more dev environment where flows are developed in Dev, shared (Subscribed) to Test and validated by the customer, and then shared (Subscribed) from Dev to Prod.

When upgrading to a new version of Flow it is advisable to have an exact copy of the Flow Prod environment as a "Flow upgrade test" environment connected to the ERP PROD. Letting a sub-set of users do their normal work in a test upgraded version of flow can give a better validation than trying to make users do non-useful work in a test environment.

Subscriptions

Subscription must be used between the Test and Prod environment, or between a Dev and respectively Test and Prod environments. In order to subscribe, first the subscription needs to be created by entering a Comment in the Distribute Version popup and sharing. This Comment will be shown in the Notes of the subscribed flow on the Production side.

Connectors must be named the same in Test, Dev and Prod environments or else the subscription will not work.

Properties must be named the same in Test, Dev and Prod environments or else the subscription will not work.