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-C89619 · Issue 429573

Custom section filters retained during refresh

Resolved in Pega Version 8.3

Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.

SR-C95253 · Issue 435786

Custom datetime controls correctly appended to Excel export

Resolved in Pega Version 8.3

The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.

SR-D10309 · Issue 482476

Custom datetime controls correctly appended to Excel export

Resolved in Pega Version 8.3

The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.

INC-164308 · Issue 634409

UseNoCacheHeaders default expiration set to "0"

Resolved in Pega Version 8.6.1

When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".

INC-172521 · Issue 651552

Email template content visible in user application

Resolved in Pega Version 8.6.1

An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.

SR-D61094 · Issue 527341

Browser cache disabled to ensure fresh RAP file retrieval

Resolved in Pega Version 8.1.8

When using RAP download, reusing the same filename as a previous download caused the older file to be retrieved and not the newer version under that name. This was caused by RAP using the browser cache and downloading the same folder from service export directory. To resolve this, validation has been inserted to disable using the browser cache for the HTTP response.

SR-D37275 · Issue 519027

Enabled PDF attachment for iPad Safari

Resolved in Pega Version 8.1.8

It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.

INC-145802 · Issue 636323

Oracle temporary space explicitly freed after writing LOBs

Resolved in Pega Version 8.6.1

Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions and the table involved had inline BLOB storage such as small blob tables like Log-service-file (2-4kB blobs). This did not occur when using OJDBC7, but investigation with Oracle could not determine why the older version did not have this issue. This issue has been resolved by explicitly freeing the LOB space with a call to free() / freeTemporary() , a utility for LOB objects that was introduced in JDBC 4.

SR-C93555 · Issue 431598

BulkMover updated to not treat Numerics as strings

Resolved in Pega Version 8.3

When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.

INC-170514 · Issue 653763

Lock conflict resolved for AssignmentCheck

Resolved in Pega Version 8.6.1

The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.

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