Version control ensures that changes to object data are saved and remain visible. This allows you to always see who made a change, when it took place, and which data was modified.

KLEKSI offers version control at two levels:

1. Object-level version control
2. Version control of bulk changes

As a result, changes remain fully traceable and erroneous adjustments can be easily corrected.


Object-level version control
With object-level versioning, you can view the change history of individual object data and restore previous values.

Advantages

• Historical traceability
• All changes to object data are recorded. This allows you to determine:
• Which user has made a change.
• When the change has taken place.
• Which value has changed.
• What the previous value was.
• Restore changes
• When an incorrect change has been saved, you can easily revert to previous values.

Cooperation
When multiple users work on the same collection, version control provides insight into who made which changes. This makes collaboration more transparent and prevents ambiguity regarding the origin of data.


How does object-level version control work?

1. Open the object whose change history you want to view.
2. Click on the three dots next to a field.
3. Select Version Control.

An overview opens with all sessions in which changes were made to the relevant field.


View sessions
Changes are grouped by session. Per session, you will see, among other things:

• The user who made the change.
• The date and time of the change.
• The number of changes made during the session.

Click on a session to view all changes within that session.

Check changes
For every change, you can see:

• Which field has been changed.
• What value was originally present.
• Which new value has been stored.
• Restore a change

Do you want to revert to a previous value?

1. Open the relevant change.
2. Check the old and new value.
3. Click on Restore.

The original value is then restored.

Version control of bulk changes
In addition to changes at the object level, KLEKSI also tracks all executed bulk changes.

This allows incorrect bulk changes to be easily rolled back without the need to manually adjust objects. For more information, see the documentation on bulk changes.