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-132507 · Issue 201175

Upgraded Apache Commons FileUpload

Resolved in Pega Version 7.1.8

In order to enhance system security, Apache commons-fileupload-1.2 has been upgraded to commons-fileupload-1.3.1.

SR-132588 · Issue 202025

Corrected Save Rule-Connect-JMS with Global Resource Set

Resolved in Pega Version 7.1.8

Attempting to save Rule-Connect-JMS containing dynamic settings to avoid hardcoded parameter values was failing. This was due to a validation step that wrongly converted formatting warnings to errors, and has been corrected.

SR-132919 · Issue 201479

REST querystring not forced to lower case

Resolved in Pega Version 7.1.8

A Rule-Service-REST.validate activity which forced the query string to lowercase was leading to REST services are not receiving the input values in case of capital or camelCase query strings. To resolve this, the code that fetches querystring name for REST will not convert it to lower case.

SR-128332 · Issue 199072

Added detection for WSDL import failure

Resolved in Pega Version 7.1.8

Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.

SR-129312 · Issue 198553

Corrected HTML display of characters in reply emails

Resolved in Pega Version 7.1.8

HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.

SR-131612 · Issue 200253

Handling added for accent characters in DataTable editing

Resolved in Pega Version 7.1.8

When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.

SR-127385 · Issue 235813

Fixed user authorization filtering error in extracts

Resolved in Pega Version 7.2.1

Extraction was failing sporadically due to the filter condition not being picked up by all the extract rules when running BIX. This was due to an error in authorizing the requestor with username/password causing differences in datetime formats, and has been fixed.

SR-A10491 · Issue 234174

Locking corrected for WebLogic BMT transactions

Resolved in Pega Version 7.2.1

Incomplete locking for WebLogic BMT transactions caused work items in the queue to be processed by duplicate agents even though the item was already processed. This has been fixed.

SR-A10653 · Issue 236942

Fixed NPE in the Connector and Metadata wizard

Resolved in Pega Version 7.2.1

The Connector and Metadata wizard was throwing a NPE in logs due to the inability to resolve a header schema definition during import. To fix this, the system will skip the unresolved header mapping processing and log an error message instead of creating an empty entry.

SR-A11695 · Issue 229147

EXCEPTION_BLACKOUT time calculation fixed

Resolved in Pega Version 7.2.1

When calculating the time for the EXCEPTION_BLACKOUT period in EmailListener, the dimensions were incorrect due to errors in the sleep time observed when email listener failed to establish connection. This 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