Version History

Created by Reachware Support, Modified on Thu, 2 Apr at 3:00 PM by Reachware Support

Versioning in Reachware Studio allows you to save multiple versions of your integration flow. Each version acts as a snapshot of your flow at a specific point in time, making it easy to track changes, manage updates, and refer back to previous work whenever needed. For example, you can:

  • Save an initial version after creating the flow for the first time.
  • Save a new version after completing a set of updates.
  • Continuously enhance your flow over time while keeping a clear history of changes.

Versioning key benefits

Historical Review

You can always go back to a previous version and review earlier implementations.

Progress Tracking

Helps you clearly see how your flow has progressed where it started and how it evolved over time.

Secure Backup

Your work is safely stored, even in case of system updates or unexpected changes.

How to Create a Version

Saving a version is simple. Follow these steps:

1

From Reachware Studio, navigate to Flows Template.








2


From the card, you can see the version you are currently using.

3

Select View Flow.

4

Click the three-dot menu in the top-right corner.

5

Select Version History.

6

The Version Control panel will appear, displaying all previously saved versions.

7

Click Add New Version.

8

Enter a Version Name and a Description explaining the updates made in this version.

9

Click Save. Your new version is now successfully saved and available in the version history.

Semantic Versioning

Use Semantic Versioning for consistent and meaningful version naming. A version number follows this format:

v1.0.0
NumberTypeWhen to changeExample
FirstMajorBig update or complete redesign of the flowv1.0.0 → v2.0.0
SecondMinorNew feature added or existing feature improvedv1.0.0 → v1.1.0
ThirdPatchSmall fix or bug correctionv1.1.0 → v1.1.1

Related Topics


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article