Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

SR-A102766 · Issue 269648

db2zOS tablespace script logic updated

Resolved in Pega Version 7.2.2

When running the generateddl script against a db2zos database, the tool determines for each table if the current tablespace page size needs to be increased before the DDL changes can be applied. For the pc_work_social table, while the tool included the size of new columns when it calculated the projected table size, it did not take into account the altering of existing columns. This has been fixed by tightening up the JDBC resource handling.

SR-A98103 · Issue 266253

Scheduled recurring Purge/Archive set to reuse specified start time

Resolved in Pega Version 7.2.2

When scheduled to run every day at a particular time, the Purge/Archive function started later each time. This was due to the function using the Agent running time for the rescheduling, starting the next day at the time it ended. The function has now been modified to use the customer-specified start time instead of calculating the Agent time.

SR-A87698 · Issue 256038

SQL info stripped from user-view DB2 error codes

Resolved in Pega Version 7.2.2

A security audit showed that entering bogus values for pyActivity in a URL resulted in actual DB@ error codes provided to user in the exception response. In order to prevent any vulnerability, the message shown to the http client will mask SQLCodes.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us