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.
SR-D52144 · Issue 515670
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.3.2
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.
SR-D52630 · Issue 519228
Ad hoc task time validation done on correct thread
Resolved in Pega Version 8.3.2
The validation on a time value was not working correctly when two cases of the same type were open at the same time. For every ad hoc task, there is some validation on the time property. After submitting a value in a second ad hoc task, the validation was triggered but used the property from the first ad hoc task and showed the error in the second ad hoc task tab. This was traced to the datepicker taking the reference from the previous MDC when it needs to take it from the active MDC. To correct this, the control_datepicker has been upadted to use pega.ctx.getElemById.
SR-D52665 · Issue 518263
Corrected error when using CharCounter in non-template mode
Resolved in Pega Version 8.3.2
An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.
SR-D52695 · Issue 515971
Pagination context switch handling updated for mouse scroll
Resolved in Pega Version 8.3.2
When using various tables in the client application that have the Pagination mode set to 'Progressive' and that contain hyperlinked elements on which an 'Open Work by Handle' action has been defined, clicking an element that was loaded progressively intermittently generated an alert with the message 'Empty work item handle'. Investigation showed that dragging the scroll bar to access the latest cases worked, but using the mouse to scroll and select replicated the issue immediately. This was caused by context not being properly switched to the current harness while scrolling due to missing context switch handlers. To resolve this, code changes have been made to set the correct context before sending the request.
SR-D52785 · Issue 518649
Cross-site scripting protection added to layout runtime java and whitelist validation available for host/XFHost
Resolved in Pega Version 8.3.2
In order to protect against Cross-site scripting issues, filtering has been added to the RepeatDynamicIndex parameter value in layout runtime java. In addition, a validation for X-Forward-Host value has been added which will be read from a local configuration. This is in the form of a white list regex filter for the host/XFHost header to ensure the URL's actions cannot be redirected.