One of the most common questions from developers who are learning about Documentum for the first time is:
Why doesn’t my custom type show up when I try to create a new document?
In order to create custom object types, most developers read Documentum Application Builder (DAB) User Guide or Content Server Fundamentals. Creating a new custom type with custom attributes is relatively straightforward using DAB. Assuming you add the attributes to the Display Configuration correctly, you should see the attributes in Webtop. Wrong. Getting them to show up in Webtop requires a few more steps that a lot of new developers overlook. Let’s review this first:
Anytime you modify an object type (and check it in of course), you should always:
- Run the data dictionary publishing job – or issue publish api
- Restart Webtop application server – or clear the dmcl cache on the application server
If you follow these two simple steps, your custom attributes should show on the import page when you select your object type. Now, when you click on File->New Document, you should see your custom type as well. Wrong.
The New Document feature was built on the principle that newly created documents should be based some sort of corporate document template for a given object type – sort of like a Microsoft Word template. If you understand the idea of a template, then the step makes absolute sense. You need to import a document template (eg Word template) into the “Templates” cabinet and select your custom type. Once you have a document of your custom type in the “Templates” cabinet, the File->New Document will have your custom type in the Type picklist.
One other note, you need to import one document per custom type/per format. If you imported a Word template, do not expect to see your custom type show up for a Powerpoint format.
One last note, this behaviour has changed in 5.3. If you do not import a document template, Webtop defaults format to none and will create a “content-less” object.