You can configure the system to prevent the UI from automatically caching the result of method calls that are executed in the business logic to retrieve metadata for screens and browses. It may be important to suppress caching in some situations; for example, if a method is customized, and does not return the same data in all cases.

You can suppress automatic caching using the CachingExceptions setting in the client-session.xml template, and homeserver.config.template. Typically, the CachingExceptions setting contains a list of components or query names that are normally included in the cache. You can then use the CachingExceptions setting to indicate that the system must suppress caching for calls to a particular component or query. For example, the following setting suppresses caching for all method calls and query calls to the component BSaf, and for the query BGL.SelectGL:

CachingExceptions = “BSaf,BGL.SelectGL”.

The CachingExceptions setting is processed by the code that implements the caching mechanism. If the CachingExceptions setting applies for a particular component or query, the system does not write data to the cache for that query or methods called on that component.

The next time the method for the component or the query is run, the cache will be empty, and this forces the method or query to be re-executed.