Deploying a Versioned Form while Maintaining Workflow

When form versioning is enabled before deployment, workflow connections are preserved across form version deployments. This allows existing workflows to continue functioning with newly deployed form versions without requiring the workflows to be recreated or reconfigured.

Consider a form that exists in two separate environments, such as a Development (Dev) site and a Live site. Versioning is enabled for the form in both environments.

1. In the Live environment (the deployment target), create a workflow associated with the form.
2. In the Dev environment, create a new version of the same form and make any necessary updates.
3. Deploy the updated form version from the Dev environment to the Live environment.

After deployment, the Live environment automatically maintains the existing workflow association while applying the newly deployed form version. The workflow continues to function with the updated form, eliminating the need to recreate or reconnect it.

Example Scenario:

A form is available in both a Dev site and a Live site, with versioning enabled in each environment.

• A workflow is created for the form in the Live site.
• A new version of the form is created in the Dev site, including updates to the form.
• The updated form is deployed from the Dev site to the Live site.

Once the deployment is complete, the Live site retains the workflow connection while using the newly deployed form version. This ensures workflow continuity across deployments and streamlines the release process.

Only the form is deployed. Workflows are not deployed as part of the form deployment process.

If workflow changes are made in the Dev environment, those changes are not transferred to the Live environment during deployment. Any workflow updates must be manually applied to the existing workflow in the Live environment after the new form version has been deployed.