TBO Override doCheckout method

Harish_Elango · 2022-01-31T08:21:49+00:00

There was an error rendering this rich post.

Hi All,

I have requirement for specific documents to be treated differently in a doCheckout method. I am able to override doCheckout method using TBO. For regular documents, i call super.doCheckout() to work as usual but for specific documents doCheckout should not retrieve file from file store and make the object locked for the user who can edit only metadata not the content. Please help how this can be achieved.

Thanks

Find more posts tagged with

Documentum

Comments

Hicham Bahi

First of all, doCheckout doesn't retrieve the content: this is done usually via getfile method or via ACS. Second, I'm not sure that TBO is the best approach here. This might have an impact on other components who may try to perform checkout. What client are your users using? Perhaps the best approach is to customize your client.

DCTM_Guru

As @bacham3 stated, this should probably be done as part of UI customization/configuration based on your application (e.g. webtop, d2, xcp, etc). That being said, if you want to do this in TBO, all you would need to do is check object type before you execute super.doCheckout. If it doesnt satisfy your criteria, dont check it out. A user who has WRITE permissions on the document can edit the metadata via properties page and doesnt have to "lock" the file, since editing properties page is typically a "quick" transaction.

Harish_Elango

Thanks @DCTM_Guru for your reply. Actually, One more measure i should take care is for those specific documents (which were moved to old/archived documents category) , i should not allow save or check-in as same version. So editing Properties page and doing save might save data on the current version. This should not happen. So wondering how this requirement can be implemented.

Hicham Bahi

Just give people VERSION permission instead of WRITE.

Harish_Elango

@bacham3 - I understand your suggestion but the archived documents are in million. It is really difficult to consolidate different ACLs, revisit them , get business approvals etc. So, looking for a way to restrict through dfc code like tbo. Thanks.

Hicham Bahi

Ideally, the number of ACLs should not be proportional to the number of documents. If they are, then this is a sign a bad design (with some exceptions, e.g. if your application revolves around collaboration, but that's not Documentum's strong suit).

DCTM_Guru

I agree with @bacham3 that any good Documentum application design would not create individual ACL for each document. Check to see if the ACL_name is the same for documents of the same type or same for documents that share the same folder. This will tell you if have "a lot" of ACLs to modify. I try to avoid ANY customization if requirements can be addressed by simple configuration changes (ie ACL change).