Custom Output Filters

Custom filters on the output for Build Model, Build cBase, Measures, and Integ process nodes can prevent certain unpreventable warnings from hiding real warnings. This feature needs to be used with great care because warnings are there for a reason, but sometimes warnings are hard to work around and can obscure any real problems when examining a Production process from a high level.

Note that the use of custom output filters does not affect the output for a node or suppress warnings. Instead, the custom filter affects the outcome state of a node (Success, Warning, Error), which in turn changes the color of the node. As always, these have a natural hierarchy; 99 Successes are trumped by 1 Warning, which is trumped by an Error.

If you decide to create a custom output filter for a node, run the node first so you have a log file to examine. Then, configure the filters. The basic idea is:

"If the output row (Contains/Starts With) <x> then treat this row as (Failed/Succeeded/Warning)."

See the Edit Custom Output Filters dialog available from the Custom Success State Rules attribute in the Build Model, Build cBase, and Measures process nodes, and the Custom Output Filters attribute in the Integ process nodes.

These filters can, for example, promote data integrity warnings to errors as well as demote suspiciously similar warnings to nothing.