SR-D48887 · Issue 512946
Read-only text inputs remain read-only after browser refresh
Resolved in Pega Version 8.4
Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case; to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed.
SR-D49182 · Issue 513737
Check added for special characters in parameter for table source
Resolved in Pega Version 8.4
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 519366
Tab layout group handling improved
Resolved in Pega Version 8.4
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 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.