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-B39458 · Issue 299698

Email Listener checks for engine startup before queue processing

Resolved in Pega Version 7.3

Items in an Email Listener queue were not processed upon server restart and an null-pointer exception was generated. This was due to the Email Listener beginning work too quickly, and has been fixed by modifying the Email Listener code to check whether the engine has started or not before beginning processing.

SR-B39489 · Issue 295922

KeyStoreType of PKCS12 passes validation

Resolved in Pega Version 7.3

Keystore has an allowed file type of PKCS12, but an invalid type error was generated when trying to create a keystore file of this type. This has been corrected.

SR-B39558 · Issue 297151

Logic added to convert UTC Date for REST clipboard mapping

Resolved in Pega Version 7.3

An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.

SR-B40665 · Issue 300419

Update to avoid unnecessary File Listener logging

Resolved in Pega Version 7.3

After upgrade, occasional errors were appearing in the log files while the listener was running correctly and files were being successfully processed. This was traced to the authentication privileges method encountering a service type that was not set, causing the class Rule-Service-null to be created. To avoid the unnecessary logging, code has been added to set service type in case of File Listener.

SR-B40665 · Issue 302272

Update to avoid unnecessary File Listener logging

Resolved in Pega Version 7.3

After upgrade, occasional errors were appearing in the log files while the listener was running correctly and files were being successfully processed. This was traced to the authentication privileges method encountering a service type that was not set, causing the class Rule-Service-null to be created. To avoid the unnecessary logging, code has been added to set service type in case of File Listener.

SR-B40923 · Issue 297879

Removed extra File Listener logging

Resolved in Pega Version 7.3

After upgrade, an INFO entry appeared in the logs every time the file listener processed a file. To correct this, the log statements level has been changed From infoForced to debug.

SR-B41820 · Issue 299434

Map from field updated to ensure Correspondence Name and Type are included

Resolved in Pega Version 7.3

An error was generated while configuring a Map From field as Correspondence. This was an issue with the Correspondence Name not being passed: when the Map From is selected as Correspondence, the backend expecting the Map from Key as a space separated combination of Correspondence Name and Correspondence Type. If only the Correspondence Name was selected, then the back end failed to find the Correspondence Type. This has been fixed by modifying the code to combine left and right from key part to ensure both parts are sent.

SR-B4193 · Issue 274552

NexFlow requestor performance improvements

Resolved in Pega Version 7.3

The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.

SR-B42078 · Issue 298933

Improved logic for external Connect-SOAP error handling

Resolved in Pega Version 7.3

An application with a requirement to check all data pages before loading the portal was generating an error if there was a Connect-SOAP failure during data page load. To resolve this, the logic has been modified to better handle external system exceptions caused by a SOAP failure.

SR-B42078 · Issue 298145

Improved logic for external Connect-SOAP error handling

Resolved in Pega Version 7.3

An application with a requirement to check all data pages before loading the portal was generating an error if there was a Connect-SOAP failure during data page load. To resolve this, the logic has been modified to better handle external system exceptions caused by a SOAP failure.

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