Checkout not cancelled for dependencies

Forum|Forum|13 years ago
March 20, 2013
2 replies
1162 views

(Using the SharePoint connector) I've observed that if I check out a file and also check out its dependencies automatically, and then cancel the checkout on the original file, the dependencies are all left checked out. Their checkouts must each be cancelled manually. Since there can be dozens or even hundreds of dependencies, this makes for a lot of work. It would be better if their checkouts were cancelled automatically along with the parent checkout.

CMS

This topic has been closed for replies.

A

Anonymous

In later tests, I wasn't able to reproduce this. Dependent checkouts are cancelled automatically, as they should be.

M

max_drawdown

Inspiring

(FM12 to Documentum),

I see similar behavior upon the initial upload of a deep-structure book from the CMS interface to Documentum.

Deep structure = book with chapter files, each chapter has text insets and referenced graphics, and the insets, graphics files, and books, are stored in separate sibling folders.

The CMS interface correctly uploads all files, creates the folder structure, and creates Documentum "virtual documents" for each chapter and the book. So far, so good.

I then use the CMS interface to upload a separate book -- think of it as a utility book, or workbench, not a deliverable -- that uses some of the same referenced graphics, insets, or chapter files. The utility book is useful for maintenance tasks.

The good result: all top-level books are correctly implemented as virtual documents and none of those books remains in a checked-out state.

The problem: some of the chapter files, referenced graphics, and inset files, remain in a checked-out state even though I never explicitly checked them out. This result implies some technical risk, but I do not know how to assess the worst-case impact. The best-case is that I use another Documentum interface (Webtop) for rapidly identifying and then checking in (or discarding checkout of) all of "my" files that are still checked out.

I'm pretty sure this is a bug, but I'm open to re-configuration ideas.