Query regarding r_immutable_flag

Hi all,

This is Subodh here and its my second post in this forum. I am a novice and want to learn more about Documentum.

Scenario: I was experimenting with Documentum developer edition 6.6. Created one file. After check-out and check-in couple of times (say till version 1.6), I tried checking out previous version 1.4 and check-in. It created a new current label object with version 1.4.1.0.

As per the content_server_fundamentals guide, the older versions cannot be checked out as r_immutable_flag is set to True.

Can someone please clarify on my understanding.

Regards,

Subodh

Find more posts tagged with

Documentum

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

aflowers001

take a look at branching for this scenario

All comments

aflowers001

take a look at branching for this scenario

Dragon_Warrior

Hi Andy,

Thanks for replying.

However, I am still confused with the concept. If r_immutable_flag sets to T once we version the document, why am I still able to edit the previous version content and check-in into the same version?

The Fundamentals guide states

1) When a user creates a new version of a document (or any SysObject or SysObject subtype), Content

Server sets the r_immutable_flag attribute to TRUE in the old version. Users can no longer change the

old version’s content or most of its attribute values.

2) You can modify the most recent version on any branch of a version tree.

The other versions are immutable. However, you can create new, branched versions of immutable

versions.

In this scenario, the version I am modifying is not the most recent version for that branch and I am able to save the content after editing in same version. So, I am not creating new version.

It would be really great if you can explain with some example or screenshot if my understanding is incorrect.