SR-D36335 · Issue 504334
Post Value action properly displayed in upper case after validation
Resolved in Pega Version 8.4
After upgrade, if a property with Edit Input toUppercase was created and placed it on a section where the text input has Post Value on Change, validating the uppercased property on the clipboard resulted in the non-uppercase value displaying on the screen. This was traced to the target element with the response value not being updated with the server response for the post value action. Only the attribute value was updated, which is not shown to the user. In order to properly display the value, logic has been added to update the target element value with the response value.
SR-D36970 · Issue 504986
Calendar icon updated to properly display the set number of years
Resolved in Pega Version 8.4
By default, the Calendar icon showed a date range of 10 years when -/+100 was expected. This issue was traced to the existing DSS setting (pyNumberofYears under Pega-UIEngine), which enables overriding the date year range, not being honored when the pyNoOfYears property was set to -1. To honor the pyNumberofYears setting, pyNoOfYears should be 21. This has been corrected so the value will be set properly. To see custom calendar range, attached snippet should be added to UserWorkForm. To see custom calendar range, the below snippet should be added to UserWorkForm: <script> pega.u.d.overrideCalendarDefaultRange = { past: 20, future: 20 } </script>
SR-D37290 · Issue 506285
Null check added to ensure value "yyyyMMdd" displays correctly in DateTime Input
Resolved in Pega Version 8.4
An issue where the input value "yyyyMMdd" was not displayed correctly in a DateTime input field was traced to moment.calendar returning invalid formatting when executed on a null property. To resolve this, a check has been added to assess whether the datetimeframe has any properties or not.
SR-D37326 · Issue 504936
Resolved clipboard formatting issue in Reply Thread and Send Correspondence
Resolved in Pega Version 8.4
Issues were seen with the table formatting of client data after mail was sent. This has been resolved by ensuring all borders are retained in RTE when used in both "Send Correspondence Task" and "Reply Thread".
SR-D37348 · Issue 514840
Added handling for placeholder in Multi-Select List Control
Resolved in Pega Version 8.4
After adding a placeholder in Multi-Select dropdown properties to hold the default value as 'please specify' by way of a refresh section on the action tab of multi-select property, the multi-select drop was showing the 'please specify' placeholder after refreshing the section even though there was value in it. This has been resolved by adding handling to make the placeholder empty when there are values.
SR-D38581 · Issue 504776
Removed unnecessary XSS filtering on paragraph rule
Resolved in Pega Version 8.4
When a link was set in a paragraph rule, the target option was removed in the returned layout structure. This was traced to unnecessary XSS filtering which has now been removed.
SR-D38729 · Issue 507032
Included section with defer load loads in modal flow
Resolved in Pega Version 8.4
An included section in a dynamic layout with 'defer load content' enabled was not loading in a modal window when it included a table sourced from Data Page which in turn called a Connect Soap to load the data. When the modal window was launched, it indicated it was loading text but did not actually load any data. When 'defer load' was unchecked, the data loaded as expected. In addition, the tab groups in the modal screen flow were not displayed. The same tab group did show when opened through a separate flow. This was traced to the data-harness-id not getting added to the flow in the modal case, and has been resolved by adding data-harness-id to the preRenderer in modalOverlay to handle modal flows.
SR-D38946 · Issue 507907
Dragresize plugin removed from RTE for better Microsoft browser compatibility
Resolved in Pega Version 8.4
When a messge was sent through Pega chat while using the Edge web browser, the text field where the message was entered before the send button was pressed did not get cleared. This was traced to the Edge browser throwing a Permission Denied error while attempting to access a detached DOM element. To resolve this, the 'dragresize' plugin has been removed from RTE as its implementation is not compatible with Microsoft Internet Explorer 11 and Edge.
SR-D39369 · Issue 513097
Handling added for images in true/false checkboxes causing security policy issues
Resolved in Pega Version 8.4
The out-of-the-box Pega security policy AllowPegaCollaborationServices, which is included functions such as Pega Customer Services for Healthcare and required by Pega Cloud Collaboration Services, was blocking Pega images from webwb. As an example, using a checkbox "*truefalse" configured with two images for true and false values when this Security Policy was set (which has Image-Source self set), a console error was generated. This was caused by the images URL being a base-64 string instead of a page URL. This meant that when the checkbox was configured with an image, the image was being converted to bytes as if for offline. To resolve this, separate handling has been added for online cases.
SR-D39455 · Issue 508606
Shortened URLs (bit.ly) supported with custom image size
Resolved in Pega Version 8.4
Marketing offers were very slow to load, often generating requestor lock exceptions due to the wait time. This was traced to one cell in one section that housed a company logo: the source to icon had a shortened "bit.ly" URL when the ImgaeIO API in Java expected the actual URL as its input. The API could not convert the shortened URL to the actual URL, resulting in the retries and connection failure. To resolve this, 'javax.imageio.ImageIO' invocation will happen only when the image size is auto. If custom height and width are used to display an image, Pega will not depend on the Java library and the system will be able to resolve the shortened URL.