INC-175990 · Issue 652089
Browser check added to ensure on-click event trigger
Resolved in Pega Version 8.7
Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.
INC-153805 · Issue 627969
Mobile app language remains consistent after data sync
Resolved in Pega Version 8.5.3
When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.
INC-157699 · Issue 624596
Customer 360 Tabs load in Firefox browser
Resolved in Pega Version 8.5.3
After upgrade from v8.1 to v8.4, the layout group's tab content was not loading as expected in the customer 360 view when using the Firefox browser. Investigation showed this was due to the �role� attribute being removed from the header div by the on-hover showSmart tip action configured on the dynamic layout tabs. This has been resolved by updating the system to use data-role along with the role tab.
INC-139086 · Issue 597146
"Show next error" correctly displayed on user portal
Resolved in Pega Version 8.5.3
In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.
INC-144778 · Issue 619615
Performance improvements for Ajax tab switching
Resolved in Pega Version 8.5.3
When using a 360-view of members in a portal implemented with an Ajax container that showed information in multiple tabs, tab switching was taking a lot of time even though the data was already in the memory. Updates have been made to improve performance.
INC-157041 · Issue 626312
Performance improvements for email listener processing
Resolved in Pega Version 8.5.3
Email processing was taking an excessive amount of time when a very large number of email listeners were running. Performance has been improved by updating the implementation of pzGetChannelByName to use obj-browse instead instead of looping through channels.
SR-D43627 · Issue 509800
Keyboard tab support added added for Focus on Date control
Resolved in Pega Version 8.2.5
It was not possible to use the Tab key to move to a section with date control to launch it, and hitting enter when on a calendar did not open it. To resolve these, tabindex has been added for date/time focus and the calendar will open on enter.
INC-215912 · Issue 711380
Corrected links being replaced by KM rich text editor
Resolved in Pega Version 8.6.4
When brackets/parentheses were encountered in URL links in the rich text editor used in Knowledge Management, those links were removed and replaced with a # (pound symbol). This was due to a legacy cross-site scripting security mitigation, and h as been resolved.
SR-D51601 · Issue 516704
Hover logic updated
Resolved in Pega Version 8.2.5
When using a dropdown in a grid layout configured with a smartInfo to be displayed on Hover, the smart tip was sometimes not displayed when the hover moved from the top to point to the dropdown. If the hover was done quickly, it was displayed. Previously, the hover was calculated only by cursor x, y positions and elements boundaries: to resolve this issue, the logic has been updated to also consider cases where the element is still hovered without meeting these conditions.
INC-155752 · Issue 622772
Hidden Question pages and answers will be saved to database
Resolved in Pega Version 8.5.3
After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.