#188 Version Branching of Published Page Set

[Anonymous]

The published version of the page set can be incorrectly branched in the version tree by the following steps:

1) Publish the page set a few times (3-5?) - for each version, choose the next major version
2) Publish the page set one more time, but do so as a minor version

After step 2 - the version created will be branched. In other words, the version will not be 4.1 or 5.1, but something like 1.0.3.2

[Nobody/Anonymous]

Note - we have only been able to reproduce this on a 6.5 docbase (fedex_dev) when running the wizard on Beaumonts (7402/Wizard). If I run the wizard on my Tomcat instance, the versions create fine.

[George Steimer]

Ok, this one goes into the “you have got to be kidding me” category. Documentum apparently changed the way version labels are interpreted in the IDfSysObject#checkin method when you want to check in a major version. Before today, the wizard did something like this (obviously without the hardcoded 2.0):

doc.checkin(false, “2.0, CURRENT”);

That works great in 5.3 , but fails in D6 and D6.5. It actually doesn’t throw an error – the 2.0 version is created, but the CURRENT label is left on the previous version. After banging my head against the wall all afternoon, the correct code should actually be:

doc.checkin(false, “2.0,CURRENT”);

Yes – you are reading that correctly. The problem is the extra space before the CURRENT label. Basically, in D6, Documentum is interpreting that space literally. So the 2.0 version is created, but with a “ CURRENT” label. The real CURRENT label is left on the previous version.

Many thanks to Gretchen for her help – and for her flier suggestion that maybe the space is the problem.