SR-B50863 · Issue 314694
Corrected error for second open of WO history
Resolved in Pega Version 7.3.1
When using the out-of-the-box View History action on the toolbar to show history, the history screen displayed as expected and could be closed with the 'close' button. However, reopening the View History showed an error screen. This has been fixed by modifying the "isWindowOnDesignerDesktop" method to return the correct value for popup cases.
INC-162426 · Issue 638771
Regex handling updated for Rich Text Editor spellcheck
Resolved in Pega Version 8.7
When using the Rich Text Editor and performing a spell check, the spell checker was adding additional CSS to the property. This was traced to the presence of a unicode newline character causing the existing regex to fail to strip the style tags. To resolve this, regex handling for the unicode newline character in the style tag has been added.
SR-B51546 · Issue 310076
PromptSelect control action set repaired for class key config
Resolved in Pega Version 7.3.1
When prompt selects were configured to use a class key validation for the source, action set events did not fire. (e.g. onchange, refresh section & data transform). This was traced to missing ClientValidation inclusion for a ClassKeys configuration in PromptSelect Control, and has been fixed to generate the necessary pega_attributes for action execution.
SR-B64265 · Issue 314375
Tab key navigation focus fixed for Silverlight
Resolved in Pega Version 7.3.1
When using a word merge functionality in the modal dialog with Tab key navigation, after the "Loaded Silverlight" text highlight, the three subsequent tabs did not focus anywhere on the screen. This improper tab movement was caused by missed handling in the pyPegaSilverlight file that caused tabindex to not be properly set for the hidden controls, and has been fixed.
INC-137510 · Issue 591295
CKEditor Source edit with formatting resumes process automatically
Resolved in Pega Version 8.3.5
Buttons on the harness were freezing after applying format using CKEditor when source mode was turned on in rich text editor. Investigation showed that on clicking the source button, after applying styles, the events were being paused and were not resumed automatically. This has been resolved by adding changes to resume the event queue.
INC-182724 · Issue 677844
Added empty space handling for tab labels
Resolved in Pega Version 8.7
After upgrade from Pega 6 to Pega 8, tab names were not displaying when rules were opened in Designer Studio. This was traced to empty space in the label which caused the Tab name to show as empty, and has been resolved by updating pzpega_ui_dynamiccontainer to use the trim method to check whether the label is empty or not .
INC-183163 · Issue 676252
Optimized table search updated
Resolved in Pega Version 8.7
Search functionality that can be enabled from tables after selecting the "Optimize" checkbox was not working correctly. This was traced to a potential issue getting the search parameter passed into the activity the section uses, and has been resolved by updating the system to get the element from pega.ctx.dom when pyFlowActionHTML div does not exist.
SR-B66561 · Issue 316940
Empty grid check added to Add Item (Before) action
Resolved in Pega Version 7.3.1
Using "Add Item -> Before" to add the first row in an empty grid configured with page list as a source showed the following issues: 1. Focus was gone and not set on the first row. 2. The grid header disappeared, and the first row added appeared. 3. It was not possible to delete the first row. Even when manually clicking to set focus on the row, the system still asked for selection of the row to delete. This was traced to the "add before" function using updateHandlesAfterInsert even though the grid was empty. The postUpdate API in ui_grid.jshas been updated with a check to resolve this.
INC-170258 · Issue 645043
Removed unneeded query parameter in UI
Resolved in Pega Version 8.7
When using an Ajax container without a dynamic container, a refresh harness / section event call related to pyBlockUnregisteredRequests was not being properly registered, resulting in a 403 error and the message "Unregistered request encountered ..". This was traced to a "pyDataTransform=" query parameter that was present in the PZPEGA_UI_MICRODC file, and the parameter has been removed to resolve this issue.
SR-B49082 · Issue 307656
Mashup gadget call modified for Microsoft Internet Explorer compatibility
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, triggering a mashup API logoff with the gadget and then accessing the gadget again generated a NullPointerException. This issue only occurred with Microsoft Internet Explorer due to it sending the sendP3P parameter with a value of "true", triggering a doUIAction process that incorrectly accessed "pyHTTPResponseHeaders" and returned it as null. To fix this, the logic in the doUIAction activity has been modified to compensate.