Liam Doyle - 184.108.40.206.1 suffers from this as well. The Archer fix, if implemented, needs to be a hotfix that addresses all supported versions. Upgrading Archer is not a realistic workaround because its too expensive to patch this issue and take on all the new issues any newer version introduces. If testing were adequate historically or release notes were comprehensive, that might make the solution easier to swallow, but that is not the case today. The pain on the front line is far greater than making good on the term "Supported Release" at Archer. RSA really should break this cycle of Catch-22 regarding "supported versions". If ever there were a time for a hotfix that worked for all supported releases, this would be the time.
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 220.127.116.11 and 18.104.22.168, both currently targeted for delivery on 2 July. Upgrading to 22.214.171.124 or 126.96.36.199 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+).
I agree with Doug's observation and also understand why a new release of Archer is the only solution.Having said that, the fact installations have to disrupt their entire user base and potentially introduce other errors/changes just to resolve a browser incompatibility is less than optimal. The Archer team receives all desktop software prior to its general distribution across the company but we cannot duplicate how our users use the system. It is a bit like IBM saying an account has to install a new version of z/OS (or whatever the current product is) just to resolve a simple problem.
The location in the code where the change occurs makes a global Hot Fix impossible.
Can you tell me more about what you'd like to see from RSA in terms of "adequate testing" and "comprehensive release notes"? Recognizing that we operate in the software industry and we can never catch every defect before release, and that the majority of our client base doesn't consume in full the documentation we do produce today, I'm curious your views as to where we are falling short in this area and what gaps exist to where you'd like us to be.
I, too, wish there was an easy button here, but there just isn't. This Chromium defect has forced us to make a change in an area of the code that requires a patch release as the delivery vehicle. Alternatively, you can wait for Chrome / Edge to correct their defect in a future release of the browser or modify your configuration to not use the Values Pop-up display option.