In a document-type-specific burst configuration file, the dmsobjtype element can contain as many typerule elements as necessary to implement the desired element-to-object-type or source-type-to-object-type mappings. Object-type mappings are useful for associating a different workflow with a given source type or element. Note that you should use either an element-to-object-type or a source-type-to-object-type mapping in a typerule element. You cannot use both mappings in the same typerule element.

If unspecified, all objects created by Arbortext Editor are assigned to the Dynamic Document object type. This type is a subtype of the EPM Document type. You can use the targettype attribute to set the object type to be a subtype of the Dynamic Document type. However, you must specify a fully qualified subtype name in the following format:

The prefix is generated by reversing the internet domain for the default organization. Each component must specify the system name of each subtype, not the display name, as given in the PTC Server Type Manager interface. Consult your Arbortext Content Manager or Windchill documentation for more information about object types.

It is recommended that you define a different PTC Server subtype for each of your supported document types and configure the burst configuration files to specify the subtype associated with the document type for new objects. You can then use that subtype to narrow searches for objects and to specify custom output.

Element-to-object-type mappings map an element name that you've specified as an object boundary, either by element name, attribute, or attribute value, to a PTC Server object type. Source-type-to-type mappings map a general source object class (that is, text or graphic) to a PTC Server object type. While you can burst a document based on element attributes, you cannot assign a PTC Server object type based on element attributes in the burst configuration file. You can do this using an AOM customization. See the sample files in the Arbortext-path\adapters\com.ptc.prowt.arbortext\samples directory for more information.

For an element-to-type mapping, enter a typerule element with the following attribute settings:

For a source-type-to-object-type mapping, enter a typerule element with the following attribute settings:

Note that each typerule element can have either an elementname or a sourcetype attribute, not both.

If the dmsobjtype content does not include a typerule element for one or both source types, the PTC Server connection will use the object class rules for the unspecified source type from the system-wide burst configuration (that is, atidefaults.bcf). Document objects (that is, source type of text) will use the dmsobjtype element. Graphic objects (that is, source type of graphic) will use the dmsgraphicobjtype element.

A dmsobjtype element must be a child of createarg. The default axdocbook.bcf file that is provided for use with the PTC Server connection does not include a sample dmsobjtype element.

Following is an example of a dmsobjtype element that assigns text objects to the Draft Document object type, graphic objects to the Graphics object type, and the Warning element to the Legal Document object type: