(This page is under construction, click here to see legacy documentation.)
Overview:
Caching is a term used when data is stored for use by an application in order to increase the loading and processing speed of recently or frequently accessed data. Workbench uses caching to speed up users' interactions with web pages that have already been loaded. This is why you may notice that a screen loads more slowly the first time or in the morning, but faster later on.
A side effect of this caching happens when certain settings are changed in Workbench. If that page was cached, the setting's new effect may not take place immediately. To counteract this, system administrators are able to clear the application cache using this screen, forcing the browser to reload all screens anew including any settings that have been changed.
Screen Guide:
Above is an example of the Application Cache, with many pages of data. Clicking Reload will refresh the list screen with any changes that have happened since first loading. The Clear button will empty the current cache, forcing browsers to replace the cache with new information.
| Note |
|---|
Note for hosted clients: Sometimes it is necessary to click Clear twice in order to fully clear the cache. It is recommended for this to be done regardless as a precaution. |
Next Steps:
Once the cache is cleared, refresh any pages that you expect a change to occur and test the effect.
FAQs:
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
Process Flow: