Sirisuda Taylor, Unal Perendi, Jonathon Ronna, Ilya Khen, Shaun-Martin Lawless, Brian. Dejno, Douglas Campbell, Michael Scruggs, Corey Brown, Margo Brosnan, Craig Morrison, Mike Dowling, Liam Doyle, et al.:
While this is a defect with the Chromium engine and thus not RSA's responsibility to fix, remediation is being made available in the next set of Patches, which will be 184.108.40.206 and 220.127.116.11, both currently targeted for delivery on 2 July. Upgrading to 18.104.22.168 or 22.214.171.124 is the method of remediation for all RSA Archer customers who cannot wait from Google to patch the Chromium engine.
Due to the number of versions we officially support and the time delay introduced by, and level of effort involved in, producing build-specific swappable DLLs, creation of these will be done on a case-by-case basis only. Due to where this problem manifests in the Archer code base, a global Hot Fix to this issue for all currently supported versions is not possible.
Additional workarounds to the issue include:
- Changing field behaviors to use a display option other than "Values Pop-up",
- Reverting the browser version back to one that is on the RSA Archer 6.6 and Later - Qualified and Supported Environments Guide, and/or
- Upgrading your browser to a version of Edge/Chrome where the Chromium defect is fixed (currently showing in v85+).
Chrome v83 is not officially supported by any version of Archer available today. Please reference this document to see what we officially Support: RSA Archer 6.6 and Later - Qualified and Supported Environments
Our users are experiencing this issue with Google Chrome version 83.0.4103.97 as well. This seems to have started within the past week. When a user clicks the ellipse icon, sometimes they get a blank dialog box with the header showing "</head><body /></html>". If they close the dialog box and try clicking the ellipse icon again, then sometimes the dialog box loads correctly. Other times they get only the header. Seems to be random. We have not seen this issue when using IE. Seems to be something specific with the most recent release of Google Chrome. We are on version 6.4 P2.
It seems to be specific to the chrome engine as Scott mentioned. E.g. Edge Chromium updated to v83 behaves the same. Mmm, this is getting in fact problematic, as it is hard not to upgrade as most of the time Chrome is updated automatically.
I think, we need to target an urgent hotfix for this aligned with Google. This or that way, it is a huge impact that needs to be resolved as soon as possible. It is hard to keep end users in previous versions of Chrome etc.
Have you reported this to our Support team? As I said v83 isn't officially a qualified browser to run any version of Archer on, but if this is a widespread problem we need to assess the impact in terms of volume of cases created. Also worth noting I'm not able to reproduce this using Chrome v83 against RSA Archer Platform 6.8" data-type="space. Have any of you looked at upgrading a non-Prod environment (maybe not to 6.8 but to something later than 6.7 P4) and seeing if it continues to occur?