Skip to main content
Version: 1.5.x

Version Control

In Engagespot, changes are meticulously managed through versioning, enabling you to publish and migrate modifications between different environments. This process ensures that updates made in your development environment—such as editing a workflow—can be smoothly transitioned to production or custom environments.

info

Version control feature is enabled by default for all new users. Existing users, please contact support to enable this feature.

Unpublished Changes​

Unpublished changes represent modifications made in the development environment that remain in draft form. These changes are not automatically transferred to production or custom environments and cannot be tested until they are published or migrated. Unpublished changes serve as a staging area for adjustments that need further refinement or review.

Published Changes​

Published changes are those that have been finalized and are ready for testing in the current environment. Once changes are published, they become available for thorough testing to ensure they function correctly before they are moved to other environments.

Published Changes

How to Publish Changes​

To publish changes, use the Publish Changes feature. This allows you to transfer modifications from the development environment to the production or custom environments. During the publishing process:

  1. Select Changes: Choose the specific changes you want to publish.
  2. Write a Descriptive Message: Provide a detailed message explaining the changes. This helps team members understand the updates and their purpose.

After publishing, the changes will be available for testing in the selected environment.

Publish Changes

Migrate Changes​

The Migrate Changes feature allows you to transfer changes from one environment to another. This is useful for ensuring that your modifications are tested and ready for deployment.

How to Migrate Changes​

To migrate changes:

  1. Click on the Migrate Changes button.
  2. A modal will appear where you can select the target environment for migration.
  3. Once you select the desired environment, the published changes will be transferred to it.

The original development environment will also be updated with the migrated changes.

Migrate Changes
info

By default, all published changes are selected for migration. You cannot choose or deselect specific changes for migration.

Revert Changes​

The Revert Changes feature allows you to undo changes made in the development environment. This is particularly useful if you need to undo modifications or revert to a previous version of a workflow.

info

You can only revert changes from the development environment. Reverting changes directly from production or custom environments is not permitted.

Revert Changes

How to Revert Changes That Have Already Been Migrated​

To revert changes that have already been migrated to a specific environment:

  1. Navigate to Version Control.
  2. Select Published Changes.
  3. Choose the environment from which you want to revert changes.

This will display a list of published changes available in that environment.

  1. Select the changes you want to revert and click on the Revert button. This action creates a new change with the same name, which reverts the modifications to the development environment.
  2. You can then publish these reverted changes to the desired environment.