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.
SR-A91805 · Issue 265722
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-A97582 · Issue 270053
Resolved error in importing code jar with tracer on
Resolved in Pega Version 7.2.2
Importing a code jar with tracer on intermittently failed and showed a blank screen. This was caused by pxCheckCodeSet closing the archive even through import is in progress, and has been fixed by modifying the CheckCodeSet activity to mark the import progress as true so that passivation doesn't cause archive to be closed.
SR-B469 · Issue 273774
Improved performance for installing schema related raps
Resolved in Pega Version 7.2.2
Performance improvements have been made relating to installing schema related raps.
SR-A99908 · Issue 270284
Purge export logic updated to handle TimeCreated keys that differ by milliseconds
Resolved in Pega Version 7.2.2
Purge archive was failing during export of the archives. Analysis showed that when exporting keys of history class mapped to a table with no blob and pxTimeCreated as Key column, mapping this to a column of Date type on Oracle caused the pzinskeys of history- instances to be recalculated and the millisecond part of the time stamp was rounded in the key to 000.This caused keys which just differed in milliseconds to become duplicates and export failed. This has been resolved by modifying the export logic to handle keys which differ in milliseconds for Blobless History class instances.
SR-A92640 · Issue 266679
Upgrade rules considers DADT instances for mapping
Resolved in Pega Version 7.2.2
When migrating and upgrading the rules tables to a new schema, the _upgradeRuleBase task was trying to remap some work classes/tables to pr_other. This was due to the class name being compared with case sensitivity when the site had DADT instances for which the class name was not same as the class instance. To resolve this, the check has been made case insensitive so DADT instances are not missed.