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-A101500 · Issue 278178

Menubar Object memory leak repaired

Resolved in Pega Version 7.3

A memory leak has been resolved by eliminating unnecessary DesktopMouseClick events when creating a new old-Menubar object.

SR-A101675 · Issue 270578

Size to Content refresh updated

Resolved in Pega Version 7.3

A expandable grid with a text area and button as columns in it was not correctly calculating the size after refreshing. An explicit call to the resizeHarnessActual has been added to ensure expected behavior.

SR-A102222 · Issue 270905

Command line BIX extract includes pzinskey in XSD

Resolved in Pega Version 7.3

When running an extract to XML from within the UI, the generated XML and XSD both include the pzInskey. However, when the extract rule was saved to a file and run from the command line using the -I option, the XML file had the pzInskey but the XSD file did not. This has been corrected by ensuing the pzInsKey is included as part of XSD generated with the -I option.

SR-A102237 · Issue 271876

Unmapped columns from an external table skipped in DDL query generation.

Resolved in Pega Version 7.3

The OBJ-SAVE method was generating a query in which unmapped columns were also getting updated. As these columns were not mapped, DB columns were being updated with the value NULL. This was due to the Obj-Save function always saving the entire object, causing an issue when only part of a table is mapped to a class. To correct this, new prconfig and DASS settings have been added to exclude unmapped columns of an external table as part of DDL query generation.

SR-A102260 · Issue 277204

Current Cassandra log displayed on landing page

Resolved in Pega Version 7.3

While the Cassandra log files were being correctly generated, the landing page showed an older file instead of the current one. This has been fixed.

SR-A102447 · Issue 276743

Corrected post-rule migration SOAP null-pointer exception

Resolved in Pega Version 7.3

In some multi tenant environments, a null-pointer exception exception was appearing for the first SOAP call after a rules migration. Subsequent calls worked as expected. This was caused by a timing issue related to loading the global context cache for a given access group, and the event order handling has been improved to correct it.

SR-A102729 · Issue 272707

Mobile modal display timing corrected

Resolved in Pega Version 7.3

When the full screen for mobile device option was used while launching a local action, the template buttons (Submit and Cancel) appeared to be missing until the screen adjusted during a focus shift to an editable field. This was an issue with asynchronous display timing in the modal dialog template using dynamic layouts with client side visible whens, and has been fixed.

SR-A102969 · Issue 273954

XSS security update for error.jsp

Resolved in Pega Version 7.3

The error.jsp file has been updated for better XSS security with WebSphere and Firefox.

SR-A103079 · Issue 273545

Check added for RD date time values

Resolved in Pega Version 7.3

An exception was generated when running RD by choosing the relationship for a datetime property as "Is not null" in filter conditions before displaying the data. This has been fixed with the addition of a check for the date time value.

SR-A103192 · Issue 271775

ReadOnly radiobutton display fixed for null value

Resolved in Pega Version 7.3

When a radiobutton control was set ReadOnly, "--" was not displaying as expected when the property did not contain any value. Instead, the radio button values were displayed as empty. This was caused by a missing span tag element for read only mode, and has been fixed.

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