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-D114 · Issue 435312

Grid menu dropdown properly hidden while editing filter

Resolved in Pega Version 8.3

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-C91898 · Issue 435421

Resolved Rich Text Editor display in popup windows

Resolved in Pega Version 8.3

The Rich text editor was not displaying in popup windows although it did display otherwise. Investigation traced this to the harness context APIs used in "pega.contro.IRTE.init" (pzpega_control_richtexteditor.js rule) returning rteTextArea as null, leading to the RTE scripts failing to bind the ckeditor dom. This has been fixed by replacing the harness context APIs with ones better suited to this use.

SR-C94190 · Issue 435433

Fixed Export to PDF page formatting

Resolved in Pega Version 8.3

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.

SR-D520 · Issue 435485

Wait corrected for sub case after reopening

Resolved in Pega Version 8.3

A re-opened parent case was not waiting for the sub case when a sub case was reopened, but it did wait if there was no sub case on the reopened parent case. This has been resolved by enhancing the system to better handle the reopen of activator and dependent work objects by checking the reopen time: - pzGetAllStatusforDepClass activity: added step 2 to consider activator reopen time - pzGetMessageKeysForFlowDependencies list view: added criteria to filter on reopen time

SR-C95727 · Issue 435551

Enhancement added to automatically manage runtime context for background processing

Resolved in Pega Version 8.3

After creating a dedicated queue processor in a branch ruleset, the processor was not showing up in the queue processor list in Admin Studio. Attempting to queue something to this queue processor with a correct access group pointing to an application with access to the branch ruleset resulted in the error "Unable to find queue processor instance in memory". Moving the queue processor to a ruleset other than the branch worked as expected. This was traced to an issue with context management. In order to improve this process, an enhancement has been added for automatic management of the runtime context for the Background Processing mechanism. This will use system runtime context to discover queue processors and job schedulers that need to be run, and the context will automatically maintained by the platform when Applications are created, deleted, saved or imported. The system administrator is able to use a portal (studio) to manually modify the system runtime context by adding, reordering, removing Applications and changing the application version. To use this automatic management, check the "Include in background processing" checkbox on the application rule form (Advanced section): when checked, the application is placed on the list of System Runtime Context during application rule save (which happens e.g. during application import, migration, etc). If the background processing checkbox is not set, the runtime context of the background processing will continue to require manual management, but that management will now be in System Runtime Context instead in the previously used ASYNCPROCESSOR requestor type, which has been deprecated.

SR-C89504 · Issue 435565

Multi-Select values visible in read-only

Resolved in Pega Version 8.3

The Selected Multi-Select values were not seen on the read-only review screen. This has been corrected.

SR-C87873 · Issue 435585

Race condition handling added to resolve stuck class loader threads

Resolved in Pega Version 8.3

A JVM became unresponsive after new JVM traffic was brought in. In reviewing the threaddump, there were hundreds of threads that originated from PRClassLoaderDB.getDefinitionForName or PRClassLoaderDB.getorCreateDefinitionForName found in a "stuck" state waiting on a condition. Investigation showed there was a thread deadlock caused by the system loading class definitions while an external resource was asking for a snapshot of the resources being loaded. This has been resolved by adding handling for the race condition.

SR-C97772 · Issue 435629

Fixed Export to PDF page formatting

Resolved in Pega Version 8.3

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.

SR-C92363 · Issue 435674

Removed duplicated cross-site scripting filtering

Resolved in Pega Version 8.3

Some specific special characters ( "(" , ")", "%" , "&" ) in Delegated View of Data Type rules are not displayed properly in Edit view. Investigation showed the parameter value was subject to multiple passes of cross-site filtering, and the unneeded cross-site scripting filters have been removed.

SR-C98214 · Issue 435683

Decision Table keeps proper values when a column is deleted

Resolved in Pega Version 8.3

When the first column in a Decision Table was deleted and the rule saved, the value that was in the second column was replaced in the first row. This has been corrected.

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