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.

INC- 128143 · Issue 564456

Application content storage change corrected

Resolved in Pega Version 8.2.7

Selecting the Content Storage radio buttons set a background property indicating the content storage option was changed, but the property was not actually being set. Investigation showed that the value for pyContentStorageChanged was not being updated correctly before the section refreshed, meaning the selection was never saved. This has been corrected.

SR-D36826 · Issue 550270

LastAccessTime returned for MDB listeners

Resolved in Pega Version 8.2.7

The lastAccess time for the JMS listener was not being updated. Investigation showed that lastAccessTime was correctly updated whenever isStopping() was called, but isStopping() was not called for MDB listeners because the MDB listeners' state is managed by the app server. This caused accessTime to be empty. To resolve this, ListenerStateImpl has been modified to return mRequestTime as the lastAccessTime if the listener is of type MDB.

SR-D52785 · Issue 518409

Cross-site scripting protection added to layout runtime java and whitelist validation available for host/XFHost

Resolved in Pega Version 8.2.7

In order to protect against cross-site scripting issues, filtering has been added to the RepeatDynamicIndex parameter value in layout runtime java. In addition, a validation for X-Forward-Host value has been added which will be read from a local configuration. This is in the form of a white list regex filter for the host/XFHost header to ensure the URL's actions cannot be redirected.

SR-D58201 · Issue 538979

Data page processing performance improvement

Resolved in Pega Version 8.2.7

After upgrade from Pega 7 to Pega 8, data page processing was noticeably slower. Based on analysis of the issue and results of testing, changes have been made to improve the performance of the query used by the expression parser by using an ClipboardPage API to read values from a Page (ClipboardPageAPI#getString(boolean, String)).

SR-D60830 · Issue 533029

Logic update for classloading synchronization

Resolved in Pega Version 8.2.7

The synchronization logic for classloading has been updated to resolve intermittent deadlocking seen when two DataFlow threads are executing a distribution test.

SR-D67142 · Issue 548641

Enhanced CMIS connector logging

Resolved in Pega Version 8.2.7

Additional diagnostic logging has been added to enhance investigating CMIS connector health.

SR-D72389 · Issue 541946

Handling added for JSON with top level array

Resolved in Pega Version 8.2.7

When using serialize mode in a JSON data transform where the Top element structure was Array and the “For JSON only” relation was selected for relation mode, the result had an incorrect JSON structure. In order to support this configuration, generatePropertyAsJSON has been amended to set isTopLevelPageList to true in instances where automap is off, the top level is an array, and the JSON context is updated within the first step. In addition, generatePageAsJSON has been updated to check this flag when processing mappings in order to ensure these context changes are processed, and updates have been made to generatePropertyAsJSON to ensure that the context is popped when appropriate.

SR-D74376 · Issue 552258

Check added for string vs boolean for pzscan JSON

Resolved in Pega Version 8.2.7

When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.

SR-D74921 · Issue 551787

Error condition will close WebSocket connection

Resolved in Pega Version 8.2.7

An async listener has been added that will close the WebSocket connection when an error condition is encountered.

SR-D75636 · Issue 549347

Improved handling for attachments not using UTF-8 encoding

Resolved in Pega Version 8.2.7

When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.

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