Understanding workflow releases

Introduction

Cargo's workflow editor incorporates a version control system.

While all workflow 'releases' and 'draft' versions are periodically saved in cloud storage, providing a version control system was a great way to offer our users the ability to collaboratively build workflows with their team.

In practice, we have seen that this helps users manage the evolution of workflows, enable the handling of drafts and global deployments, much like software development teams would use Github (or equivalent).

Firstly, it allows multiple team members to collaborate on the same workflow, ensuring changes are synchronized and conflicts are minimized.

Secondly, users can manage different versions of a workflow simultaneously, enabling experimentation and testing without disrupting the main workflow.

---

Publishing drafts

In Cargo, all workflows releases are initially drafts until they are 'published' as releases, making them active and executable.

It is best practice to make small and regular releases, so that workflow logic can be tested in small increments after changes.

Once a published release is 'Enabled', the workflow can then begin to actively track relevent changes to enrole the right records into the workflow from a data model.

To reduce the possibility of version conflicts between team members, it's recommended to reuse the latest release before proceeding with edits on a local draft. The workflow editor will prompt the user to reuse the latest version when such a case is detected.