SR-119239 · Issue 173898
Max limit error localized and variable added for unsaved work items
Resolved in Pega Version 7.1.7
In order to allow a local value for the number of unsaved work items, a new Field value has been created : MAXIMUMTABSALERT. In addition, the error message text "You have reached the maximum limit for pending changes. Please commit/cancel one or more changes to continue" is now available for localization.
SR-119537 · Issue 174774
Improved speed for deleting repeat grid rows with Dynamic Select
Resolved in Pega Version 7.1.7
When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected.
SR-112935 · Issue 166182
Repeating grids enhanced to allow the '&' character as text
Resolved in Pega Version 7.1.7
When values in a repeating grid contained the character "&", the ReloadSection activity failed with an illegal argument tracer and no values were passed to a second Repeating Grid Page List. This was traced to '&' being used by the system to perform a split of value string. In order to allow use of the '&' character in the list values field, it will now be encoded so it is passed without evaluation.
SR-115387 · Issue 164437
Flow Action support tuned for MenuBar keyboard navigation
Resolved in Pega Version 7.1.7
Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.
INC-120299 · Issue 578183
Added null check to ActivityStatusExceptionHandler
Resolved in Pega Version 8.5.2
Invalid Parameter Exceptions were being logged in the production environment related to an 'CPMInteractionPortalWorkArea' execution error on page 'pyTmpDisplayHarness' indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)". This has been resolved by adding a null check before reading the DC data model in the activity ActivityStatusExceptionHandler.
INC-128279 · Issue 591378
Layout Group tab alignment correctly shown in Microsoft Internet Explorer
Resolved in Pega Version 8.5.2
Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.
INC-132176 · Issue 588809
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.5.2
The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.
INC-132219 · Issue 580266
Values with accent characters are sorted properly
Resolved in Pega Version 8.5.2
Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.
INC-132569 · Issue 595174
Resolved case detail overwrite
Resolved in Pega Version 8.5.2
In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.
INC-133576 · Issue 590325
Expandable Grid behavior corrected
Resolved in Pega Version 8.5.2
Expanding any row in master details was collapsing a previously expanded row. This has been corrected.