SR-A8445 · Issue 220085
Ensured display of empty user worklist section in hybrid client
Resolved in Pega Version 7.2
The user worklist section was not being displayed in the hybrid client if the login had no assignments (the WL(D_pyUserWorkList pxresultcount is zero) and the crewleaderworklist harness had a repeating dynamic layout. This has been corrected.
SR-A8217 · Issue 223611
Added server retry for push notifications in Sales Automation 7.14 / SFADevelopment for Android
Resolved in Pega Version 7.2
Push Notifications were not working on Sales Automation 7.14 / SFADevelopment for Android. This was traced to an error returned by the GCM server during registration, and the code has been modified to re-try the registration process if a failure is encountered.
SR-A12537 · Issue 224733
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.
SR-A9893 · Issue 220141
Checkbox values retained in Hybrid client on iOS
Resolved in Pega Version 7.2
Checkbox property values were not retained in Hybrid client on iOS inside a repeating dynamic layout, displaying the checkboxes as unchecked even when the property associated with the checkbox had value = true. This was not an issue when running the application on a desktop or in a regular mobile browser. This was traced to the ID attribute value of all the checkboxes being rendered as the same in this circumstance, and the system has been updated to generate unique ID attributes if bOptimized is true in the pzGenerateCheckbox RUF.
SR-A12638 · Issue 223936
Check added to handle mismatched property names given in referred page
Resolved in Pega Version 7.2
If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.
SR-A7008 · Issue 216642
Number separators localized for Excel export handling
Resolved in Pega Version 7.2
While using the Export to Excel button in reports, some of the figures in numbers columns displayed warning messages indicating they were formatted as text. This was a localization issue where numbers containing unusual separators were interpreted as strings, and has been resolved with a code change that allows Excel to decide the right format based on locale.
SR-A5758 · Issue 218426
Corrected automatic decimal rounding in summary report
Resolved in Pega Version 7.2
In the summary view report grand total, decimal values having 4 digits after the decimal point were being rounded to two places and displaying two zeroes in the 3rd and 4th decimal places. Ex: 1.1234 + 2.2345 returned 3.3500 instead of 3.3579. This was traced to the format "#.##" being applied to every value in the summary, and has been corrected.
SR-A7716 · Issue 219147
Proper value separations in filtered report definitions
Resolved in Pega Version 7.2
In a report definition in edit mode, trying to set filtering on several value was causing values to be appended without proper separators. As a result, no results were found when trying to apply a filter. This was due to a conflict in visibility conditions for the DataType identifier , and has been fixed.
SR-A10501 · Issue 223738
Corrected date format for chart using custom DateTime filter
Resolved in Pega Version 7.2
The date format of legends for a chart was not being formatted properly if a Filter Criteria range was used on the Datetime property. This has been corrected.
SR-A10369 · Issue 221614
Listview list query accepts non-date criteria
Resolved in Pega Version 7.2
The Listview list query was not being refreshed if the criteria values were taken from Time Period. This was due to the pyConditionValue1purpose not populating properly when given a non-Date data type setting, and had been corrected.