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-A6449 · Issue 214540

Clarified page handling for Idle Processing activity

Resolved in Pega Version 7.2

The Idle Processing activity in file listener was throwing a NullPointerException(NPE) when it had the Obj-Browse/RDB-Open method in it. This has been corrected by modifying the code to send the primary page and a parameter page if null page values are encountered.

SR-A7298 · Issue 215177

Clarified page handling for Idle Processing activity

Resolved in Pega Version 7.2

The Idle Processing activity in file listener was throwing a NullPointerException(NPE) when it had the Obj-Browse/RDB-Open method in it. This has been corrected by modifying the code to send the primary page and a parameter page if null page values are encountered.

SR-A8445 · Issue 220085

Ensured display of empty user worklist section in hybrid client

Resolved in Pega Version 7.2

The user worklist section was not being displayed in the hybrid client if the login had no assignments (the WL(D_pyUserWorkList pxresultcount is zero) and the crewleaderworklist harness had a repeating dynamic layout. This has been corrected.

SR-A8217 · Issue 223611

Added server retry for push notifications in Sales Automation 7.14 / SFADevelopment for Android

Resolved in Pega Version 7.2

Push Notifications were not working on Sales Automation 7.14 / SFADevelopment for Android. This was traced to an error returned by the GCM server during registration, and the code has been modified to re-try the registration process if a failure is encountered.

SR-A12537 · Issue 224733

Optimistic locking honors OfflineEnabled function

Resolved in Pega Version 7.2

After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.

SR-A7642 · Issue 218030

Code added to support automated unit tests on Microsoft Internet Explorer 11

Resolved in Pega Version 7.2

When attempting to create automated tests for a decision table, the dialog to create the test cases was coming up without the version dropdown box. This was traced to a null object being returned for the WebWB_New_Available rule due to Element.all support being dropped by Microsoft Internet Explorer 11. To resolve this, that rule has been modified in order to work on all versions of Microsoft Internet Explorer .

SR-A10487 · Issue 221146

Resolved BIX command line NPE for username/password

Resolved in Pega Version 7.2

Attempting to run a BIX extraction from the command line without specifying -a/-p (username and password) parameters failed with a NullPointerException. This has been corrected.

SR-A11445 · Issue 222408

Wildcard extraction trims extraneous spaces from BIX output

Resolved in Pega Version 7.2

An extra space was being appended to the XML output file name when %t was used. The ExtractImpl.replaceWildCards() method has been updated to trim any additional spaces at the end.

SR-A12684 · Issue 224534

Extracts count corrected when using XML as output

Resolved in Pega Version 7.2

While running an extract using XML as output, a difference was observed in the number of records being extracted when compared with 'Database Schema' as output. The Pega-BIX logs contained failed records with 'Index out of bounds' exceptions. This was traced to missing handling for the value group property references in this scenario, and has been corrected.

SR-A10974 · Issue 223153

BIX Manifest enhanced to include fully qualified property names

Resolved in Pega Version 7.2

If an page list property with the same name existed under two levels in the extracted data (specified in the extract rule multiple times), there was no way to differentiate them when viewing the BIX Manifest file. To resolve this, an enhancement has been added to ExtractImpl to include the fully qualified name for the property.

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