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-124944 · Issue 186362

Handling added for 'agentinfoupdate' map exceptions

Resolved in Pega Version 7.1.8

The function 'agentinfoupdate' updates a distributed map (provided by Hazelcast) for the purpose of an agent landing page. This distributed map was throwing exceptions which did not have proper handling, resulting in the agent scheduler being terminated and thereby stopping agent functionality. The required handling has been added to prevent this situation.

SR-124989 · Issue 188104

Added error handling for passivated dashboard tab

Resolved in Pega Version 7.1.8

If the dashboard tab has been ide for 30 minutes or more, clicking on links on the tab generated 'not found' errors and NPE exceptions . This failure was traced to the passivation process, which does not save read-only pages and has been resolved by modifying change tracker logic to not send null values when read-only data page is not present.

SR-125192 · Issue 189446

Thread Name displayed in RemoveInactiveThread API

Resolved in Pega Version 7.1.8

An enhancement has been added to display the thread name when throwing an exception during thread deletion: "You may not remove the "+aThreadName+" thread currently processing".

SR-125520 · Issue 194874

Open Authoring OCX and other certificates renewed

Resolved in Pega Version 7.1.8

In order to ensure ActiveX and other helper programs continue to work properly, the components have been re-signed with a digital certificate expiring 12-Mar-2018.

SR-125610 · Issue 189352

Added handling for property-defined declare value list indexing

Resolved in Pega Version 7.1.8

When adding or updating entries in a value list, the corresponding index entries were not getting created in the database. This was caused by handling that was missing from the minimum feature string clipboard properties that were recently introduced for better performance. These strings get created when it's not a reference property and has no declaratives defined etc. In this case, a declare index that is defined on the value list property should not have those elements be minimum feature properties. To correct this, the code has been changed to pass the featureID of the parent property.

SR-125913 · Issue 192447

Fixed file attachments in Mobile

Resolved in Pega Version 7.1.8

When using the AttachContent Control functionality in mobile, attaching a file popped up a window with the message 'File attached successfully', but no Action Sets associated with file attachments were actually run. Using the same functionality on desktop did not have any issues. This problem was traced to an error in the JavaScript code for the mobile control relating to the access group, and has been corrected.

SR-126011 · Issue 195418

RUF 'hasMessages' working with Declarative Pages

Resolved in Pega Version 7.1.8

Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.

SR-126011 · Issue 195591

RUF 'hasMessages' working with Declarative Pages

Resolved in Pega Version 7.1.8

Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.

SR-126092 · Issue 189635

Enhanced logging for SQL exceptions with BIX

Resolved in Pega Version 7.1.8

In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.

SR-126455 · Issue 189883

Stale thread issue resolved and logging updated

Resolved in Pega Version 7.1.8

The error "com.pega.pegarules.pub.context.StaleThreadError: Thread has been recycled" was appearing sporadically in the log files. The root cause was traced to the usage daemon, and has been resolved by changing the logic such that while capturing usage data, the system will avoid setting the last thread as processing thread while taking requestor lock. This avoids usage of a stale thread. Additionally, a change was made to avoid repeated logging of a stale thread error while creating a PRException object when exception occurs do occur due to a stale thread.

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