SR-A9070 · Issue 221177
Updated caches for Data-Admin-DB class groups
Resolved in Pega Version 7.2
Data-Admin-DB-Table, Data-Admin-DB-Name, and Data-Admin-DB-Class Group were not receiving updated cache entries for newly exposed columns. This was an error in the updated database triggers engine code, and has been corrected.
SR-A11421 · Issue 223667
nvarchar support corrected for MS/SQL
Resolved in Pega Version 7.2
The datatype nvarchar (used for Unicode encoded strings) in MS/SQL was incorrectly reported as unsupported. The data type mapping has been reviewed and updated to correct this.
SR-A2733 · Issue 221219
Migration process handles underlying varchar CHAR
Resolved in Pega Version 7.2
Handling for CHAR length semantics has been added for imports of rule schema to support Oracle varchar2 columns, and the import/export will correctly deal with the circumstanced columns of CASETYPEVERSION and PXREFOBJECTCLASS.
SR-A11286 · Issue 224545
Drop Index SQL updated to remove duplicates
Resolved in Pega Version 7.2
If a query was used in SchemaManager to get all of the covered indexes for the table, firing the same query in the DB to generate XML resulted in duplicate indexes and column names. This was traced to the Drop Index SQL being generated twice, and the query to get the covered index columns from the DB has been changed to remove the duplicates.
SR-A11286 · Issue 223221
Drop Index SQL updated to remove duplicates
Resolved in Pega Version 7.2
If a query was used in SchemaManager to get all of the covered indexes for the table, firing the same query in the DB to generate XML resulted in duplicate indexes and column names. This was traced to the Drop Index SQL being generated twice, and the query to get the covered index columns from the DB has been changed to remove the duplicates.
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-A9198 · Issue 218533
Text retrieval for deprecated "Query" button updated for universal browser support
Resolved in Pega Version 7.2
The Firefox popup window provided by the Product rule when querying "Individual Instances to Include" failed to transpose the selected rule information back into the Product ruleform when the OK button was clicked. This was due to the use of the deprecated "Query" button, which does not have support for all browsers, to launch the ListView. To handle this, the node text retrieval method in DataInstancesQueryScript has been updated to use the 'textContent' function (compatible with all browsers) instead of the previous 'innerText'.