Versioning

As you build and improve your Flows, FormWise keeps track of every version so you can experiment freely without worrying about losing your work. This guide explains how the versioning system works and how to use it effectively.

How versioning works

Every Flow in FormWise starts as a draft. When you are happy with it, you publish it to create a named version. You can keep iterating and publishing new versions over time, and FormWise keeps a full history of every version you have created.

Working with drafts

When you first create a Flow or make changes to an existing one, you are working on a draft. Here is what you should know about drafts:

• Changes save automatically. As you edit your workflow, form, or settings, your progress is saved in real time. You do not need to click a save button.
• Drafts are private. Your draft is only visible to you and your team in the editor. End users never see draft changes until you publish.
• There is only one draft at a time. Your draft always represents the latest state of your work.

Think of the draft as your workspace - it is where you build, experiment, and refine before making anything official.

Creating a version

When your Flow is ready to be saved as a snapshot:

1. Click the Publish button in the Flow editor.
2. Give your version a name (for example, "v1", "v2", or something more descriptive like "Added follow-up questions").
3. Optionally, check Make this version live to deploy it immediately (more on this in Deploying).
4. Click Publish to confirm.

That is it. FormWise takes a complete snapshot of your Flow at that moment - the workflow, form schema, and UI configuration are all saved together.

Viewing version history

To see all the versions you have created:

1. Open your Flow.
2. Click the version selector in the editor's toolbar - it shows Draft (or the name of the version you're currently viewing).
3. The dropdown lists every published version, newest first, with the currently live one marked LIVE.

Restoring a previous version

If something goes wrong or you want to go back to an earlier state:

1. Open the version selector and choose the version you want to go back to. The editor now loads that version's content.
2. Make any changes you want (or none at all), then click Publish to save it as a new version based on the one you selected.
3. Check Make this version live if you want it to replace the current live version.

Nothing is overwritten until you publish - selecting an older version just loads it for you to review or build on. Your full version history stays intact either way.

Why version your Flows

Versioning gives you a few important advantages:

• Experiment safely. Try new system instructions, swap models, or restructure your workflow. If it does not work out, you can always go back.
• Track changes over time. See how your Flow has evolved. This is especially helpful when multiple team members are making changes.
• Roll back quickly. If a new version causes problems in production, publishing from a previous version takes seconds.
• Compare results. Run your test suite against different versions to see which one performs better.

Best practices

• Publish before making big changes. If your Flow is working well, create a version before you start experimenting. That way you have a safe point to return to.
• Use descriptive version names. Names like "Added JSON output" or "Switched to GPT-5.1" are much more helpful than "v1" and "v2" when you are looking back through history.
• Publish regularly. Do not wait until everything is perfect. Frequent versions give you more rollback points and a clearer history of changes.

Next steps

Ready to share your Flow with users? Learn how to make a version live and deploy it in Deploying.