Committing and publishing together

In the portal, under Environments, click Development, and there Open. Flow opens in a new tab and you are signed in straight away.

Click Versions in the bar on the left. With every change since the previous version it says who made it. When a colleague works along, Flow says above the button that you also commit their work: a version is a snapshot of the whole environment.

You write what changed and click Commit. At that very moment Tom Baker saves something else. Flow then commits nothing you did not see: it says what changed and by whom, and shows the list again.

You see the list as it is now. Click Commit once more: the version is in the history, with whose work is in it.

Tom Baker had Version control open too. Your version appears there without refreshing, and his changes are gone from the list: they are in your version.

Click Publish, top right. The preview shows what goes along, and also what is not committed in Development yet and so does not go along: Tom Baker is still working on his workflow.

While you look, Tom Baker commits a new version. When you click Publish, Flow does not publish that newer version unseen: it says what happened and shows the preview again, with what goes along now.

You have looked at the new version. Click Publish once more: Acceptance now runs exactly this version, under the number it was committed as in Development: version #2 from Development. So one piece of work has one number, from Development to Production.