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-C53711 · Issue 391792

Acecss Group encoding updated for compatibility with the latest versiosn of Tomcat

Resolved in Pega Version 8.2

After upgrading to Tomcat 7.0.88, there were intermittent login issues. This was due to the access group hashcode having "[[" appended in the URL, which the latest version of Tomcat does not accept. To resolve this, updates have been made to URLComponentProcessor where the encoding of the access group is done.

SR-C49920 · Issue 392248

Presaveas activity for Proposition Filter fixed

Resolved in Pega Version 8.2

An error appeared when attempting to add a proposition filter to a Revision Management overlay. This was inadvertently caused by a logic change for 'save as' done to address another issue, and has been corrected in the presaveas activity of Proposition Filter.

SR-C44259 · Issue 408852

Lock handling for DB during platform start/restart updated to only delete expired locks

Resolved in Pega Version 8.2

After quiese of the node serving the user and server, instance restart locks assigned to the user were deleted in the database. This led to the error 'You have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue.' appearing when attempting to submit a previously opened case. To correct this, the lock handling for the database during Platform start or restart has been updated; a filter for comparing sLockExpireTime with SYSDATE or CURRENT_TIMESTAMP in mDeleteStatementForSystem SQL query in DBLockProviderImpl Java class has been added so that only expired locks will be deleted.

SR-C40740 · Issue 408513

Improved error handling added for sync issue with malformed JSON action

Resolved in Pega Version 8.2

A sync issue with a timesheet record was preventing mileage submission. This appears to be caused by a malformed JSON action being inserted into the actions queue sent to the server, and enhanced error handling has been inserted to avoid this issue.

SR-C34802 · Issue 388490

DomainId Column size increased in Pegadata.Address table

Resolved in Pega Version 8.2

Previously, domainId (in table pegadata.p_Address ) had a column length maximum of 16 characters. This has been increased to 256.

SR-C32383 · Issue 404383

Pegacall Longpoll now supports rerty after network drop

Resolved in Pega Version 8.2

Previously, Pegacall Longpoll would not auto-connect after a network drop, although polling could be restarted by refreshing the browser. Retry support has now been added to Longpoll.

SR-C61477 · Issue 418265

HTML conversion added to email IVA

Resolved in Pega Version 8.2

When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.

SR-C79142 · Issue 417678

HTML conversion added to email IVA

Resolved in Pega Version 8.2

When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.

SR-C44297 · Issue 397534

XSS filtering added to RTE control

Resolved in Pega Version 8.2

The system has been updated to close a vulnerability with RTE where an authenticated application user could potentially inject an XSS payload into the Case Notes section for later execution.

SR-C65032 · Issue 407952

XSS filtering added to RTE control

Resolved in Pega Version 8.2

The system has been updated to close a vunerbility with RTE where an authenticated application user could potentially inject an XSS payload into the Case Notes section for later execution.

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