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-D60206 · Issue 529326

Resolved null pointer on Reference Helper startup

Resolved in Pega Version 8.2.6

An issue with the system failing to start and generating a NullPointerException on Rule-Utility-FunctionReferenceHelper.java has been resolved by modifying some Rule-Utility-Function code to better handle threads that are not completely initialized yet but still running rules.

SR-D60318 · Issue 526871

Data table validation message placement updated

Resolved in Pega Version 8.2.6

An issue with validation errors unexpectedly appearing on primary key columns instead of on an added decimal data type column was traced to the system using a temporary page to update the record: if there was an error, all of the messages were copied to the temporary page and put on the first key of the data type. To resolve this, the system will populate the messages on individual properties on the main page and the rest of the messages will be put on the first key of the data type.

SR-D60375 · Issue 527756

Resolved upgrade SqlSyntaxErrorException

Resolved in Pega Version 8.2.6

When trying to perform an in-place update, the error "SqlSyntaxErrorException" appeared. Investigation showed that DDL statements for Adding 'pzInsKey' as PrimaryKey for Tables pc_work and pr_sys_locks were generated during the upgrade while pzInsKey was already the PrimaryKey in corresponding tables. This has been corrected.

SR-D60442 · Issue 522062

Enhanced logging and error messages for JSONMappingUtils failing to map a number value

Resolved in Pega Version 8.2.6

Some integer properties were not mapped from JSON, such as itemID. Investigation showed that because the maximum range of a signed integer is 2,147,483,647, only those itemIDs less than or equal to that were processed during the initial mapping of the incoming JSON data. Others were bypassed to allow for the remaining properties to map to the clipboard. As this mapping incident is rare, no code changes will be made to address it. Instead, if this condition is seen Pega recommends changing the property mode manually to text to prevent arithmetic being done on itemIDs or other integers. In order to better support administrators and developers, updates have been made to the warn/error log messages in the event of JSONMappingUtils failing to map a number value so that missing data mapping will be clearly indicated.

SR-D61199 · Issue 533478

Support expanded for postgres versions and logging improved

Resolved in Pega Version 8.2.6

While trying to import data into the Data Type Tables using a CSV file and selecting the 'Add or Update' option, an error appeared and the import failed. Using 'Add or Delete' worked as expected. This was traced to the import of data failing for postgres version 10.x because UseMerge for postgres did not use merge if the version of Postgres was not 9. Support has now been added for versions of Postgres higher than 9 in SQLGeneratorPostgres.useMerge(), and logging has been enhanced to improve triaging issues such as this.

SR-D61706 · Issue 524956

PropertySet will iterate over chageList map copy to resolve CME

Resolved in Pega Version 8.2.6

An empty menu was seen intermittently when handling incoming email, and a ConcurrentModificationException error was logged. Investigation showed that a step scope changeList map used in the handleChaining method was sometimes modified by another process while the first one was iterating over it. To resolve this, PropertySet will receive copies of the change list map from clipboard pages instead of the original map.

SR-D61971 · Issue 529607

Search Landing Page handling added for email addresses containing hyphens

Resolved in Pega Version 8.2.6

When an e-mail addresse containing a hyphen was entered for the Automated Search Alert functionality, the validation error "Please Enter Valid Email Address(s)" appeared. For example, [email protected] was not accepted. To resolve this, the regexp function used for the email validator has been updated.

SR-D62755 · Issue 522828

Enhanced diagnostic logging for Email Listener failures

Resolved in Pega Version 8.2.6

In order to better diagnose issues where the email listener entered a disabled state as soon as it was started, a catch block has been added to enhance logging the reason of failure.

SR-D62840 · Issue 534124

Updated HashMap logic for better concurrent thread handling

Resolved in Pega Version 8.2.6

The Pega execution engine was getting stuck at com.pega.eclipse.util.collections.HashtableOfIntValues.get for many thread within thread dumps. Investigation showed that when the key was not present in keytable, a thread would be stuck in an endless 'while' loop related to mapping. To resolve this, the data structure that is used for ruleset mapping from HashtableOfIntValues to Concurrent HashMap has been modified to better handle concurrent threads, and the handling for get and put has been updated.

SR-D63234 · Issue 529099

Blobless class handling updated in BIX extract

Resolved in Pega Version 8.2.6

When performing a BIX extract to database, null values were seen for some columns when there were values present in the clipboard and the report definition. Analysis showed that an Extract Rule defined on a Blobless class with a property having a length greater than 30 would return a null value even when the source table's corresponding columns do not have null values. This was due to BIX using an internal Report Definition which would truncate the column alias if the length of the column was greater than 30: when the extract then tried to find the actual property name in the result page, it did not find it and returned a null value. To resolve this, if the class is Blobless, the system will iterate over the property and check whether it is truncated or not. If it it truncated, the truncated name will be used when looking for the property in the result page instead of using the unmatching actual property name. This will ensure the correct value populated in the result page will be used.

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