Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Document Types | Creating an IS Document Type | Derived Types and IS Document Types | *doctype Fields in IS Document Types
 
*doctype Fields in IS Document Types
When IS document types are registered with their XML schema types, Integration Server adds a *doctype field to the IS document type of both the base document type and derived document types. When using the IS document type in Designer, Designer lists the valid values you can select for the *doctype field.
*For a base document type, the list contains the fully-qualified names of all the derived document types that can be substituted for the base type.
*For a derived document type, the list contains only the fully-qualified name of the derived document type itself.
The *doctype field is of use when using an IS document type for a base type. Integration Server uses the derived document type you select to validate documents (IData objects) against the IS document type. It also uses the derived document type you specify when converting documents (IData objects) to XML. As a result, the derived document type that you select in Designer should correspond to the schema type name that Integration Server should use for the <xsi:type> attribute in the XML.
For example, you might have a Document field for an invoice address. To indicate that the structure of the invoice address uses a derived type that represents an address in the United States, for the *doctype field select the name of the appropriate derived document type (for example, docType_Ref_order_USAddress).