SR-D49468 · Issue 516324
Parent harness context passed for reference properties in Ajax containers
Resolved in Pega Version 8.4
Attempting to save values failed for any property which was mapped to a parent property that was also a reference property. This was traced to an issue with the harness-level templating status: for the lazy loaded sections of a harness, the harness's template status was being passed instead of the parent harness template status when using an Ajax container. To resolve this, logic has been added to pzpega_ui_doc_serverProxy js for the invokeHandler function to add parameters based on the parent harness context to the safeURL object before invoking the post request.
SR-D49527 · Issue 516297
XSS security added to CKEditor in Richtext Editor
Resolved in Pega Version 8.4
A scenario where HTML objects could be copied and pasted into CKEditor and the click action modified to perform different actions was traced to Pega event attributes present in the RTE content. This has been corrected by blacklisting Pega event attributes like data-click, etc.
SR-D50069 · Issue 514342
Image Attachment File Type error localized
Resolved in Pega Version 8.4
Localization has been added to the error message generated when an unsupported image is uploaded while in live-chat.
SR-D50116 · Issue 518002
XSS filtering added for MobileSnapStart URL
Resolved in Pega Version 8.4
XSS filtering has been added for windowTitle in the MobileSnapStart URL.
SR-D50372 · Issue 514614
Interaction Driver now supports more than 7 open items
Resolved in Pega Version 8.4
After creating 7 items in an interaction so they are open in the interaction driver, adding item number 8 caused the threads in the clipboard to not correspond with the number of items and the interaction driver was not extended with the new items. This was traced to the "parentKey" parameter not being present in the request: the "parentKey" parameter isn't mandatory but is usually used internally for the RECENTS functionality, and was missed only when maxdocs limit was reached because the recents feature was not validated in case of maxdocs. To resolve this, the "parentKey" will now be passed for all use-cases.
SR-D50621 · Issue 519299
Handling added for Pagelist with brackets in rendering RDL
Resolved in Pega Version 8.4
After configuring four nested embedded sections where the last section included a repeating dynamic layout, the RDL showed up in the included section as raw HTML markup in the UI at runtime. Analysis showed that when rendering the RDL on the last item of the Pagelist which contained PAGE_LIST_NAME<LAST>, the angular brackets were treated as HTML entities that caused the attribute page-context to break. This was a missed use case for First and Last pagelist items that caused an error in appending the page context to attribute, and has been resolved by encoding the HTML for the page context attribute before appending it to the DOM.
SR-D51330 · Issue 515247
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.4
When a field was implemented with a radio button control in the service case screen, starting two cases of the same or different case type (with the same property and control) resulted in the selected value not sticking in the first case when selections were made for the second case. This was traced to multiple radio buttons with the same name in the dom for different AJAX containers: as per radio buttons behavior, only one could be selected if they have the same name. To correct this issue, updates have been made to change the name on radio buttons which are inside the hidden AJAX container and toggle the changes when the buttons should be shown.
SR-D51555 · Issue 516496
Resolved system hang after changing input field value post note
Resolved in Pega Version 8.4
After upgrade, a session was hanging in a Non-Member Search Phone interaction after navigating back from "Add or edit attachments" window. The same code worked as expected in the Member Search Phone interaction. Investigation showed that changed values (transaction ID, pzFromFrame) were being sent to the client twice, once in the popup window after attaching the note and again to the parent window. When the changed values were consumed and used in next actions, a mismatch resulted in pzFromFrame. To resolve this, the system has been updated so the Client will not consume the pxThread.pxClientExchange value if pxThread.pxClientFrame is different from what the current tracker is using.
SR-D51601 · Issue 516705
Hover logic updated
Resolved in Pega Version 8.4
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.
SR-D51776 · Issue 531986
Check added to resolve Ajax Container instantiation error in log
Resolved in Pega Version 8.4
When using the Microsoft Internet Explorer or Edge browsers, manually launching a Service Intent and clicking the F5 refresh button properly refreshed the screen, but the PegaRULES log file contained the error "(DynamicContainerDataModel) Error occurred while instantiating tab for the thread index." This issue / exception was observed only when pzCustomDCTabHeader was configured (pyEnableCustomTabHeaders) and when there was a AjaxContainer configured in the document. Because the CustomTabHeader recreation (DynamicContainerDataModel.updateCustomTabHeader) should be skipped for AjaxContainer, as CustomTabHeader is applicable only to the top level DC document and not to the AjaxContainer document, a check has been added to resolve this issue.