SR-A82001 · Issue 255793
Keyed access data pages consider grid sort
Resolved in Pega Version 7.2.2
Page properties populated from keyed data page access were not taking into account grid sorting when passing the page list keys. This did work with the data page set to "Reload once per interaction" on the Refresh strategy, but this caused performance issues (as the SOAP service source was invoked with every single interaction on the data page). The cause was the hash table of keys in keyed page list not being rehashed after sorting, and this has been fixed.
SR-A99690 · Issue 270878
Extended Currency codes working as expected
Resolved in Pega Version 7.2.2
Pega provides the means to extend support for modified currency codes by way of a currency.properties file that holds the required currency code values. This files can be created and placed in the java_home lib folder. To resolve an issue where the API CurrencyProperties getCurrencyProperties(String aCurrencyCode) was not working for overridden values due to the value being stored as a locale code when retrieval was looking for a currency code, changes have been made to the lookup logic of where the currency.properties file will be read and when those values are updated in the currency map that the engine maintains internally.
SR-A22374 · Issue 250037
Node.isUsable() has been updated to return more accurate startup status
Resolved in Pega Version 7.2.2
Previously, Node.isUsable only checked whether the node is initialized or not. This created the possibility that if an Agent was started late in the engine start-up, node.isUsable() could return true while the agent was still null. In order to retain backward compatibility, a new API isStarted() has been added to the system to determine whether the server is completely up or not.
SR-A24733 · Issue 255983
Roles/Portals default setting updated to handle >50 portals
Resolved in Pega Version 7.2.2
Previously, the default setting for max Records was 50 when no number was specified in the list Page, but this was causing errors in the Data-Admin-Operator-AccessGroup Validate activity if the site had more than 50 portal records. This has been corrected by setting pyMaxRecords to 0 (which fetches an unlimited number of records) for the Validate activity while validating each portal.
SR-A90037 · Issue 263152
Handling added for BIX command line parameter combination
Resolved in Pega Version 7.2.2
Running a series of comma separated extract rules to an XML file from the Pega BIX command line using -i parameter resulted the incorrect elements in the corresponding XSD file. Running each extraction separately generated the XSD file correctly. This was caused by multiple XML extracts run using -i and without -a and -p resulting in incorrect XSD schema generation for one of the extracts, and handling has been added to ensure the proper generation.
SR-A90037 · Issue 263071
Handling added for BIX command line parameter combination
Resolved in Pega Version 7.2.2
Running a series of comma separated extract rules to an XML file from the Pega BIX command line using -i parameter resulted the incorrect elements in the corresponding XSD file. Running each extraction separately generated the XSD file correctly. This was caused by multiple XML extracts run using -i and without -a and -p resulting in incorrect XSD schema generation for one of the extracts, and handling has been added to ensure the proper generation.
SR-A90037 · Issue 263130
Handling added for BIX command line parameter combination
Resolved in Pega Version 7.2.2
Running a series of comma separated extract rules to an XML file from the Pega BIX command line using -i parameter resulted the incorrect elements in the corresponding XSD file. Running each extraction separately generated the XSD file correctly. This was caused by multiple XML extracts run using -i and without -a and -p resulting in incorrect XSD schema generation for one of the extracts, and handling has been added to ensure the proper generation.
SR-A90037 · Issue 260736
Handling added for BIX command line parameter combination
Resolved in Pega Version 7.2.2
Running a series of comma separated extract rules to an XML file from the Pega BIX command line using -i parameter resulted the incorrect elements in the corresponding XSD file. Running each extraction separately generated the XSD file correctly. This was caused by multiple XML extracts run using -i and without -a and -p resulting in incorrect XSD schema generation for one of the extracts, and handling has been added to ensure the proper generation.
SR-A23970 · Issue 249825
RecreateIndexesForClass OOM resolved
Resolved in Pega Version 7.2.2
Running the activity RecreateIndexesForClass after creating a new Declare index rule in order to reindex old existing work objects was causing a JVM OOM error that required a restart. This was traced to the API fetching all of the records at once to reindex and save, and has been resolved by modifying the function to do an Obj-browse of all the instances and reindex/save the instance one by one.
SR-A23686 · Issue 248675
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.