Important Considerations When Modifying Publishable Document Types

When you modify a publishable document type (for example, delete a field or change a property), the publishable document type may no longer synchronized with the corresponding provider definition (Broker document type or Universal Messaging channel). For information about how to synchronize document types, see About Synchronizing Publishable Document Types.

Any change is automatically propagated to all services, specifications, document fields, and document list fields that use or reference the IS document type. (This happens when you save the updated IS document type to the server.) To view a list of elements that use the IS document type and will be affected by any changes, use the Find Dependents command on the right-click menu.

If you make the document unpublishable by changing the Publishable property to false, publishing services and processes that use the publishable document type will fail. For more information about making a document type unpublishable, see Making a Document Type Unpublishable.

When you change the messaging connection alias assigned to a publishable document type, you might need to synchronize the publishable document type with its associated provider definition.

When you change the messaging connection alias assigned to a publishable document type, Integration Server reloads any webMethods Messaging Triggers that subscribe to the publishable document type.

Changes you make to the contents of a publishable document type might require you to modify the filter for the document type in a trigger condition. For example, if you add, rename, or move fields you need to update any filter that referred to the modified fields. You might also need to modify the service specified in the trigger condition for the webMethods Messaging Trigger.

When you change the encoding type of a publishable document type, you might need to synchronize the publishable document type with the provider definition on Universal Messaging.

You might also need to change the provider filters for any webMethods Messaging Triggers that subscribe to the publishable document type. When the encoding type is IData, it is optional to include _properties in the provider filter. However, when the encoding type is protocol buffers, you need to include _properties in the provider filter. If you want a provider filter that operates on the contents of _properties to work regardless of the encoding type, always include _properties in the filter expression.

For an IS document type created from an e-form template, 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.