Filter log

The filter log file shows all of the filters that were checked during an operation. If a filter was executed, the log also provides a list of the operations performed.

By default, the log file is named arfilter.log. 

This log is especially useful for checking the interaction of your filters and for verifying whether a filter is performing correctly.

The filter log format is similar to the SQL log format, but the information in the filter log is displayed over multiple lines. The log has the following characteristics:

• Each line starts with a tag that identifies it as being a filter logging line (<FLTR> ).
• A time stamp line is written for every operation that triggers filters.
• A line indicates that processing has started and the operation is being performed.
• A line provides details about the workflow object mode, indicating whether the object is Unmodified, Overlay object, or Custom. This information helps in easily troubleshooting filter related issues. Additionally, the log specifies the filter stack level and the corresponding filter number within the stack.
• As each filter is checked, a message is written that includes the name of the filter, its escalation order, an indication of whether the filter passed the qualification, and any action taken with their results.
• The last line contains a closing time stamp.

Phases 1, 2, and 3 of filter processing appear in the filter log. As AR System checks filters, all notify and run process actions are deferred to phase 3. Phase 3 begins when phases 1 and 2 are completed, and the database has been updated. In phase 3, all deferred filter actions are run. This information enables you to track the filters that are being checked, the filters that are running, and the actions that are being performed.

For more information about filter processing, see Filter-processing.