SR-D24682 · Issue 501080
Added check for undefined targetTD in repeating tab layout
Resolved in Pega Version 8.4
Given a repeating tab layout and a validation on the flow action which used edit validate, clicking on the next button set an error on the page. Putting in the correct data and clicking the next/submit button a second time resulted in a console error indicating the targetTD was undefined for the markSectionTabErrors function in pzpega_ui_doc_tabsupport. This has been resolved by adding a check for the undefined targetTD.
SR-D32507 · Issue 507846
GenerateCellContent updated to properly set active context
Resolved in Pega Version 8.4
An issue with adding and deleting items in existing rows in a repeating grid layout was traced to the Base_ref being wrongly stamped on a section included cell. This was caused by a grid in previous cell causing the active context to be updated to the cell's grid source context, and has been resolved by updating the generatecellcontent Rule-Utility-Function to set the active context properly in generation.
INC-139018 · Issue 587716
Rules updated to handle Outlook change that displayed multiple/duplicate email responses
Resolved in Pega Version 8.6
In Pega Email Triage case, all the replies were displayed along with the original email body, meaning for each and every reply, Pega showed the original email body and duplicated the data. This was traced to an update made by Microsoft in the Selector function of Outlook Windows, and has been resolved by updating the rules 'PyExtractLatestReplyFromHTML' and 'pyRichTextEmailHistorySelector' to work with this change.
INC-128639 · Issue 608654
Updated dynamic container event listener for JAWS
Resolved in Pega Version 8.6
Upon tabbing in, JAWS 2020 was reading the entire contents of the center panel including announcing "Center Panel", "Tab Panel", "Frame" and all UI elements in the center panel without stopping. This has been resolved by updating the 'pega.util.Event.addListener' function in PZPEGA_UI_DYNAMICCONTAINER.
INC-150222 · Issue 612575
Custom client-side future date validation works on mobile
Resolved in Pega Version 8.6
After developing a custom client side validation based on documented examples that used jquery to locate two input fields (date pickers) and added an on-change function, the validation worked as expected on the desktop but gave a validation error for any future date when using the mobile app or browser. This was an issue with the name attribute handling on mobile, and has been resolved.
SR-D22885 · Issue 494165
Added check for empty class properties to report scheduler
Resolved in Pega Version 8.1.6
A report that was looking for events in the most recent X hours by using the "Difference In Hours" filter function ran in the foreground but failed with an exception when running under the scheduler. The same report ran as expected in background without the filter. This was traced to a classname property not being set on the clipboard, and has been resolved by adding a check for empty classes on the clipboard when scheduling a report.
SR-C93572 · Issue 440080
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.1.6
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.
SR-C97873 · Issue 437282
Added check to maintain key value when using collapseAllMenu in child navigation menu
Resolved in Pega Version 8.1.5
After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.
SR-D392 · Issue 438873
Behavior reset for using getLocalizedValue with an input string containing parentheses
Resolved in Pega Version 8.1.5
After upgrade, the getLocalizedValue function was not returning any value if the input string contained parentheses. This was a difference in behavior caused by a missed use case when correcting another issue, and has been resolved by resetting the system to the previous behavior of getLocalizedValue returning a localized string in cases where a Field value/Rule message is present, or otherwise returning the exact input string.
SR-C93572 · Issue 440079
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.2.2
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.