SR-A99595 · Issue 267749
Error message displayed on UI for RAP import failure
Resolved in Pega Version 7.2.2
A build success message appeared after importing a RAP file even though the import process failed and an error was put in the log file. During the import process, the JSR94Client did not delegate any exceptions to the callers. This has been changed.
SR-A95888 · Issue 270679
MSSQL upgrade indexing updated
Resolved in Pega Version 7.2.2
After upgrade, an index was missing. Analysis showed the create index statement was using an include clause to add pzInskey in the index column list, which did not work on MSSQL because the DatabaseMetadata interface for the MSSQL JDBC driver did not return the columns in the INCLUDE list when a call to getIndexInfo was made. This resulted in a mismatch of the column list available in pr_changelog. This has been fixed, and automation has been added to detect this mismatch in the future.
SR-A87670 · Issue 256183
Better handling for external data source in the Upgrade utility
Resolved in Pega Version 7.2.2
An external data source included in the system configuration was being considered in the process of upgrade, resulting in an exception. To fix this, the UpgradeApplicationSchemaUtility has been modified to log errors with a message to rerun "Update Application Schema" from the landing page and then continue.
SR-A24411 · Issue 257220
Fastloader update error handling improved
Resolved in Pega Version 7.2.2
An issue was found where the FastLoader failed when an update to the vw table modified 0 instances. The update.bat script has been modified to better handle encountering data that did not get updated as expected.
SR-A76982 · Issue 253572
pyRuleSet added to fields of listview filter if not explicitly set
Resolved in Pega Version 7.2.2
Data Instances were not included in product jar when a Developer included ListView Rule with certain Filter criteria in Product Rule to extract Data Instances. When a listview filter is added to RAP, the instances returned by listview must be packaged by Rule-Admin-Product, but this was not happening if the listview filter did not have pyRuleSet in its fields. When a pyRuleSet is not included in listview, records returned by listview filter will be treated as invalid by export process in InstanceInfo class. To avoid unexpected behavior, .pyRuleSet will now be added to fields of listview filter if it doesn't exist.
SR-A90125 · Issue 258542
Index reference synchronizer upgraded to capture previously shipped rulesets during upgrade
Resolved in Pega Version 7.2.2
During upgrade, some sites were seeing an SQLIntegrityConstraintViolationException error. This was caused by the presence of rulesets (e.g. PegaUVU, PredictiveAnalytics-UI) that were once shipped but are no longer, but that have rules that are still shipped. To correct this problem, the index reference synchronizer has been upgraded to capture those previously shipped rulesets.
SR-A97991 · Issue 268664
Index reference synchronizer upgraded to capture previously shipped rulesets during upgrade
Resolved in Pega Version 7.2.2
During upgrade, some sites were seeing an SQLIntegrityConstraintViolationException error. This was caused by the presence of rulesets (e.g. PegaUVU, PredictiveAnalytics-UI) that were once shipped but are no longer, but that have rules that are still shipped. To correct this problem, the index reference synchronizer has been upgraded to capture those previously shipped rulesets.
SR-A23701 · Issue 257746
Archive/ Purge JVM dependence removed
Resolved in Pega Version 7.2.2
If the JVM was shut down in the middle of the purge and archive process, some SLA queue items remained in a 'now-processing state' and were not automatically picked up by the SLA agent for rescheduling when the JVM was brought up again. This has been fixed by redesigning the the Archive/ Purge flow to run in the background in queue batches so SLA queue items will be updated immediately with their next goal. With this approach, updates of SLA queue items will not depend on purge and archive process duration, and SLA queue items will always be in a scheduled state.
SR-A89765 · Issue 260524
Archive/ Purge JVM dependence removed
Resolved in Pega Version 7.2.2
If the JVM was shut down in the middle of the purge and archive process, some SLA queue items remained in a 'now-processing state' and were not automatically picked up by the SLA agent for rescheduling when the JVM was brought up again. This has been fixed by redesigning the the Archive/ Purge flow to run in the background in queue batches so SLA queue items will be updated immediately with their next goal. With this approach, updates of SLA queue items will not depend on purge and archive process duration, and SLA queue items will always be in a scheduled state.
SR-A91805 · Issue 259301
Archive/ Purge JVM dependence removed
Resolved in Pega Version 7.2.2
If the JVM was shut down in the middle of the purge and archive process, some SLA queue items remained in a 'now-processing state' and were not automatically picked up by the SLA agent for rescheduling when the JVM was brought up again. This has been fixed by redesigning the the Archive/ Purge flow to run in the background in queue batches so SLA queue items will be updated immediately with their next goal. With this approach, updates of SLA queue items will not depend on purge and archive process duration, and SLA queue items will always be in a scheduled state.