nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Will doDestroyAllVersions() call doDestroy()?

RaphaelBosshard

I have a custom document type (cus_document) which needs special attention when being deleted. For that I have created a TBO with a customized doDelete() method. However, there is still the doDestroyAllVersions method. How do these two work together? Will a call to the doDestroyAllVersions method call all doDestroy methods for all cus_documents? Or will doDestroyAllVersions call doDestroyAllVersions for all cus_documents?

Any help is appreciated.

Find more posts tagged with

Documentum

Comments

CláudioGil

Actually destroy() will delete the object and destroyAllVersions() will call prune() on the 1.0 version (r_object_id = i_chronicle_id). To control the deletion of an object you must override both doDestroy() and doDestroyAllVersions().

RaphaelBosshard

From the DFC javadoc:

void prune(boolean keepLabels)
           throws DfException

Removes unwanted versions of an object.

What are 'unwanted versions' in this context? All the 'old' versions (r_object_id != i_chronicle_id)? Will the TBOs methods be used for this 'pruning'?

CláudioGil

Prune removes a version branch and it's root. So if you prune version 1.0 you remove all versions. But if you have versions 1.0, 1.1, 1.1.1, 1.2 and you prune 1.1 then you are left with 1.0 and 1.2. I think this process is described in the Content Server Fundamentals or one of the core documents about the internal semantics.

RaphaelBosshard

Ah, thank you very much. You have been most helpfull. Will take a look at that.

liaojiyong

No , doDestroyAllVersions() and doDestroy() call different docbaseapi to destory obj.

RaphaelBosshard

Thanks to the help of liao jiyong and Cláudio Gil, I think I can summarise the answer to my question, in case anyone has ever the same question:

Short; no, doDestoryAllVersions(...) will not call doDestroy(..)

Long; instead, doDestryoAllVersions(...) will first prune on the 'i_chronicle_id' and than flush the object out of the repository.

Now a wag of the finger to EMC/Documentum: 'Removes unwanted versions of an object.' is not what I call adequately documented. What are 'unwanted' versions?

Anyway, thanks for helping me out!

Arbee

Francois Dauberlieu

It's supposed to be all version between version 1.0 and the latest current version, leaving both of them.

I can't remember what happens if version 1.0 has already been deleted. Will it keep the lowest version and the current version or only the current version ?? can;t remember, you'll have to test yourself, unless somebody else in here can remember

liaojiyong

prune----------- removed a branch from the version tree of object


//(eg1: 1.0, 1.1, 2.0, 2.1) 
IDfSysObject.getImplicitVersionLabel='2.0'
IDfSysObject.prune(false);(left versions:1.0)//(eg2: 1.0, 1.1, 2.0, 2.1) 
IDfSysObject.getImplicitVersionLabel='1.1.1.2'
IDfSysObject.prune(true);(left versions: 1.0, 1.1,2.1) //(eg3: 1.0, 1.1, 2.0, 2.1, 1.1.1.0, 1.1.1.1, 1.1.1.2, 1.1.1.3) 
IDfSysObject.getImplicitVersionLabel='1.1.1.2'
IDfSysObject.prune(false);(left versions:1.0, 1.1, 2.0, 2.1)//(eg4: 1.0, 1.1, 2.0, 2.1, 1.1.1.0, 1.1.1.1, 1.1.1.2, 1.1.1.3) 
IDfSysObject.getImplicitVersionLabel='1.1.1.2'
IDfSysObject.prune(true);(left versions: 1.0, 1.1, 2.0, 2.1, 1.1.1.0, 1.1.1.1, 1.1.1.3)