INC-156051 · Issue 622504
Double quotes escaped when parsing placeholder string
Resolved in Pega Version 8.6
When trying to open the ‘View Properties’ modal for a new utility shape in a flow, the system was hanging on the busy indicator. The issue occurred when the pzEnterDescriptionOrChooseExistingSpec field value had double quotes, and was due to double quotes not being escaped when trying to parse Rich Text Editor placeholder string. This has been resolved.
INC-156094 · Issue 621066
Access control updated for non-auto-generated finishAssignment
Resolved in Pega Version 8.6
After upgrade, a flow containing a flow action that called an out of the box HTML rule was triggering a SECU0019 alert and blocking functionality. This was a missed use case for BAC where all non-auto generated rule actions should be registered, and has been resolved by registering finishAssignment.
INC-156625 · Issue 620656
Cross site scripting protection update
Resolved in Pega Version 8.6
Cross site scripting protections have been updated for labels.
INC-156802 · Issue 620675
Handling added for special characters for track changes
Resolved in Pega Version 8.6
After entering inverted commas ["] inside a text box configured with post value and 'refresh this section' actions, focusing out of it caused the UI to freeze. A JSON parse issue was seen in the browser console, which was traced to the domelement API not having handling for special characters in the HTML code. This has been resolved.
INC-156826 · Issue 625438
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.6
When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.
INC-156912 · Issue 627487
Updated accessibility for Rich Text Editor navigation in a modal dialog
Resolved in Pega Version 8.6
When navigating through a Rich Text Editor while in a modal dialog, it was expected that once focus was brought to the Rich Text Editor Toolbar (Alt+F10), pressing Escape on the keyboard would bring the focus back into the Rich Text Editor text area and the cursor would appear. However, when this Rich Text Editor was within a modal dialog, pressing Escape closed the modal dialog entirely. This has been resolved by updating the code to stop the Escape key event propagation from the Rich Text Editor toolbar when in a modal dialog.
INC-156992 · Issue 628623
Corrected custom portal JUMP condition
Resolved in Pega Version 8.6
After upgrading Pega from 8.3 to 8.4, a custom portal was not correctly rendering the stream although the activity was getting executed and the clipboard had all the necessary data. This was traced to a syntax error in work done earlier that placed the JUMP condition (.pyDesktopType=="Custom") in ShowDesktop at the pzPopulateRequestor call step, and has been corrected.
INC-157041 · Issue 626310
Performance improvements for email listener processing
Resolved in Pega Version 8.6
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.
INC-157119 · Issue 621746
Rule-Message instances added for guardrail warnings
Resolved in Pega Version 8.6
Log errors were seen when saving a rule in Dev Studio that generated a guardrail warning from the pzValidateFieldValueReference function. This was related to work done when the function "addwarning" was deprecated in favor of pxAddGuardrailMessage, and has been resolved by adding Rule-Message instances for pxFieldValueMaxLength, pxFieldValueConsecutiveSpaces, and pxFieldValueQuotesNotAllowed.
INC-157353 · Issue 624012
Handling added for autoclose of assignment in tabbed MDC
Resolved in Pega Version 8.6
After configuring an Ajax container in a section using tabs and max doc defined as 8 with 'doClose' set after processing has been completed, finishing the assignment caused the work item tab to stop working. Checking the console showed a script error was being thrown. Investigation showed that when the doClose action was triggered and tried to find the activeTabs in MDC, the target element being fired was null. This has been resolved by adding a condition for the doClose to handle the combination of autoclose and tabbed MDC that will close the current Ajax container div before proceeding.