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-B67316 · Issue 317299

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.

SR-B50434 · Issue 317985

Struts mapping updated to compensate for behavior change

Resolved in Pega Version 7.3.1

The expectation was that after system startup in a zOS multi-servant environment where each servant has two JVMs which are running at any given point of time, launching SMA after adding a primary node should cause the servant node to show up in the edit page and upon submit the servant nodes should be listed under the primary node under left navigation links. However, after upgrade new nodes added to the cluster in the SMA were not visible due to behavior change between struts releases. This has been addressed by modifying the mapping in struts.xml and tuning some JSP syntax issues in AddNodeIDs.jsp.

SR-B56125 · Issue 317516

WebLogic deployment guides updated for dual user setup

Resolved in Pega Version 7.3.1

The WebLogic deployment guides have been updated to specify that dual user setup requires the addition of the jdbc/AdminPegaRULES datasource with entries added to prconfig.xml. This is similar to the method used for the Tomcat app server.

SR-B56437 · Issue 317515

Schema handling enhancement added for Alternate database option in list view

Resolved in Pega Version 7.3.1

A List view configured to use the Alternate Database setting generated an error when the report was run, due to the schema used by the Reporting Database (defined in the Sandbox-Work database table rule) having a different name than the default Pega database. The main Pega database schema is PEGA721, and the Reporting Database in this case was a schema called PEGA721REP in the same database, causing the table to not be found. As support for the reporting database being located on an alternate database with user specified schema is not available, an enhancement has been added to provide a prconfig that takes the schema for an alternate database and provides the support for ReportDefinition to use it.

SR-B77148 · Issue 325930

Handling added for importing PostgreSQL database Application Bundles

Resolved in Pega Version 7.3.1

Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.

SR-B77536 · Issue 326544

Check added to keep "::" in imports between PostgreSQL systems

Resolved in Pega Version 7.3.1

Application Bundle imports were failing on db2/MSSQL systems due to syntax differences, generating the message "FATAL ERROR: Encountered an issue applying DDL". Postgres database view definitions include ":: and character varying", but other databases do not require those characters. To ensure compatibility when importing the archives to non-Postgres databases from the Postgres instance, "character varying" will be removed through removeTypeCastingFromPostgreSQL in databaseschemaUtils. It will not be removed for import to another Postgres system.

SR-B65434 · Issue 334578

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B74189 · Issue 334576

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B76468 · Issue 336009

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B76989 · Issue 327639

Informational text added to "No suitable driver" error message

Resolved in Pega Version 7.4

After configuring Pega to connect to an external database using Data-Admin-DB-Name with a JDBC URL configuration that had the appropriate jar for the driver in the application server classpath, unexpected behaviors were seen. The first time the Test Connectivity button was clicked, a "No suitable driver found" error appeared. The second click ran the test as expected. This confusion was related to an undocumented enhancement: because adding a new database JDBC driver in Pega may require configuration to get the driver class loaded to the classpath, the 'No suitable driver' exception was enhanced with the configuration required to get the JDBC driver loaded at the next restart. In order to avoid confusion, informational text will now appear as part of the "No suitable driver" error message to explain this.

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