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-163628 · Issue 660555
Corrected view generation logic for nested subsections
Resolved in Pega Version 8.5.6
Performing a save-as of the pyCaseMainInner work- section in the UIKit resulted in an infinite loop in the view generation logic. This was traced to the system recursively generating views from subsections, and has been resolved by updating the logic so a view is only generated for valid py prefixed sections on save of a section.
INC-164620 · Issue 640658
jQuery variable handling updated for mashup
Resolved in Pega Version 8.5.6
After upgrade, embedded mashup was not working. The browser console log showed the error "Uncaught TypeError: $ is not a function at pega.web.manager._initGadgets (PegaReg?pyActivity=pzIncludeMashupScripts:69)". The $ function belongs to the jQuery library, and investigation traced this to a difference in variable handling. This has been corrected by updating the referring jQuery to use the variable 'jQuery' instead of '$'.
INC-164775 · Issue 681238
Web page generation security updated
Resolved in Pega Version 8.5.6
Cross-site scripting protections have been enhanced around web page generation.
INC-165992 · Issue 657690
Table Filter save uses correct harness
Resolved in Pega Version 8.5.6
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
INC-167704 · Issue 671628
Email timing updated to ensure content captured
Resolved in Pega Version 8.5.6
Outbound email replies constructed using a pyReply section were intermittently blank if the 'Send' button was clicked immediately after adding text. This was traced to the blur not happening immediately on click of the submit button, and has been resolved by introducing window.blurDelay to ensure the data is captured. The delay time is configurable, and by default is set to 200ms.
INC-167871 · Issue 666295
Desktop browser java render error corrected
Resolved in Pega Version 8.5.6
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.