Well it's actually already on documentation :D
https://docs.bmc.com/docs/display/public/ars81/Cache+Settings+parameters
https://docs.bmc.com/docs/display/public/ars81/Cache+Settings+parameters
On 12 Feb, 2014,at 10:11 AM, "laurent matheo" <lm...@me.com> wrote:
I guess the help will be updated in the future, BMC didn't explain the "sync in cluster" new option as well (it's visible in the screen capture there):
https://docs.bmc.com/docs/display/public/ars81/Using+the+sync+cache+option
It seems that all mid-tier will sync altogether now (?)
On 12 Feb, 2014,at 09:50 AM, Rod Harris <r...@smapps.com.au> wrote:**Hi Jason,Wasn't this "new" feature just going back to the way it used to be prior to 7.6.3? In 7.5 and earlier you could just set your cache expiry to 0 and then only ever have to flush the mid-tier, not the client's browser. Since 7.6.3 the behaviour where you need to flush the local cache as well as the mid-tier for form changes etc was sprung on us and now has there been a rethink?Yes I much prefer the "new" behaviour which I believe is similar to the way it worked in mid tier 7.5 and earlier.Rod_ARSlist: "Where the Answers Are" and have been for 20 years_On 12 February 2014 16:04, Jason Miller <jason.mil...@gmail.com> wrote:**Now that 8.1 SP1 is public (at least for AR and CMDB)... Mid Tier 8.1 SP1 has a new capability where users are not suppose to have to clear their cache to pick up MT changes._ARSlist: "Where the Answers Are" and have been for 20 years_
Notes
- Starting with BMC Remedy AR System Service Pack 1, you need not manually flush the browser cache whenever there is a change in forms and other metadata in the AR System server. The changed forms are automatically fetched from the mid tier and are reloaded in your browser.
The way I understand it this doesn't remove the need to sync/flush MT cache as an admin but removes the next step where we have to tell our users to clear their browser cache.Too good to be true? Does it really work? I haven't had a chance to pound on it yet. I thought I would share this happy news since this has been an obvious pain point in this community and to our end users.Jason
