- BOF’s main goals are to centralize and standardize the process of customizing.
- Set of functionality introduced in Documentum 5.3 that allows developers to extend the Documentum Foundation Classes (DFC).
- Always executes when it is supposed to, regardless of the client program.
- Inherits, and can extend, the implementation of core Documentum functionality.
Benefits Of BOF:
- Reduced development time
- Abstraction of Business Logic from Presentation
- Encourages Reuse
- Portable across Applications
Types Of Business Objects:
- Type Based Object(TBO)
- Correspond to custom object types in the Docbase
- Allow developers to override the typical DFC methods to add validation logic or change the way that the original methods behave.
- You create a TBO by extending a DFC object such as DFDocument.
- Service Based Objects(SBO
- Provides general purpose functions for your application to use.
- can be used across docbases, even accessing multiple docbases at once.
- Can be called from custom GUI or from within TBO
Documentum Business Object Registry:
- Allows developers to “register” their custom business objects with DFC’s object factory.
- At runtime, DBOR provides the appropriate class name to the DFC method, which loads and instantiates the Java class and returns the reference.
- Once registered, DFC will automatically create and use your business object whenever it is dealing with a document object belonging to that custom object type.
- Example: [SBO interface name]=service,[SBO class name],[version]
com.myProject.myPackage.IStartAutoNumber = service,com.documentum.myProject.myPackage.StartAutoNumber,1.0[object_type]=type,[TBO class name],[version]custom_doc=type,com.myProject.myPackage.tbo.customDocTBO,1.0