Book a Demo

Author Topic: How to make HTML Report updates show in browsers?  (Read 3679 times)

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
How to make HTML Report updates show in browsers?
« on: November 21, 2014, 06:29:38 am »
I have been wondering about this issue for a while and I think it is time to see if there is a satisfactory solution.

I am creating (EA v 10.0.1009) HTML Reports of top-level models or packages, and placing the generated files on a server.  This works fine except that when I generate a new version of the same model or package the changes don't always show up in a browser.

I started with Internet Explorer (v 11 on Windows 8.1).  I went to the link for the model--fine.  I changed something in the model and put the new version of the HTML report on the server.  I refreshed IE--no change.
Next I opened Firefox on the same machine.  I had not opened the link in Firefox previously, and it showed me the new version.
I then made another change to the model, and neither browser showed the update.
We saw the same issue (as expected) with Safari on Yosemite.  (I haven't tried Chrome yet.)

After some research and testing, I found:
Forcing a page refresh (Ctrl+F5 on IE and Firefox, for example) does not retrieve the new page version.
I changed the setting in IE to "Check for newer versions of stored pages: Every time I visit the webpage." This did not work to see changes I had made prior to changing the setting, but it has worked to show the 4 changes I have made since.  I just had to refresh the page.  (I'm not sure what the equivalent setting is in Firefox--I didn't see one in the settings, but I haven't done a web search--or Safari.)

So, I have a workaround for IE, but it isn't so good because:
1) each user has to set this in their web browser(s);
2) it may have undesirable side effects.

I'm not a web developer.  My understanding is there is some metadata one can add to a page to force reloading.  If I know more about this, maybe I can add this to each HTML report (not what I want) or maybe we can get Sparx to add this so it is always in the generated HTML reports (may be the best solution).

Ideas?