SR-A23916 · Issue 253818
BIX extract WO handling corrected
Resolved in Pega Version 7.2.2
After upgrade, a BIX report was not working correctly due to the difference in work object handling. During BIX extract, the currently extracted WO was being maintained on a tempPage that was not subsequently being used for the lookup. This has been fixed.
SR-A76413 · Issue 254770
Custom datatypes import support added to SQL RD
Resolved in Pega Version 7.2.2
After upgrade, external classes of type 'text' mapped to an external DB were throwing an error while executing report definition. This was due to the method used to get the column type, and the logic has been updated to correct this.
SR-A52484 · Issue 251721
BIX Extract retains pre-upgrade filenames and columns
Resolved in Pega Version 7.2.2
After upgrade, extract rules were created with underscores replacing dashes in the original filenames and ExtractIndentifier and ExtractDateTime columns were added to the output csv file. This was an inadvertent change related to enhancements made to filename conventions, and has been corrected with the prconfig "bix/retainOriginalFileNameForCSV" to retain the filename as provided in the extract rule and the prconfig "bix/ignoreAdditionalColumnsInCSV" to not add the new additional columns pxExtractIdentifier and pxExtractDateTime when upgrading rulesets.
SR-A24412 · Issue 249993
Calendar icon display fixed for Microsoft Internet Explorer11
Resolved in Pega Version 7.2.2
Calendar icons were not displayed in a data table in Microsoft Internet Explorer 11 due to the browser not supporting the icon rendering. A meta tag has been added in the ReviewHarness to correct this.
SR-A23686 · Issue 249793
Support extended for NUMERIC types in RD SQL joins/filters
Resolved in Pega Version 7.2.2
Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.
SR-A75946 · Issue 252101
pxCommitDateTime BIX extraction more robust
Resolved in Pega Version 7.2.2
The exported XML file was not including the pxCommitDateTime column even when that column was included in the BIX extraction. This was traced to the site trying to perform the commit on the same work object more than once: performing the commit the second time caused the previous value to be overridden by the new commitdatetime. That led to the pxCommitDateTime not being stored in the BLOB, and since BIX extracts the data from source table's BLOB, it cannot extract the value of pxCommitDateTime. To resolve this, the source query that BIX uses has been modified to get both pzPVStream and pxCommitDateTime (if the column is present in the source table) and use the value of pxCommitDateTime from the resultset while writing to the output file.
SR-A87552 · Issue 257706
Implicit privileges do not generate warnings
Resolved in Pega Version 7.2.2
RARO with implicit privileges was generating warnings that affected the compliance score. There is a particular format for declaring implicit privileges. i.e. Classname:ruleName, and the system has been updated with a check for this so implicit privileges will not be adding any guardrail warnings.
SR-A101006 · Issue 272734
JDBC password handling corrected
Resolved in Pega Version 7.2.2
After upgrade, a JDBC database connection on WebSphere 8.5/Oracle 11G indicated success on test connection, but a username/password "connection could not be obtained" error was thrown when attempting to save the connection. This was due to the handling of the encrypted password, and has been fixed.
SR-A101808 · Issue 269472
WebSphere deployment documentation updated to clarify JVM configuration advice
Resolved in Pega Version 7.2.2
The deployment guides for WebSphere have been updated to clearly distinguish between Oracle and IBM JVM when providing JVM configuration advice.
SR-A24989 · Issue 248910
WebSphere deployment guide updated to clarify scope settings
Resolved in Pega Version 7.2.2
The WebSphere Deployment Guide has been updated to indicate that the scope must be "server". If this is not set correctly in a split schema installation, the defaultSchema namespace bindings are defined at the cell level and will not be picked up at start, and the database user in the jdbc/PegaRULES datasource will not have the necessary privileges to run the system. Please see WAS deployment guides on the PDN for further information.