The versioning rules have the 'versionMode' attribute that controls when an old version should be created.

The possible values are:

•oncePerSession: an old version is created only once per editing session - so if an object is opened in an editor and saved more than once while being edited only the first save will create a new version

•explicitSave: old versions are created at every save requested by the user - auto-save triggered automatically by the system do not create versions

•everySave: old versions are created at every and all saves.

Note that this setting controls only which operations trigger the creation of a version. The limits on the number of old versions to keep are honored regardless of this setting.

About editing objects and versioning mode

When editing an object in the Web interface if the versioning mode is set to 'oncePerSession' the first click on 'OK' or 'Apply' trigger the creation of a version, subsequent clicks will save the object without creating a new version.

There are no auto-saves in the Web interface, so there is no difference between 'everySave' and 'explicitSave'.

About the versioning rule editing form

The versioning rules editing form looks like this:

The versioning mode is copied into the partitions (as the other versioning rule attributes) in the automatically computed attribute 'versionMode':

Global versioning mode

It is recommended to avoid to activate the versioning on the global level, as it will create versions for all objects, even for those you cannot really use, affecting the performances. It is recommended instead to configure the versions on the versioning rules, partitions and folders level.

The global configuration object (GlobalConfig.xml) has the attribute 'VersionMode' of the VersioningDefaults element that sets the default mode to be used for the objects that do not have an associated partition - or whose partition does not have a versioning rule:

  <GlobalConfig . . .>

    <ReadingTime MinRate="980" MaxRate="980" />

    <VersioningDefaults InitialVersions="1" LastVersions="2" VersionMode="explicitSaveVal" />

    . . . 

  </GlobalConfig>

This attribute can be edited in the global configuration form:

IMPORTANT: To make these changes available to the GN4 users, after you saved the GLOBALCONFIG.XML file and imported it into the database, or after you modified it in EdAdmin4 and saved, recycle the GN4 application pools on all IIS servers and then make all users log out and log back in.