Versioning

---

The database Version server enables versioning of files stored in it and saving all information about changes that were applied to a given element.

A new version is created when:

1. you choose Check out,
2. you create a New element,
3. you recover a file version,
4. you make changes to one of the previous versions,
5. you import a file the current version of which differs from the imported one.

tip

Each version of the file is assigned an expiry date, specifying from when it "works" in the created application. If two versions have the same effective date, the version creation date is checked and the version with the later date is respected.

We can distinguish the following states in which a version (and indirectly a file) can be found:

1. current version - a version of which the validity period covers the current date,
2. edited version - a version that was opened in edit mode,
3. incorrect version - a version that, due to errors made during editing, does not meet the validation conditions.

Information about the file status is available in the Properties panel.

Thanks to versioning it is possible to:

1. track the lifecycle of a file - you can see who, when and what changes have been made in the Tracking section
2. restore or correct any historical version - see Restoring a version.
3. maintain the consistency of the application, despite the changes introduced to its elements.

Version Properties

You can display the properties window for the selected version.

1. Select the Version server panel.
2. Select the file on the version server.
3. Right-click and select Properties from the context menu or from the top menu.

The Properties window contains basic information about a given version, grouped in sections:

Check out- informs if the file is being edited, and if the version is being edited, then additional information is displayed in this section, including the effective date of the version.

Basic - version properties:

1. Path - where the version is located.

2. Description - you can enter optional text describing the file's purpose, structure.

3. Version identifier - A unique key generated for each version server file that allows it to be uniquely identified.

4. Is new, Valid, Deleted - Information about the version being new, correct or whether it was deleted.

5. Metadata

6. Name - here you can change the name of the version, which will also be changed in the version server tree.

7. Full name - Full name with extension.

8. Technical version - in this field you can choose whether the version has a technical status.

9. Version type.

Audit- version creation and modification data

1. Creation date - date when the first version of the file was created.
2. Creator - The person who created the first version of the file.
3. Last modification date
4. Last Modifier - The person who last made changes to the version.

Version history

You can display a window with a complete list of versions from the oldest to the newest.

tip

This functionality is available only for the database version server.

1. Select the Version Server panel.
2. Select the file on the version server.
3. Right-click and select History from the context menu.

In the History window, you can go to the preview of a particular version in the designer window or to the XML view . Select one of the Open options.

See also

Deleting a Version

Performing operations on a Version

Version Mass Validation