SR-A24246 · Issue 248666
Event size difference on calendar corrected
Resolved in Pega Version 7.2.2
When using the out-of-the-box calendar gadget to display some events apart from the worklist goals and deadlines, an event shown on the calendar was correct in the monthly view but had the wrong time and duration in the daily view. This was traced to the way the height of the div tag was calculated in different functions, and has been corrected.
SR-A38578 · Issue 253239
Population handling added for null value flowType property
Resolved in Pega Version 7.2.2
While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.
SR-A19119 · Issue 241157
Improved error handling for XML-executed BIX extract failures
Resolved in Pega Version 7.2.2
When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.
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-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.