It is considered a best practice to make changes to your OnBase configuration during periods of minimal use. While some changes occur in real time, many configuration changes require users to restart their OnBase Client before changes take effect. If you are running OnBase as a Windows Service, the Windows Service must be stopped and restarted before changes made to OnBase configuration take effect.
For changes to take effect in the Web Client, the Unity Client, and modules that communicate to OnBase through the application server, you can either reset the cache by exiting the Configuration module and clicking Yes, or by clicking Utils | Service Monitoring and clicking the Reset Cache button. From here, you can also configure whether you would like to be prompted with the ability to reset the cache upon exiting the Configuration module.
Using the Reset Cache option in OnBase Configuration or the Reset Server Cache option in OnBase Studio may have a negative impact on system performance. Requests to the Application Server will be forced to wait until the cache is rebuilt before they can be processed. Depending on the size of the OnBase system, as well as the current server load, the performance impact of resetting the cache may be severe. To avoid performance issues, only reset the cache of the Application Server during off-peak hours.