Updating to a new release

[RICHARD RUTA]

I need to update to the newest release to enable a mobile application that has been running in a development environment . I’m currently running:

1. Version 4.0.3 in production
2. Version 4.2.4 in development.

I guess that means that I am going to update both to the newest version: 4.6.1.

I’ve hesitated to do this. In the past when I updated to a new release, I’ve had to clear the cache. That was fine when we had internal users only. We now have a client base using your software. I was wondering, first of all, if you think all will need to clear their cache? And second, if all do need to clear it, how would you advise them? I'd appreciate a recommendation from any Profoundui user who might have gone through this.

[Scott Klement]

The browser does not cache the code permanently, it only holds it for a short while. If you go right back into Profound UI immediately after an update, sure there's a good chance that your browser will still be caching the data -- so to see the change, you may have to clear your cache.

But, if you wait a few hours, the browser should stop using the cached version and download a new version from the server -- in which case, there's no need to update the cache.

So, my suggestion would be to update when people will be out of the office for awhile. For example, wait until the employees leave for a weekend (assuming you don't work on weekends) and then do the update Friday night. By the time people attempt to use it again on Monday morning, the cache will have expired and the new version will be used.

Another approach might be to have code that calls the pui.refresh() API. This will unload PUI from the browser cache and automatically reload. If you have a screen that they'd see at the start of the process, use pui.refresh() from that screen to force pui to reload.

Does that help?