Checking out documents that are bound to children in Documentum

[joe.hopkins]

Has anyone worked with documents in Documentum that are bound to older versions of the children? There seems to be an issue with XMetaL related to this....

After checking out a document with read only descendants, XMetal fails to load the references correctly if the descendants are not the CURRENT version in Documentum.

We are using XMetaL Documentum Adapter 2.1.0.084 with XMetaL 6.0.1.030 in a Documentum 6.5 Sp1 environment.

Does anyone have any ideas?

[Derek Read]

There is no feature for working with versions prior to the current version with the Documentum + XMetaL integration (all releases to date). The software is designed to always check out the current version of any document.

[joe.hopkins]

Hi Derek, Thanks for the response!

To clarify, we do not actually need to work with the references, they just need to resolve in XMetaL. We check out the document (with read only references) via standard Webtop (not the DA adapter). We then open the document locally with XMetaL. Instead of resolving the references locally, XMetaL is going to the repository and trying to download them. Is this by design? If so, is there a plan to update XMetaL so that it supports working with documents that have been bound to older versions of its references? As a work around we have found that we can copy the files out of our Checkout folder, make changes in XMetaL, then copy them back into the checkout folder.

Thanks.

Attach are screenshots of the issue.

[Derek Read]

It would help if we could see one of the reference href/conref attribute values to be really sure we are on the same page.

To clarify, we do not actually need to work with the references, they just need to resolve in XMetaL. We check out the document (with read only references) via standard Webtop (not the DA adapter). We then open the document locally with XMetaL. Instead of resolving the references locally, XMetaL is going to the repository and trying to download them. Is this by design?

This is by-design. However, you can alter this behaviour in the dialog Tools > DITA_Options > Update Content (tab). Try unchecking one or both of the "Refresh references when opening..." options. That should stop XMetaL from trying to auto-resolve things.

If so, is there a plan to update XMetaL so that it supports working with documents that have been bound to older versions of its references? As a work around we have found that we can copy the files out of our Checkout folder, make changes in XMetaL, then copy them back into the checkout folder.

Our development team has this listed as an item in their backlog. However, other feature requests have so far taken precedence.

[joe.hopkins]

Here is xml from the parent file that references Content_02176. The file its referencing is local, but is not the current version in Documentum. When I turned off the "Update Content" options, none of the references came though (even though they were available locally).


<lcInstruction id="lcInstruction_88D6B0B3836E420AB5054155E7657471"><p><ph dctm:link_version_label="V2" conref="Content_02176_4.xml#id-08d5ba95-64d5-4103-b491-e2d5d5a59aea/4p1"><?xm-replace_text Phrase?></ph></p><p><ph dctm:link_version_label="V2" conref="Content_02176_4.xml#id-08d5ba95-64d5-4103-b491-e2d5d5a59aea/4p2"><?xm-replace_text Phrase?></ph></p></lcInstruction>


Do you know of any other work arounds besides copying the files out of the checkout folder?

Thanks!

[Derek Read]

There is nothing in the product that would offer more, for that you would need to wait for some future version.