Filters

Use native filters or IBM Engineering Lifecycle Optimization - Publishing filters to limit the amount of processed data. Not all data sources support native filters, but use native filters whenever you can.

There are two ways to filter data:

  • Engineering Publishing filter: This filter is a JavaScript expression that uses the data attributes of the entities that are returned by the query. These filters are processed when data is extracted from the data source.
  • Native filter: These filters are plain text, interpreted by the data source, and in a format specific to the data source type. When a query is run, only the data entities that match the filter are returned.
    Note: The native filter must be a valid filter as defined by the data source. No validation is completed. An invalid filter might produce results that range from incorrect data in the output to failing the document-style report generation.

Not all data sources support native filtering. You cannot define a native filter for data sources that are accessed through the Generic XML input driver of Engineering Publishing. The only exception is for the data sources where the filtering can be specified in the URL.

Tip: Use native filters whenever possible. Native filters are more effective and generate document-style report faster than Engineering Publishing filters.

Results

When you apply a filter to an element, the element displays with an Filtering icon icon in the template content editor.
A paragraph element with a query and a filter applied