Set this option to YES to indicate that the filter or command handler should stay active even when it is not visible.
This option is recommended for heavily used filters and command handlers. Using it usually sacrifices memory usage for a performance increase.
Alternatively, setting this option to NEVER can minimize memory usage. The NEVER Stay Active option indicates that when you move between business objects, any inactive filters or command handlers (i.e. ones that are on tabs that are not visible to the user) should be terminated. This means that their uTerminate methods should be executed. (Note: Visible/active filters or command handlers cannot be terminated because the user may redisplay them at any time).
DEFAULT sets the Stay Active option for filters and command handlers to the value set on the new Framework level option, Stay Active Default for Command Handlers and Filters.Programming notes:
Normally a filter or command handler may be destroyed when the tab is no longer required and recreated when it is displayed (the random creation/destruction process is controlled by the system, not the Framework). If a filter or a command handler is heavily used, this process can be costly and can be avoided by setting Stay Active to YES.
If you have filters or command handlers that are specified as Stay Active, you can find out when the filter is being created for the first time (uInitialize) and when it is being destroyed (uTerminate) so that you can in turn yourself create and destroy things that your filter and command handler uses.
If you use uInitialize and uTerminate with a non-stay active filter or command handler they still work, but they may be invoked frequently as the filter or command handler is being created and destroyed, and they do not run every time the object is hidden and displayed.
This property is in the Commands Allowed tab and the Filter Snap-in Settings tab.