Creating custom data types in Documentum

I know we can easily create custom object types using Composer, but I want to create a custom data type so I can create custom attributes of this data type, not just the integer, string, boolean, etc., that Documentum provides.

Is this possible? I tried using aspects but no luck.

Find more posts tagged with

Comments

rawat_harish

Can you give more details on type of data types that you want to implement? And what extra behavior (like validation/ formatting) do you want to implement for these data types?

Thanks

Harish

Derrick

Instead of a data type TIME, I want to create a data type called TIMECODE, that will be of the format hh:mm:ss:ff (hours:minutes:seconds:frames). Each piece of the time code will be an integer. I want to give my custom attributes the data type of TIMECODE.

Am I clear? Clear as mud?

aflowers001

Hi,

Short answer is not possible. The definition of what is atored by Documentum is limited to those data types supported by DQL, which is a small, portable list available to be mapped to all client databases. I can see what you're after, domains as i've seen it called in some databases, and it would be nice.

Long (?) answer is that to do what you want you'll probably need to store it as a string and enforce the translation at the UI/Application/BOF level.

If you need searching in a WHERE clause then you may need to have a something else, possibly multiple properties, that can be used and are mapped from the real data field, probably via BOF TBO to be sure.

regards,

aflowers001

One option I just remembered is a registered table with the underlying database field type and validation defined. This could work as a 'related' item to the object in question but would again require coding to support it.

parasj

Unfortunately, Documentum's object model does not support nested data-types

You could consider using aspects ... e.g. you could create an Aspect called TIMECODE - and attach it to instances of your object

Note - There would several other design considerations required to be undertaken with Aspects e.g. Webtop and XForms don't show aspect values by default