Filtering

To add a filter:

  1. Click Connect > Data Flows.
    A list of existing data flows is displayed.
  2. Select the document flow where the filter must be added
  3. Click Details to open the document flow modeler
  4. Add a Filter activity to the flow.
  5. If the preceding activity provides more than one document type, use select for documents as filter.
  6. Click the Attributes tab;
  7. Select the attributes that must be used in the filter.
    You can select the attributes in these ways:
    1. From document content.

      See Selecting attributes.

    2. From headers

      • Click + From Header.

      • Select Document or All documents from the drop-down list.

      • Select header from the drop-down list. When All documents is selected the Custom headers are not shown.

  8. Click the Conditions tab.
  9. Specify the conditions for the selected attributes.
    See Defining conditions. After activating the flow, the ION Service ensures that messages are filtered according to the specified conditions.
  10. Select the used condition for the filter.

Notes:

  • Multiple flows can be defined using the same connection points and document types. In ION Service those flows using a logical disjunction ('or') are combined. For example; an active flow orders that SyncSalesOrder documents having status X must be sent from A to B. Another active flow orders that SyncSalesOrder documents having status Y must be sent from A to B. Then all SyncSalesOrder documents having status X or Y are sent from A to B.
  • Filtering is done at message level. Either the whole message is delivered or nothing. The message is not partly delivered (for example by only including the relevant purchase order lines).
  • When, using attributes that occur multiple times in a document the document is passed on if at least one of the lines matches the filter. For example, attributes from an order line can occur multiple times.
  • The actionCode in BODs is not changed by the filtering. If the first BOD with actionCode Add is filtered out, and the second BOD for the same object instance with actionCode Update is passed. The actionCodeUpdate.
  • Filtering is not applied to BODs used is Event Management. If an application publishes SyncSalesOrder and an event monitor exists for SalesOrder. Then all SyncSalesOrder BODs are delivered to the event monitor, even if in the document flow a filter is specified.