- Type-based business objects (TBOs) are the most common types of business objects. They correspond to custom object types in the Docbase and used to apply custom business logic to those object types. You can create a TBO by extending a DFC object such as DFDocument.
- Type-based objects allow developers to override the typical DFC Method to add validation logic or change the way that the original methods behave. You can also add your own custom methods for your own purposes. Because all objects are created via the object factory, your TBO is guaranteed to be used even by existing Documentum clients.
Create a TBO for a type in composer:
- Create a Type-artifact for your custom type (ie. custom_type)
- Create an interface ICustomType In this example we’ll use IDfDocument.
public interface ICustomType extends IDfDocument, IDfBusinessObject
{
//optional custom methods
//Overrides parent class methods
}
- Create a class CustomType that implements ICustomType and IDfDynamicInheritance, and also extends DfSysObject
public class CustomType extends DfDocument implements ICustomType, IDfDynamicInheritance
{
//implement optional methods you have defined in the interface
}
- Package the interface and implementation in 2 different jars.
- Create JAR Definition-artifacts for the 2 jars (ie. custom_type_tbo_impl and custom_type_tbo_inter).
- Create a Module-artifact of TBO-type (give it the same name as your custom type: custom_type) and set the implementation-jardef (+ set the class) and interface-jardef + optional dependencies or required modules.
- Install the Composer Project in the docbase.