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-A6172 · Issue 208100

obj-delete and obj-open now working with external DB

Resolved in Pega Version 7.2

An activity was failing when trying to perform an obj-open or an obj-delete or Obj-Open-By-Handle or Obj-Refresh-And-Lock or Obj-save on an external DB2 database with column type as Date. This issue occurred when a class was mapped to a table in an external DB which was not the same as the Pega hosting DB. This was caused by incomplete handling of a null classname in the platform check, and has been resolved.

SR-A1803 · Issue 206925

Support added for Virtual Private Databases (VPDs)

Resolved in Pega Version 7.2

An enhancement has been added to allow an application developer to pass a customizable set of property values to an Oracle or Enterprise DB when a connection is established to the DB to run SQL statements. The primary use case for this feature is the ability for Pega DBMS that support Virtual Private Databases (VPDs) to implement unbreakable object-level security for all data access from a Pega application by defining on class tables that reference this information.

SR-A5100 · Issue 212794

Support added for Virtual Private Databases (VPDs)

Resolved in Pega Version 7.2

An enhancement has been added to allow an application developer to pass a customizable set of property values to an Oracle or Enterprise DB when a connection is established to the DB to run SQL statements. The primary use case for this feature is the ability for Pega DBMS that support Virtual Private Databases (VPDs) to implement unbreakable object-level security for all data access from a Pega application by defining on class tables that reference this information.

SR-A1999 · Issue 214345

"Edit in Excel" not supported in Microsoft Internet Explorer 11+

Resolved in Pega Version 7.2

Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.

SR-A1999 · Issue 214460

"Edit in Excel" not supported in Microsoft Internet Explorer 11+

Resolved in Pega Version 7.2

Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.

SR-A2378 · Issue 214518

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A2378 · Issue 210254

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A2378 · Issue 211007

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A4717 · Issue 214606

Added handling for Microsoft Internet Explorer double-submit on enter

Resolved in Pega Version 7.2

When using the Microsoft Internet Explorer browser, List view was throwing an error on submission by pressing 'enter keyboard key' while working as expected when using the submit button. This was traced to an Microsoft Internet Explorer issue that fires the 'onunload' event twice if it is redirected from within the event handler, and has been resolved by applying a flag-based condition check while executing to prevent the second firing.

SR-A5424 · Issue 213337

Check added to handle mismatched property names given in referred page

Resolved in Pega Version 7.2

If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.

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