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.
SR-A87291 · Issue 255631
JDBC password encryption check logic updated
Resolved in Pega Version 7.2.2
When using a Database instance with a JDBC connection URL, the specified password is encrypted. An issue was occurring where multiple saves of the instance caused the encrypted password to be encrypted again, causing the agent to lose access to the DB due to an authentication failure. The problem was traced to a logic flaw in the method used to check whether the password was already encrypted, and has been fixed.
SR-A94871 · Issue 263314
Handling added for summary report paging mode changes
Resolved in Pega Version 7.2.2
After switching a summary report previously configured to use the "Next Previous" paging mode to a list report using the "List" action in the "Actions" menu, changing to a new page caused an error to be shown and no records displayed. This has been corrected by adding a step to the activity pzPostReportSummarizeConfig to reset the paging of a report when converting from a summary report to a list report.
SR-A92781 · Issue 264233
Fixed date format in en_GB locale
Resolved in Pega Version 7.2.2
When using locale en_GB, the date format of the fields was displaying in the wrong date format. The pyCustDateTime parameter was set for custom datetime format, but this was not getting cleared after getting the formatted value and then being incorrectly used for the next DateTime control. This has been fixed by clearing the pyCustDateTime parameter in the pzGenerateFormat RUF after calling formatter RUF.
SR-A67932 · Issue 251208
Blank query field in Bulk Actions defaults to none instead of all
Resolved in Pega Version 7.2.2
Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. 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.
SR-A86228 · Issue 256027
Documentation corrected for connection properties with WAS 8.5.5.7 and MSSQL 2014
Resolved in Pega Version 7.2.2
The case specified in the install guide for including the "SelectMethod" and "SendStringParameterasUnicode" connection properties was incorrect, causing poor performance in the import process when using WAS 8.5.5.7 and MSSQL 2014. The documentation has been corrected.