Project Versions

This section outlines how version control works in IPSE GO, including how new versions are created, how to access previous versions, and who is permitted to manage version history. Project versioning in IPSE GO provides a robust and secure framework to support the long-term development of your models.

Each project version is saved along with the current project data, helping maintain traceability and consistency throughout the modeling process. With versioning, users can confidently make changes, knowing there’s always a reliable way to revert to earlier versions of the project and its model.

Saving New Versions

Whenever changes are saved in IPSE GO, the previous state is automatically preserved as a Project Version, making it available for future access.

Figure 1. You can assign a name to saved versions directly in the Save-As dialog.

To save a new version manually, press CTRL+SHIFT+S. This opens the Save-As dialog (see Figure 1). Ensure the project contains unsaved changes, then select New Version and provide a descriptive name in the Version Name field to support better traceability.

Viewing Project Versions

IPSE GO automatically maintains a cloud-based version history for each project. To access the version history:

Go to Project Versions from the toolbar.
The project version history window will open, as shown in Figure 2.

Figure 2. Use the version history window to browse, inspect, or manage previously saved versions.

The version history window features a timeline displaying all saved versions, along with the author’s name and the creation timestamp. On the right, a flowsheet visually represents the project state for the selected version. You can inspect data, open a project in a previous state, or copy data between versions using CTRL+C and CTRL+V.

Version Descriptions and Tags

Each version may include a description and tags.

A description is free-form text that helps users quickly identify the purpose of a version. If no description is provided, the timestamp will be shown instead. It is recommended to label important versions clearly i.e. Initial Working Version, Design 75%, Public Draft.

Version tags are short, unique identifiers within a project. You can assign multiple tags to a version to mark significant milestones. Tags can be added or modified using the context menu by selecting Edit Tags. Tags cannot contain whitespaces and are by convention written in lower case characters using hyphens (-) as separator (e.g. public, version-1, draft-05).

A practical use of tags is in combination with project embedding. This ensures that embedded versions remain unchanged, even as new edits are made to the project.

Deleting Versions

To remove an earlier version, right-click the desired version and select Delete Version. Deleting a version does not affect any earlier or later versions.

Deleting a version is irreversible. Please ensure the version’s data is no longer needed before proceeding. As with project deletions, support cannot recover deleted versions.

Only the project owner or the user who created a specific version can delete it. This ensures secure and traceable version management. Note that the current active version cannot be deleted.

If a project is deleted, all associated versions will also be removed.