INC-148392 · Issue 610670
File type handling added for cloud downloads on mobile app
Resolved in Pega Version 8.5.3
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the mobile app, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so the file type was not able to be identified. This was a missed use-case for returnFileForDownload(), and has been resolved.
INC-154778 · Issue 620906
Bulk actions filtering works in Spanish locale
Resolved in Pega Version 8.5.3
Filtering by only case type did not return any results when using the Bulk Transfer functionality with the Spanish locale. Investigation showed that the filter value case type had a field value set, but the localized value was not being checked in the pzPostFilterOperation in step 1 'when' condition. This has been resolved.
INC-152084 · Issue 620952
Handling added for cross-origin DOM exceptions
Resolved in Pega Version 8.5.3
When an openURLWindow action was used to open any other domain, DOM exceptions were generated related to cross-origin iFrames communication and the UI became unresponsive. This has been resolved.
INC-145939 · Issue 606896
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.5.3
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
INC-154824 · Issue 620922
Check added for hidden field during validation
Resolved in Pega Version 8.5.3
When using custom validation for a future date, after certain steps the message "value cannot be blank" was displayed even though there was a value in the date control. This was traced to the validation also being performed on a hidden field, and has been resolved by adding a condition in pega_validators to check for hidden fields when running the validation.
INC-150222 · Issue 612577
Custom client-side future date validation works on mobile
Resolved in Pega Version 8.5.3
After developing a custom client side validation based on documented examples that used jquery to locate two input fields (date pickers) and added an on-change function, the validation worked as expected on the desktop but gave a validation error for any future date when using the mobile app or browser. This was an issue with the name attribute handling on mobile, and has been resolved.
INC-155319 · Issue 616476
Action Set Dialog features displayed correctly in App Studio Design with Firefox
Resolved in Pega Version 8.5.3
When using the App Studio Design mode to edit controls and elements within section at runtime (Open Case Type in App Studio -> Save and run) and selecting a control in Design mode that has any action set configured on it, upon opening the action set clicking the �Add an action� link element the dialog box which appeared cut off. This was traced to an issue where Overlay was not flipped in Firefox v83.0 when the client.right value exceeded the main container width, and has been resolved by adding a condition for Firefox to use the correct client.right value as per the main container.
SR-D45360 · Issue 510101
Support added for non-decimal currency notation
Resolved in Pega Version 8.1.7
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-D43179 · Issue 509888
Corrected viewing of sorted drill-down spreadsheet-style summary reports
Resolved in Pega Version 8.1.7
When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to.
SR-D39236 · Issue 508452
Corrected viewing of sorted drill-down spreadsheet-style summary reports
Resolved in Pega Version 8.1.7
When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to.