Can we better categorize/organize browser issues?
I appreciate the effort to convert questions into PDN Support A searchable bug database is long overdue. Browser version is an obvious indexable field, and it should be indexed for searching.
We have users of a v6.2 users being upgraded to IE11. Your compatibility guide states that v6.x in compatibility mode is "unreliable."
We need more details than that.
The best I can do is search here:
https://mesh.pega.com/search.jspa?q=IE11
Here's the sort of record that would be extremely helpful:
I appreciate the effort to convert questions into PDN Support A searchable bug database is long overdue. Browser version is an obvious indexable field, and it should be indexed for searching.
We have users of a v6.2 users being upgraded to IE11. Your compatibility guide states that v6.x in compatibility mode is "unreliable."
We need more details than that.
The best I can do is search here:
https://mesh.pega.com/search.jspa?q=IE11
Here's the sort of record that would be extremely helpful:
| Header 1 | Header 2 |
|---|---|
| Browser | IE |
| BrowserVersion | IE11 |
| PRPCVersion | v6.2 |
| Category | EndUser-Attachments |
| Issue | Attachment control does not work in IE11. |
| Behavior | When user clicks on "Attach a File", an empty pop up is seen without any attachment options. |
| RootCauseRule | R-U-Function BrowserIsIE |
| RootCausePart | (function if above is JS file; step if above is Activity, etc) |
| Resolution | HFix-21442 |
JPMC
IN
Great idea Jon !
I have posted this in our internal portal as a potential enhancement for our portals. We would liek to tank you for this idea.
BNY Mellon
US
Thanks. Moreover, we're looking for a hotfix package of all JavaScript fixes in v6.2 -- filed an SR for that.
Pegasystems Inc.
US
Could you please update the thread with the SR if you have the number? This way we can track for you.
Thanks in advance!
Hi Jon,
The scenario you described which spurred you to suggest this idea is something I would like to comment on.
Compatibility view may be "unreliable". But using IE11 in its native mode(Edge/Standars) and relying on Pega HFixes to force Quirks, etc is even more "unreliable". Each method of emulation has its limitations.
Have you read through this related document? https://pdn.pega.com/documents/support-for-internet-explorer-11
I am also concerned with your request to bundle all JS HFixes for 6.2 SP2.
I would not attempt to do this. This will literally pull in hundreds of dependencies.
Is compatibility view or Enterprise mode (Enterprise Mode FAQs: Pega Expert Blog) an option for you as a mitigation until you can make the jump to Pega 7?
These will be much safer alternatives for you than attempting to install every JS HFix.
BNY Mellon
US
Thanks. The response from Support, incidentally, was to go to this link: https://pdn.pega.com/user-interface/troubleshooting-ie10-and-ie11-ui-problems-fixed-by-prpc-5x-and-prpc-6x-hotfixes-for-ie5-quirks-mode
Which, lists a number of hotfixes for the portals, but omits (among others, probably), HFix-21442 - https://community.pega.com/support/support-articles/attachment-control-does-not-work-ie11
Getting me to my original question, about getting a total list.
As per the literal hundreds of dependencies... yes, that's a headache, we'll have to deal with that then.
I just want to be able to explain to the business what specific problems there are.
Haven't tested Enterprise mode yet -- I was unaware of your document till you mentioned it -- I'll wager that the tags for my question and your document don't overlap.
Yes, we'd started the project to upgrade to v7, but that's on hold.
Accepted Solution
BNY Mellon
US
We reviewed all of the support articles related to IE11 issues that couldn't be solved by switching to compatibility mode, and produced this document: PRPC 6.x in IE11: Known Issues & Hotfixes
BNY Mellon
US
Upon further review, the PDN search is pretty good in this regard...
The main drawback is that some of the articles are poorly categorized.
e.g., https://community.pega.com/support/support-articles/unable-modify-step-activity-rule-ie11 - should have been coded as Developer Studio, not User Interface.
Pegasystems Inc.
US
Jon,
As you noted, PDN Search filters work well.
Regarding your second example, SA-13058, https://community.pega.com/support/support-articles/unable-modify-step-activity-rule-ie11, because this is a Support Article, the Topic category derives from the product development backlog that was specified for the parent Support Request (SR), in this case, User Interface. It cannot be changed. If this were a PDN Article, the Topic category could be edited. Who knows? Future refinements to the SA publication process might allow for changes to taxonomy and metadata.
-Mary
BNY Mellon
US
Thanks, Mary. Looking forward to future refinements to the SA publication process that allow for changes to taxonomy and metadata. :-)
As I brought up last March -- while it's intellectually rewarding to have different support articles on the same topic, it is time-consuming for the reader to go through, and some work should be done to synthesize them.