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-B49349 · Issue 311189

Logging simplified to improve performance issues related to PEGA0069 alerts

Resolved in Pega Version 7.3.1

In order to improve system performance in installations where many PEGA0069 alerts are logged, no data will be output for the "lastInput" field of the alerts. "Last input" field is typically populated with useful information that helps end user to analyze where the issues lie, but the field does not hold value in the context of PEGA0069 alerts.

SR-B53224 · Issue 310551

Performance improvements for metadata queries with Oracle12c

Resolved in Pega Version 7.3.1

Performance issues with metadata queries were traced to a bug in Oracle 12c which caused the query to be executed multiple times instead of checking for the presence of table from tableInfo map. To improve performance, the logic in DatabaseImpl.getColumnsForUndefinedTable() has been modified to ensure the query executions will not happen with out looking at the tableInfo from map.

SR-B56921 · Issue 312557

Performance improvements for metadata queries with Oracle12c

Resolved in Pega Version 7.3.1

Performance issues with metadata queries were traced to a bug in Oracle 12c which caused the query to be executed multiple times instead of checking for the presence of table from tableInfo map. To improve performance, the logic in DatabaseImpl.getColumnsForUndefinedTable() has been modified to ensure the query executions will not happen with out looking at the tableInfo from map.

SR-B54147 · Issue 310771

Improved MinConnections handling and performance

Resolved in Pega Version 7.3.1

The MinConnections setting in prconfig was not being considered by the connection manager, and some performance issues were seen due to the system closing and reopening a connection when a duplicate key exception was encountered. This has been corrected by modifying the connection manager to correctly consider the MinConnection value provided, and by improving error handling so that time is not spent making a new connection after an exception is encountered. In addition, DB trace events will be generated for closeConnection events.

SR-B54147 · Issue 310646

Improved MinConnections handling and performance

Resolved in Pega Version 7.3.1

The MinConnections setting in prconfig was not being considered by the connection manager, and some performance issues were seen due to the system closing and reopening a connection when a duplicate key exception was encountered. This has been corrected by modifying the connection manager to correctly consider the MinConnection value provided, and by improving error handling so that time is not spent making a new connection after an exception is encountered. In addition, DB trace events will be generated for closeConnection events.

SR-B42729 · Issue 309850

Prgateway exception logging enhanced

Resolved in Pega Version 7.3.1

Stack trace logging has been enhanced for Prgateway exceptions.

SR-B42729 · Issue 309869

Prgateway exception logging enhanced

Resolved in Pega Version 7.3.1

Stack trace logging has been enhanced for Prgateway exceptions.

SR-B43915 · Issue 308088

Fixed Product Rule min and maxVersion value reset

Resolved in Pega Version 7.3.1

Values of mMinVersion and mMaxVersion were not being reset to null values after the "rulesets to include section" was processed in the product rule. This affected the "classes to include" section of the addSpecInstances() method as well, and happened only in special case when 'Rule-RuleSet-Version' class was included in the classes to include section. This resulted in the condition propagating from one section to another instead of clear initialization. This has been fixed by resetting the minVersion and maxVersion values after processing rulesets to include.

SR-B67118 · Issue 316911

Password obfuscated in serviceutils INFO message

Resolved in Pega Version 7.3.1

When running prpcServiceUtils.sh, the password from the property pega.rest.proxy.password was visible in an INFO statement due to the export with params listing all values including the password. The code has been revised so passwords will be obfuscated while logging in prpcServiceUtils.properties and not shown as plain text values.

SR-B56367 · Issue 313698

Query updated for Oracle DDL generation

Resolved in Pega Version 7.3.1

When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.

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