Creating Filters for Use with Universal Messaging
If a webMethods messaging trigger subscribes to publishable document types associated with a Universal Messaging connection alias, you can create:
A provider filter that
Universal Messaging applies to the documents that it receives.
Universal Messaging saves the filter along with the subscription to the document type. When
Universal Messaging receives an instance of the publishable document type,
Universal Messaging applies the filter.
Universal Messaging enqueues the document for the trigger only if the filter criteria is met.
Use the Provider Filter (UM only) column in the Condition detail table to specify a provider filter. For information about the syntax for provider filters for Universal Messaging, see the Universal Messaging documentation.
When you save a trigger, Integration Server does not evaluate the syntax of the provider filter. Integration Server passes the filter directly to Universal Messaging.
Note:
If the trigger contains multiple conditions that subscribe to the same publishable document type, Integration Server does verify that the provider filters are identical upon save. If the supplied provider filters are identical, Integration Server saves the trigger. If the provider filters are not identical, Integration Server throws an exception and considers the trigger to be invalid.
A local filter that
Integration Server applies to the published document header or document body after the trigger receives the document. Use the
Filter column in the Condition detail table to specify a local filter.
Create the local filter using the conditional expression syntax described in webMethods Service Development Help.
When you save a trigger, Integration Server evaluates the local filter to make sure it uses the proper syntax. If the syntax is correct, Integration Server saves the webMethods messaging trigger in an enabled state. If the syntax is incorrect, Integration Server saves the webMethods messaging trigger in a disabled state