SR-D33421 · Issue 501115
DX API - Field values for placeholder text localized
Resolved in Pega Version 8.4
While using DX API, it was observed that if a field value was used for displaying placeholder text, the field value rule was not resolved. Instead, the name of the field value rule was passed in JSON as text and not the actual value. This has been corrected by adding pyNoSelectionText to specifically localize the placeholder text for dropdown.
SR-D33445 · Issue 505995
Handling added for context switching with Ajax container in Timeline
Resolved in Pega Version 8.4
When using Interaction Portal -> Overview -> Timeline and opening a case that uses an AjaxContainer, clicking on an icon in the Timeline without having first clicked anywhere in the document was generating an exception. If there was a click in the document body first, clicking on the icon worked as expected. This has been resolved by adding a parameter to registerContextSwitching method to handle customeDOMEvents along with a condition to check if pega.u.d.isAjaxContinerExists is a function, which will register the Context if 'true'.
SR-D33966 · Issue 504608
Corrected accessibility error after resize
Resolved in Pega Version 8.4
From within a Case and on a screen displaying the Information and Audit tabs in a Layout group, it was possible to use a series of sequences that included resizing the browser and opening Audit to cause the information tab to no longer be accessible. This has been resolved by setting the transform value to 0 after completing the resize.
SR-D34824 · Issue 508211
Support added for non-decimal currency notation
Resolved in Pega Version 8.4
Previously in the pxCurrency control, the options allowed either specifying Decimal places (2 by default) or using the locale to decide decimal places when "Use currency standard" was selected (creating the default for 2 for en_US, 0 for jp_JP and 3 for ar_JO.) However, this did not account for currencies like JPY, TWD, and HUF, which do not use decimal precision. In order to support these currencies, handling has been added to formatNumaber js and pxFormatNumber for locales which do not have decimal precision in their currency.
SR-D35266 · Issue 509482
Check added to postOpenAssignment to support Ajax Container use
Resolved in Pega Version 8.4
After configuring an 'OpenAssignment' action on a begin button and giving the target as 'Dynamic Container', it worked as expected to open the assignment in a new tab on the Platform, but did not work from the Customer Service interaction portal. This was traced to the Customer Service portal using MicroDC to display the cases in the work area, which was not within the scope of the Ajax Container. Additional checks have now been added to the postOpenAssignment function to support this use.
SR-D35268 · Issue 506686
Max results limit increased for open-rule-advanced query
Resolved in Pega Version 8.4
An issue with the results list of a class instance query being clipped in the autocomplete drop down was traced to an old limit that was put on to restrict the number of results shown in open-rule-advanced. This limit has now been increased in the open-rule-advanced control.
SR-D35618 · Issue 504689
pzGetURLHashes returns proper content-type
Resolved in Pega Version 8.4
When using an environment set with X-Content-Type-Options:nosniff, the response from pzGetURLHashes was returned with text/html response type and the mashup would not load due to browser exception "MIME Type ('text/html')is not excutable, and strict MIME type checking is enabled." In order to support CORB mitigation in the browser, the javascript content type will be set in the response header for pzGetURLHashes call.
SR-D35842 · Issue 505709
Checks added for empty/missing properties during rule restoration
Resolved in Pega Version 8.4
After making a change to the harness and checking it in, restoring an old version of the harness from history resulted in the old version of the rule displaying a missing or corrupted button area. The was caused by the rules revision history not keeping empty / default properties in the DB, so when the rule is restored those properties were not populated in the resulting XML. To resolve this, empty checks and default values have been added for any non-existent properties in pzpega_ud_gridlayout_model JS and pzpega_ud_gridlayout_structure JS.
SR-D35955 · Issue 525239
Special character removed from filename of RTE uploaded into PDF
Resolved in Pega Version 8.4
An Image uploaded from RTE was not displayed in PDF if the image name had special characters. This has been resolved by setting the system to remove '%' from file names uploaded into RTE.
SR-D35956 · Issue 521643
Handling enhanced for invalid date values in date/time
Resolved in Pega Version 8.4
Refreshing a section or entering an invalid date was causing the date/time to be reset to the current date. This has been resolved by modifying the logic and adding conditional checks in 'pzpega_ui_formatDateTime.js'.