---
title: "Process Versions"
slug: "process-versions"
updated: 2024-01-28T08:30:32Z
published: 2024-01-28T08:30:32Z
canonical: "kb.easysend.io/process-versions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.easysend.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Process Versions

## Article Overview

The following article describes EasySend's Process Versions feature. It describes what it is and how to use it.

## What is the Process Versions Feature?

Process Versions is a Builder platform feature that allows users to view and restore previous versions of a digital process. The feature maintains a history of changes made over time to help users debug, audit, and understand the evolution of a process.

## How to Create a New Process Version

(See **Figure 1** and **Figure 2**)

A new process version is created when changes are made to one of the process's modules:

- Webflow
- PDF
- Workflow manager
- Model
- Agent

and then by:

- Immediately Deploying to a selected server (1)
- Manually saving a new version by performing the following actions:
  - Clicking the three dots (1)
  - Clicking Save a new Version (2)

**![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705949506718.png)**

**Figure 1:** **Deployment**

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705988677640.png)

**Figure 2: Save a new version**

Additional ways to create new process versions are:

- Deleting a:
  - Webflow
  - PDF
  - Workflow Manager step output
- Resorting an old version

NOTE

- A manually saved new version, a deletion, and restoring an old version will not reflected on a server as a new process version until deployment is done.
- For additional information about restoring a process version, click [here](/v1/docs/process-versions#how-to-restore-a-version).

Important!

- When saving a new version all the modules are saved simultaneously.
- When restoring a saved process version all the modules are restored simultaneously.

## How to Access the Feature

(See **Figure 3**)

The Process Versions feature is accessible by clicking the Versions icon (1). The icon is located across the Builder platform:

- Webflow
- PDF (after creating a new form)
- Model
- Agent

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705943040819.png)

**Figure 3:** **Versions Icon**

clicking the Versions icon opens the Process Versions screen.

## Process Versions Screen

(See **Figure 4**)

The screen is divided into two sections:

- Current Versions (1)
- Versions History (2)

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705953321614.png)

**Figure 4: Process Versions Screen**

### Current Versions

(See **Figure 5** to **Figure 9**)

This section displays information about the currently deployed digital process version on each server. The servers are divided into two types:

- Dev (development) - used for testing and QA purposes
- Prod (production) - used to launch the digital process

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705946193303.png)

**Figure 5: Current Versions**

NOTEDeploying a process to a Dev server and then deploying it to a Prod server without preforming any changes does not create an additional new process version. 

If a digital process is not deployed on a server or its most recent deployment was before June 23rd, meaning that there is no compatibility with the current version mechanism, the server will display a message:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705947948952.png)

**Figure 6: No** **Deployment**

If a digital process was deployed after changes were made to one or more of its modules, the server will display the current version number and a message that includes when the digital process was deployed and by whom:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705948090994.png)

**Figure 7: Deployed to a Server**

If a digital process was manually saved after changes were made to one or more of its modules and then deployed, the server will display the current version number and a message that includes when the digital process was saved and by whom:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705948993157.png)

**Figure 8: Manually Saved**

If a digital process was restored to a previous version, the server will display the current version number and a message that includes the version number that was restored, when the digital process was deployed, and by whom:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705954494160.png)

**Figure 9: Restored Version**

NOTEFor a detailed description of how to restore a previous version, click [here](/v1/docs/process-versions#how-to-restore-a-version).

### Versions History

(See **Figure 10** to **Figure 12**)

This section displays the version history of the digital process. It includes the following information:

- Version Name (1)
- Description (2)
- Last Deployment On/To (3)(4)
- Environment (5):
  - Dev
  - Prod
  - Saved Version
- Author (6) - the user that last deployed the digital process or saved it manually

The information in this section is searchable by version name or description (7) and can also be filtered by server (8).

NOTEA successfully manually saved version of a digital process and a deletion (Webflow, PDF, Workflow Manager output) will appear in this section as new versions without performing a deployment. 

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705953353316.png)

**Figure 10: Versions History**

In this section, you can perform additional actions. The actions are visible by clicking the three dots (9):

- Restore Version
- Edit Description - allows the user to edit the description message

NOTEThe description message in the Current Versions section will not change. 

- Deploy History - displays the Deploy History window

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705951746339.png)

**Figure 11: Additional Actions**

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705952849282.png)

**Figure 12: Edit Version Description and Deploy History Windows**

## How to Restore a Version

(See **Figure 13** to **Figure 17**)

To restore a version, perform the following steps:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705953448107.png)

**Figure 13: Three Dots**

1. Locate the desired version
2. Click the three dots (1)

*Result:*

Additional options appear:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705953584311.png)

**Figure 14: Restore Version**

1. Click **Restore Version** (2).

*Result:*

The **Restore Version** message appears:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705953756615.png)

**Figure 15: Restore**

1. Click **Restore** (3).

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705954033742.png)

**Figure 16: Restore Success** **Message**

1. Wait for the process to end and for the success message to appear (4).
2. Navigate back to the canvas (5).

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705954122096.png)

**Figure 17: Restore Success** **Message**

1. View the resorted version and edit it if required.
2. **Deploy** the digital process to the desired server (6).

When returning to the Process Versions screen after the deployment notice that:

- The server that the restored version displays a message indicating that the version was restored (see **Figure 18**):

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705954802047.png)

**Figure 18: Current Versions**

- A new entry (8) is added to the Versions History section indicating that the current version was saved before the restoration happened (see **Figure 19**):

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705954940327.png)

**Figure 19: Current Versions**

NOTEThe added entry will be used to revert the restoration if needed.

## Process Versions Retention

Performing a deployment or manually saving a new version is quite common and frequent while building a digital process. To keep the Versions History section easy to follow, the system will automatically remove Dev process versions older than six months - as long as the process has at least 20 versions.

## Restore Failures

Users will not be able to restore a process to its previous version if any one of the following conditions exist:

- None of the Languages used in the process exists within the customers' languages in Customer Settings
- All of the Themes used in the Webflows of the process do not exist anymore
- Two users are co-browsing
- A Deploy is in progress
- Internal platform issues

An error message indicating the failure will automatically appear when the restore process is done, for example:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1705990156720.png)

**Figure 20:Restore Failed Error Message**

If the restore process keeps failing, please contact our support team.