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; } } }

Documentum Backend - Docbase ID save

Alcaporzel

Hello friends,

as I have never developed something in Documentum Backend, i have a simple question. Maybe this task is not very hard, as I understand Java Development.

We want to setup documentum, that it will duplicate the docbase id in an extra attribute or table in documentum. We want this because after you moved a document into another repository it will have a new docbase id. We just want to simply save this first docbase ID parallel.

How do you make something like this and what do I exactly need?

Thanks

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

Haroon_A

An alternative to TBO would be to create a custom method/job that executes the DQL that was suggested.

You can schedule it daily (or hourly, depending on your need) which will mass update all the newly created documents. You may need to make it smart to not update the ones that are already updated, by adding a condition in where clause like WHERE custom_id <> r_object_id...

All comments

DCTM_Guru

You can simply run DQL (which is Documentum version SQL) query to update another custom attribute and set that value. Something like this:

UPDATE dm_document (all) OBJECTS

set your_custom_attr = r_object_id

Alcaporzel

Hello Johnny,

indeed, thank you.

The Problem is we need this automatically after creating a document.

Thanks

edit:

My thought is that i can maybe do this composer. create a new attribute. But how can I say to this attribute that it will get the docbase value on creating a document?

DCTM_Guru

You need to write a TBO (Type based Business Object) to override the doSave() event and copy the value there.

bacham2

It's not clear to me if you want to store the original r_object_id or just the docbase ID part (i.e. the digits 3 to 8 of the r_object_id). In the former case, you also need to override doSaveAs() in case a user copies a document. And doCheckin() in case a user checks in a document as a new version because each version has its own r_object_id (unless you choose save a unique identifer generated by yourself or some sequence and which would be shared across all versions). There are probably a few other methods to override.

Haroon_A

An alternative to TBO would be to create a custom method/job that executes the DQL that was suggested.

Alcaporzel

Hey,

this sounds for a best solution for me.

Thanks all for your suggestions, this helped me a lot!

Kind Regards

DCTM_Guru

Keep in mind that there is no guarantee that job will run as expected (e.g if you have other jobs running, the window for this job might fall outside of your expected duration). Also, there will always be a "gap" where the object ID is not saved in the custom attribute.

TBO is executed as part of the save transaction, you will never have this issue.

Haroon_A

I would only ensure, before exporting any document outside Documentum, to make sure the job is run (or even better run it manually)