handle check in as same version and do save in TBO

While check in as same version doSave() method is called (not doCheckin()). I want to run a functionality in TBO on CheckinAsSameVersion but do not want to run in each doSave call. How to handle Save and CheckinAsSameVersion differently in TBO doSave method.

Find more posts tagged with

Documentum

Comments

JorgKrause

Hi,

this is simply the way the underlying DFC classes are designed to work, and the concept of checkin as same version is simply a save to the repository.

If you need to apply certain logic if the save is triggered from a clients "Checkin as same version", you could check whether the object is checked out at the time of save call.
However, this isn't bulletproof either, since you may call a simple save on a checked out object from anywhere.

The only save way is to apply this different handling on the client side.
In short, it's pretty difficult to handle these operations differently, since there is no difference at all.

Jørg

PanfilovAB


protected boolean isCheckin() {
    StackTraceElement[] ste = new Exception().getStackTrace();
    for (StackTraceElement e : ste) {
        String clazz = e.getClassName();
        if (!DfCheckinObject.class.getName().equals(clazz)) {
            continue;
        }
        if ("checkin".equals(e.getMethodName())) {
            true;
        }
    }
    return false;
}

sunnybatra

Hi Jorg,

Thanks for the response. I too thought of this but as a last option

I am looking for some thing handles by Documentum Out of the Box.

Regards

Sunny

sunnybatra

Hi Andrew,

This is a purely java way to handle this. Have you ever used this somewhere or Would you confirm if it is a preferred way to handle it ?

Regards

Sunny