Document versioning

ConteBracco

Hi, I'm trying to version a document.

I've loaded the master one and then I checked out the document and checked in 9 more versions with new contents.

When I read all versions of the document with GetAllVersions (DFS) I notice something strange about the version number. Here you are the output of GetAllVersions method:

[01] chronicle_id: 09022164801d240c - object_id: 09022164801d240c creation_date: 28/04/2016 12.07.50  version: 1.0

[02] chronicle_id: 09022164801d240c - object_id: 09022164801d2414 creation_date: 28/04/2016 12.25.00  version: 1.1

[03] chronicle_id: 09022164801d240c - object_id: 09022164801d2416 creation_date: 28/04/2016 12.25.17  version: 1.0.1.0

[04] chronicle_id: 09022164801d240c - object_id: 09022164801d27a5 creation_date: 28/04/2016 12.25.29  version: 1.0.2.0

[05] chronicle_id: 09022164801d240c - object_id: 09022164801d27a7 creation_date: 28/04/2016 12.25.37  version: 1.0.3.0

[06] chronicle_id: 09022164801d240c - object_id: 09022164801d27a9 creation_date: 28/04/2016 12.25.47  version: 1.0.4.0

[07] chronicle_id: 09022164801d240c - object_id: 09022164801d27ab creation_date: 28/04/2016 12.25.55  version: 1.0.5.0

[08] chronicle_id: 09022164801d240c - object_id: 09022164801d27ad creation_date: 28/04/2016 12.26.03  version: 1.0.6.0

[09] chronicle_id: 09022164801d240c - object_id: 09022164801d2418 creation_date: 28/04/2016 12.26.13  version: 1.0.7.0

[10] chronicle_id: 09022164801d240c - object_id: 09022164801d241a creation_date: 28/04/2016 12.26.20  version: 1.0.8.0 (CURRENT)

Why the 2 first versions are numbered as 1.x and the other ones as 1.0.x.0? Is there a way to have a common versioning policy with the same i_chronicle_id? I always use the VersionStrategy.NEXT_MINOR.

If I try to create a major version with the same i_chronicle_id (the 11th in my idea), I receive an error : "cannot save [object_name] since is immutable".

If I try another 6/7 versions of a new document (other i_chronicle_id) and after the checkout I try to checkin a major version, if I use the VersionStrategy.SAME_VERSION I continue viewing only a document with version 1.0 and the content is not the last one I added.

What's the use of VersionStrategy.SAME_VERSION if I can't change the content?

When I use the VersionStrategy.NEXT_MAJOR the numeration is as I expect: 1.0, 2.0, 3.0.

Can you help me please?

Thank you in advance

Aqualung

Alvaro_de_Andres

if you version 1.0 to next major you get 2.0. If you version 2.0 to next major you get 3.0. But you've versioned 1.0 (non current, as your current was 2.0) to next major, which causes a new branch to be created: 1.0.1.0. Then you've versioned to next major 1.0.1.0, which results in 1.0.2.0 and so on.

anupatnaik

This is called Branching of versions in Documentum.

When you create a minor version on CURRENT version 2.0 => you get 2.1, 2.2, 2.2 etc.

When you create a minor version on non-CURRENT version 1.0 => you get 1.0.1.0,1.0.2.0  and so on.

When you create a major version on either of the existing versions => you get 3.0, 4.0 etc

Branches in a version tree are created whenever changes are made to a non-current version in the version tree. Branching allows us to make changes to an older version while marking that the changes were done from an older version.

Haroon_A

What's the use of VersionStrategy.SAME_VERSION if I can't change the content?

You can checkin as same version only the CURRENT version. Previous versions are immutable and cannot be checked in as same version.