SR-A6387 · Issue 216159
Resolved errors while saving in summary view
Resolved in Pega Version 7.2
While saving an existing summary view, the error message "Output type: ** Your Field Definition does not match with Chart Definition. Verify it" was generated if only the third column was selected at the time of the save. In addition, selecting any checkbox other than the first in the chart's data tab during save of the summary throws an error. These issues have been fixed.
SR-A7649 · Issue 219010
Fixed RD "Report on Descendant" access to application page
Resolved in Pega Version 7.2
A report definition using the "Report on Descendant" option worked when executed from a user session but did not work when executed by a File Listener Process. This was due to the report not being able to access the application page in the batch requestor context, and has been corrected.
SR-A12707 · Issue 229383
Subreport join/filter updated
Resolved in Pega Version 7.2
An invalid subreport join/filter condition error was thrown if a filter with an unoptimized property from a sub report on one side had an optimized or literal property on the other side, even if the prconfig setting "reporting/useStreamInJoinConditions" was set to true. This has been fixed.
SR-A9129 · Issue 220717
Report Definition error message localized
Resolved in Pega Version 7.2
Localization/customization has been added for the Report Definition error message : "Retrieving the report data exceeded the limit of * seconds. Please try making the report more specific by further limiting which rows to include".
SR-A12941 · Issue 224444
NCHAR column type added to RD supported column types
Resolved in Pega Version 7.2
After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java
SR-A12941 · Issue 230561
NCHAR column type added to RD supported column types
Resolved in Pega Version 7.2
After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java
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.