Cache Me If You Can
We wanted to capture a few notes about getting the PDF Preview function in the application to show the latest values – whether it is new expense entries or change in status. Since every user’s browser settings can be set differently, it is important to understand how these settings can affect the PDF Preview function.
Depending on the stage of the expense report in the approval process, it can retain various statuses. The initial status is always ‘Saved not Submitted’. When the expense report is submitted the status will change to other levels and consequently, the PDF will show the updated status. Also, as the user adds new transactions or make updates to existing transactions, the PDF content will change content-wise.
In 99.99% of the cases, the most recent entries/statuses are not visible in the PDF due to the cache settings of the user’s browser. If the settings are done correctly, the updates within the PDF would be instantaneous. In most cases refreshing the browser will show the updates. If doing a CTRL + F5 shows the updates, it proves that it is a cache setting issue (Basically CTRL + F5 re-downloads the page while just F5 reloads the content from the cache)
If your cache storage setting is large, you may need to clear the cache (periodically) to see the updated PDF. Alternately, the user may choose to reduce the cache setting to, say, 1MB. Here is how the cache can be cleared in some of the frequently used browsers –
(Make sure you are checking under the correct OS)
Internet Explorer | Firefox (the browser all cool people use :)) | Chrome
For the uninitiated, here are a few references to understand what the cache really is and it’s function.
Cache 101 – It is not cash spelled incorrectly
Cache 102 – link 1 | link 2 (a technical note from friends at Cisco)
Hope this quick guide helps you understand how your browser’s settings play a vital role in the application’s functionality. As always, let us know if there are any questions – firstname.lastname@example.org.