SR-D49182 · Issue 513736
Check added for special characters in parameter for table source
Resolved in Pega Version 8.3.2
A table with a literal string that included the @ symbol for a parameter to its data page source was unable to load the section if it had the optimize code checkbox enabled. This has been resolved with the addition of a check for special characters.
SR-D49305 · Issue 519363
Tab layout group handling improved
Resolved in Pega Version 8.3.2
A difference in scrolling speeds between left and right arrows and an issue with the cursor correctly being redirected to mandatory fields were traced to errors in the tab layout group handling. The right scrolling issue was due to the calculation for right tab movement being incorrect in certain resolutions with relatively positioned elements, and has been corrected. The cursor redirect was caused by an error in the layoutgroup focus when used inside a screen flow where the first focus goes to the screenflow navigation on load, and has been resolved by adding a try catch for an invalid selector in case of a div error.
SR-D49468 · Issue 516323
Parent harness context passed for reference properties in Ajax containers
Resolved in Pega Version 8.3.2
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 516296
Cross-site scripting security added to CKEditor in Richtext Editor
Resolved in Pega Version 8.3.2
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-D50208 · Issue 517231
Corrected layout of sort and filter icons for grid tables
Resolved in Pega Version 8.3.2
The sort and filter icons in a table grid were almost overlapping, and in some cases the sort icon was so small that it was almost not visible unless the width of the specific text was enlarged to see it. This was traced to a CSS snippet present in one of the override files that forced the width of the name column grid header to 100%, and has been corrected by ensuring the sort column is left aligned next to the column header.
SR-D50621 · Issue 519298
Handling added for Pagelist with brackets in rendering RDL
Resolved in Pega Version 8.3.2
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 515245
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.3.2
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 516493
Resolved system hang after changing input field value post note
Resolved in Pega Version 8.3.2
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 516702
Hover logic updated
Resolved in Pega Version 8.3.2
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 531983
Check added to resolve Ajax Container instantiation error in log
Resolved in Pega Version 8.3.2
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.