Day 2:
Update on this issue.
In the expectation this was a Chrome cache issue, have tried installing Cache Killer.
Interestingly this seemed to solve the problem on one machine but not on another.
There are a number of places in the app where the same functionality exists for different Access Levels.
In all but 1 place the Operation was being sent to a New Tab rather than default. Hence tried setting the problem one to New Tab also.... No Go
But, here is a clue....
When I invoke the operation the PDF screen that gets displayed has this in the title bar...
http://10.31.1.12/AwareIM/DOCS_6548626/EMPLOYEE%20LEAVE%20APPLICATION.PDF
If I then close that and invoke the same operation on the next record the PDF screen shows EXACTLY the same thing. http://10.31.1.12/AwareIM/DOCS_6548626/EMPLOYEE%20LEAVE%20APPLICATION.PDF
Watching underneath at these temporary DOCS folders being created, I cannot understand what their lifecycle is and when Aware decides to create a new one.
Clearly invoking the same operation from two different records DOES NOT create separate DOC folders. Aware uses the same folder and I am guessing this is why the browser takes the previous version in cache rather than the new version that has definitely been written to the temp DOC folder.
You will notice that the document name is EMPLOYEE%20LEAVE%20APPLICATION.PDF. Apart from exporting the report as some defined filename and re-importing to display (should not be necessary) can anyone suggest a way to give each new document a unique filename...like.... XYZ_EMPLOYEE%20LEAVE%20APPLICATION.PDF?
This way I might be able to have the browser understand that it is a new version.
