Hello,
It possible to use Documentum in order to supply and store the available values of an attribute for the filling of user via 2 solutions: Value Assistance/Mapping and Custom Object.
Here, the hierarchical diagram of Documentum objects : persistent object, dm_user, dm_acl, dm_sysobject, dm_document, ..etc.
Solution 1 : Value Assistance/Mapping
This solution consists to use the values mapping on the attributes of a custom type like subtype of dm_document.
These values mappings are configurable via COMPOSER:
- Advantages : Automatically check of data by DCTM that refuses the saving of documents with an incorrect value in single or multi-value metadata
- Disadvantages: Heaviness through the Composer
Solution 2 : Custom Object
This solution consists to use Documentum custom object in order to store the available values for an attribute.
- Advantages : Easy installation and maintenance
- Disadvantages: No automatic data check by DCTM
Example n°1 : the creation of a subtype of « persistent object » (WITH SUPERTYPE NULL) (Generating DQL queries to create a type via “genesis” SAMSON):
01 | DQL> genesis my_root_persistent_object |
03 | CREATE TYPE my_root_persistent_object ( |
05 | categories CHAR(64) REPEATING, |
Example n°2 : the creation of a subtype of « dm_document » (Generating DQL queries to create a type via “genesis” SAMSON):
01 | DQL> genesis my_root_document_type; |
03 | CREATE TYPE my_root_document_type ( |
04 | id_client CHAR(32) REPEATING, |
09 | refs_operation CHAR(25) REPEATING, |
13 | comment_hist CHAR(255) REPEATING, |
17 | merging_parents_id ID REPEATING, |
19 | WITH SUPERTYPE dm_document |
22 | ALTER TYPE my_root_document_type MODIFY |
23 | comment_hist CHAR(512), |
That’s all!!!
Huseyin OZVEREN
Related
