This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Filter processing in BMC Remedy AR System server

The BMC Remedy AR System server processes filters in an execution order you specify. As the BMC Remedy AR System server considers actions in each filter, it categorizes those actions into one of three phases. (See Filter phases.) In general, actions are carried out such that database operations are deferred until after all actions that modify the database have been performed. At that point, a single database transaction is opened and all the database operations are performed. This keeps transaction time and table and row locks in the database to a minimum.

Some complex applications, however, require database operations to be performed immediately. For example, an application might be used as a subsystem of another application, where the results of the subsystem's work are needed immediately by the calling application. For more information, see Overriding filter processing phasing.


You can combine the Filter, SQL, and API logs to "see" how BMC Remedy AR System interacts with the database and how the different phases interact with each other, especially if you are creating complicated workflow. For more information, see Server logging modes.

For more information, see:

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.