- Getting started
- For administrators
- RPA workflow projects
- Creating an RPA workflow from an idea
- Creating a project
- How to start an RPA workflow
- Managing project files and folders
- Connecting RPA workflows to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- App projects
- Agentic processes
- Agents
- Solutions
- API workflows
- Tests
Studio Web user guide
Version control for solutions
Version control enhances team collaboration, allowing multiple users to view, track, and restore different versions of a solution at any time. This enables developers to build and test automations without overwriting each other’s work.
Version control in Studio Web works differently depending on the type of workspace:
- Cloud workspaces: version control is managed via snapshots in the Change History panel.
- Local workspaces: version control is managed via Git in the Version Control panel.
Version control in the Cloud Workspace
Version control for solutions is handled within the Change History panel through snapshots. You can think of snapshots as "checkpoints" of the solution as various stages in its development. Snapshots preserve the entire solution state, including its automation projects, resources, and deployment configuration.
There are multiple types of snapshots:
- Current version: The current (latest) version of a solution. It appears at the top of the list of snapshots in the Change History panel.
- Manual snapshots: Snapshots created manually by users. They have a name and an optional description. Selecting or hovering over a manual snapshot shows the name of its author and when it was created. Can only be opened in read-only mode.
- Auto snapshots: Snapshots created automatically when you close the solution and every 40 minutes while the solution is opened. Auto snapshots have timestamp-based names (for example, "Auto snapshot - 2026-03-14 10:40 UTC").
- Publish snapshots: Snapshots created automatically each time the solution is published. Their name is the published solution version. Hovering over a publish snapshot shows the name of its author and when it was created. Can only be opened in read-only mode.
Note:
All snapshots, including manual ones, are available for anyone who has access to the solution.
The Change History panel lists all snapshots chronologically, showing their:
- Version number and description (for example, "v1.1.0 - Feedback form included").
- Author and timestamp (for example, "2 months ago by John Doe").
- Title (for example, "Stable build before testing NetSuite integration").
You can use the Filter button to control which types of snapshots appear in the Change History panel.
When you select a snapshot from the panel, you are viewing the solution as it existed at that particular point in time. A temporary banner message appears when browsing a past snapshot, informing you that you are viewing a past version of the solution in read-only mode.
Auto snapshots have retention limits based on your organization's entitlements and may vary depending on the licensing plan:
- Per-solution limit: Each solution retains a maximum number of auto snapshots. When this limit is reached, the oldest snapshots are automatically removed as new ones are added.
- Time-based limit: Auto snapshots older than a configured retention period are automatically removed.
To create a new manual snapshot:
- Open the Change History panel. Ensure that the Current version snapshot is selected.
- Select the Create snapshot button in the top-right corner of the panel.
- Enter a name for your snapshot.
- Optionally, press the Tab key or select the Add description field to enter a description.
- Click anywhere in the Studio Web Designer or press the Enter key. The new snapshot is created and is added in the Change History panel.
One of the main features of snapshots is the ability to restore the solution to a particular point in time. By default, restoring a solution from a snapshot creates a copy of the latest snapshot (that is, Current version) for reference. This ensures that you do not lose any work that you did on the latest version of the solution.
To access the restore feature:
- Open the Change History panel.
- Hover over a manual snapshot or a publish snapshot.
- Select the Restore button. The Restore snapshot window appears.
- Under the Title field, enter a mandatory name for the copy of the latest snapshot.
- Optionally, enter a description of the updates made to the solution.
- Select the Restore button. A banner message appears, informing you that the solution was successfully restored to that particular point in time.
- Alternatively, select Restore without saving to discard the latest version of the solution.
Selecting Restore without saving restores the solution without saving the latest snapshot (the Current version snapshot). This means that the latest version of your solution is deleted.
FAQs
Do auto snapshots affect performance?
No. Auto snapshots are created in the background and do not block or slow down your work in the designer.
Can I delete individual auto snapshots?
No. Auto snapshots are managed automatically by Studio Web and cannot be deleted individually. Old auto snapshots are removed automatically based on the retention policy.
Do auto snapshots count toward my storage?
Yes. Auto snapshots use cloud storage. The retention limits ensure that storage usage stays bounded.
Are auto snapshots visible to everyone who has access to the solution?
Yes. Like all snapshots, auto snapshots are available for anyone who has access to the solution.
What happens to auto snapshots on shared solutions?
Shared solutions follow the same auto snapshot policy as owned solutions. Auto snapshots are created for any user who opens and works on the solution, and all snapshots are visible to anyone with access.
Can I create auto snapshots for local solutions?
No. Auto snapshots are only available for cloud solutions.
Version control in the Local Workspace
Studio Web integrates with Git to enable efficient version control for solutions saved locally on your machine.
As a prerequisite, make sure you are working on a locally-saved solution:
- Open Studio Web.
- Navigate to the Local Workspace page.
- Open an existing local solution via the Open solution button or create a new one from the Create New button. You can also select an existing solution from the list of previously opened solutions.
- Select the folder where an existing solution is saved locally or indicate a folder where the new solutions should be created. You new local solution opens.
Important:
When prompted by your browser, allow Studio Web to edit files.
- Open to the Version control panel.
The first time you open the panel, you are instructed to initialize a local Git repository. This step is mandatory and is performed automatically by selecting the Initialize repository button. When you initialize a local Git repository, Studio Web:
- Creates a .gitignore file.
- Makes an initial commit with the current files in the solution.
- Creates a local branch named "master".
Creating and managing branches
Select the branch name from the top-left corner of the Version control panel to:
- Create a new branch from the Create new branch button. Enter the branch name and then select Create. The branch is added to the list of available branches.
- Switch branches by selecting a branch name from the list under Local branches. The solution reloads when switching branches.
Branches are grouped under local branches and remote branches. When selecting a remote branch, a message window informs you that switching to the remote branch means losing the changes made currently to your local branch and resetting the local branch to the state of the remote branch.
Connecting to a remote repository
To connect your existing local repository to a remote repository:
- Select the options icon in the top-right corner of the Version control panel.
- Select the Connect to GitHub button. The GitHub authentication window appears.
- Authenticate to GitHub using the GitHub Integration Service connector.
- After successfully authenticating, enter the URL for your remote repository in the Repository URL field.
- Select the Save configuration button.
- Alternatively, select Back to return to the Version control panel.
Committing and pushing changes
When working on a solution, the changes that you make are recorded under Changes in the Version control panel. Select each change in the list to see a side-by-side view of what changed. Changes are highlighted as follows:
- Green and the + icon indicate that something has been added to a project file.
- Orange and the / icon indicate that the file has been modified.
- Red and the - icon indicate that something has been remove from a project file.
To commit the changes made to your solution and push them to the branch you are currently on:
- Select the Commit button in the Version control panel.
- Enter a commit message. The changes included in the commit are displayed under the Changes section.
- Select Commit. Your new commit appears in the Commit History section.
Viewing the commit history
The Commit history section contains all your commits in chronological order starting from the initial commit. Each commit shows information about its author and when it was created.
Select a commit from the list the see the Changes section for that particular commit.
Right-click a commit and select:
- Create branch from this commit to create a new local branch beginning from this commit. Give the new branch a name and select Create. The new branch is now active and appears in the list of available branches.
- Reset local branch to this commit to restore the current branch to the state it was when the commit was created. Commits that are more recent than this commit are automatically deleted from the Commit history.
