Organizations Turn to Documentum to Rapidly Build Case-Based Applications
Applications Developed on Documentum Enable Customers to Reduce Cycle Time, Improve Compliance and Promote Business Agility
Today National Health Insurance Company (DAMAN) has built case-based applications using Documentum. Applications developed on Documentum enable customers to reduce cycle time, improve compliance and promote business agility.
Documentum follows Object Oriented Design (OOD) paradigm. Every element present in the system whether it is content object that contains metadata and reference for a specific document or image, or the simply the metadata exists as an object. To understand the system as a whole we need to understand the process and assumptions that are inherent in OOD, as well as the relations among the Documentum objects.
Successful design of Documentum implementation depends on how well we organize our objects to meet our specific requirements. Since Documentum allows simple to complex relationships among documents, we should be very careful in designing objects to achieve optimum design.
To store any kind of data, Documentum uses the concept of Object Types. Objects Types are nothing but a template defining the structure. Data is stored as object type instance which contains the structure defined in the Object Type definition. There are several object types available in Documentum for internal use. These object types can be extended to meet our business requirements.
In a nutshell, whatever information we store either it is a document or media file will be stored in the Documentum as object instance.
All of the Documentum object Types when we create the repository will start with dm_ prefix. Documentum allows us to extend these objects to accommodate our business logic. As in OOD, the derived object types share properties with their parent object types, and on the level of the derived object type properties can be added. Documentum passes even the security configuration of the super type to subtype. However we can override the security configuration at the subtype.
In Documentum terminology we call the parent object type as super type and child object type as subtype. Object type hierarchies enable consistency across the enterprise, and it also provides flexibility that is needed to address the specific requirement in business logic for individual departments or applications.
ليست هناك تعليقات:
إرسال تعليق