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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B35045 · Issue 291487

CMIS files stored according to application config

Resolved in Pega Version 7.3

Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.

SR-B35048 · Issue 292012

CMIS files stored according to application config

Resolved in Pega Version 7.3

Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.

SR-B35050 · Issue 292342

Repaired BIX extract rule filters

Resolved in Pega Version 7.3

pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.

SR-B35050 · Issue 293637

Repaired BIX extract rule filters

Resolved in Pega Version 7.3

pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.

SR-B35741 · Issue 292129

Corrected thread contention in BAC

Resolved in Pega Version 7.3

A thread contention condition was found in BAC due to the use of maccesscache. That function and the matching clearAccessCache() function are no longer used in Basic ApplicationContext and BasicApplicationContextImmutableimpl to resolve the issue.

SR-B3580 · Issue 275558

Error fixed for PMF application RAP

Resolved in Pega Version 7.3

An invalid database script error was being generated when attempting to execute SQL generated from RAP on PostgreSQL. This has been fixed by modifying the matcher logic to remove text[] from the SQL text.

SR-B3591 · Issue 277488

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B3591 · Issue 278006

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B35963 · Issue 292315

pyID displayed in Show relevant Records

Resolved in Pega Version 7.3

Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.

SR-B35963 · Issue 292466

pyID displayed in Show relevant Records

Resolved in Pega Version 7.3

Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.

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