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.

SR-C86138 · Issue 431776

Security updates for avatar upload function

Resolved in Pega Version 8.2.2

Updates have been made to enhance security around the avatar upload function.

SR-C80129 · Issue 425387

Enhancement added to hide class join warning from end user

Resolved in Pega Version 8.2.2

An enhancement has been added to hide the joined class warning message at the end user portal if the section pzManageRecords is delegated to the user. This is done by by checking pxLimitedAccess on the pxThread clipboard page.

SR-C79851 · Issue 430384

Filter logic updated for Warning Summary guardrail report

Resolved in Pega Version 8.2.2

After scheduling a Guardrail report for Warning Summary, the warning summary reports received in email were blank irrespective of the filter criteria. The logic filters have been modified to resolve this issue.

SR-C96362 · Issue 433332

XSS filter added to API form handling

Resolved in Pega Version 8.2.2

An XSS scripting filter has been added for properties that can be changed via API.

SR-C77121 · Issue 423113

Looping issue with CyberArk resolved

Resolved in Pega Version 8.2.2

In order to avoid looping issues when using CyberArk integration, the reference to PRMiniLoader has been removed from PRBaseLoader.

SR-D114 · Issue 435313

Grid menu dropdown properly hidden while editing filter

Resolved in Pega Version 8.2.2

After opening the filter options as if to change the filter, summarizing any of the available columns without closing the filter resulted in a screen showing a broken filter. This was traced to the implementation of the navigation menu for auto-generated grids, which was not allowing other functions while any of the "inline modals" are being used, such as editing a filter. To correct this, the grid menu dropdown will not be shown while editing a filter. This is consistent with the rest of the UI actions which are hidden while editing a filter.

SR-C88882 · Issue 431068

External mapping definitions will be used for exported property names

Resolved in Pega Version 8.2.2

Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.

SR-D2457 · Issue 437345

Stale transaction error resolved for Robot Manager deletions

Resolved in Pega Version 8.2.2

The UI was hanging and displaying a stale transaction error after multiple entities were deleted from the Robot Manager UI. This has been resolved by adding clientFrame handling for SPA cases separately in the pega_ui_modaldialog js file.

SR-D13 · Issue 434982

Memory leak repaired

Resolved in Pega Version 8.2.2

A server side memory leak was traced to heap utilization increasing due to a Stream control assembly problem where the CleanForReuse() function was not cleaning up pzAuto. The cleanForReuse method in generated HTML properties is used to either initialize local fields, in which case aContext will be non-null, or to clear the object for pooling, in which case aContext will be null. Because the pzAuto variable was not being properly nullified, pooled controls were retaining stale references to StreamTools, LayoutRuntime, PRThread, and others. This has been resolved by adding code to ensure the pzAuto variable is correctly nullified.

SR-C90358 · Issue 433296

Updated Attach Content Control for use in repeat grid

Resolved in Pega Version 8.2.2

When using Attach Content Control in a repeat grid, selecting a file via attachcontent control and submitting the page resulted in the message "The operation completed successfully, but returned no content". This was traced to the newassignPage being removed after closing the modal, causing finishassignment to fail. To resolve this, the Attach Content Control function has been modified to set the needed grid attributes for desktop implementation to ensure newAssignPage will be available to the attach content modal action.

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