Designer 10.7 | webMethods Service Development Help | Working with Document Types | Creating an IS Document Type | Creating an IS Document Type from an E-form Template | Notes About IS Document Types Created from E-form Templates
 
Notes About IS Document Types Created from E-form Templates
Keep the following points in mind when working with IS document types created from e-form templates:
*When an e-form template serves as the source, Designer creates a publishable IS document type. Designer adds the envelope (_env) field to the IS document type automatically. This field is a document reference to the pub:publish:envelope document type.
*If Integration Server is connected to a Broker at the time you create an IS document type from an e-form template, the resulting IS document type will be publishable to the Broker and will have an associated Broker document type.
*After the IS document type exists, any modifications to the content or structure of the IS document type will make it out of sync with the e-form template from which it was created. This makes it unusable with the associated e-form. When an instance of the e-form template is received, it will not match the IS document type
*Any changes to the e-form template after using it to create the IS document type results in the template being out of sync with its document type. If the source e-form template changes, delete the IS document type and the associated IS schemas. Then, recreate the IS document type from the latest version of the e-form template.
*When metadata about an IS document type created from an e-form template is published to the CentraSite registry, CentraSite uses the following name for the asset corresponding to the IS document type: e-formTemplateName:ISDocumentTypeName.
This allows multiple e-form templates to have the same name and for each template to be associated with one or more IS document types. Consequently, when searching the metadata repository for a specific e-form template name, consider using the “Contains” clause to search for the e-form template instead of the “Equals” clause.
For more information about using e-forms, refer to Implementing E-form Support for BPM.