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-B71308 · Issue 319409

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.

SR-B71308 · Issue 320806

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.

SR-B65658 · Issue 314838

New case creation save errors resolved

Resolved in Pega Version 7.3.1

When a new case was created in an application built on top of Pega Pharmacovigilance, data propagation was throwing an error on the screen. Creation worked as expected when the pyDefault case type rule was opened and saved. This issue was traced to the case type rule not being created properly as part of the application creation, and has been resolved by updating pzDoesClassRequireBasicSave to not include Rule-Obj-CaseType in rows so the new application process performs a standard Save instead of an Obj-Save. In addition, it was not possible to save associated rules for selected data type when data type was in a locked ruleset and the pxUpdateRecord API was not setting pyrulename correctly when doing a save-as of the rule; these issues have also been corrected.

SR-B66453 · Issue 315656

New case creation save errors resolved

Resolved in Pega Version 7.3.1

When a new case was created in an application built on top of Pega Pharmacovigilance, data propagation was throwing an error on the screen. Creation worked as expected when the pyDefault case type rule was opened and saved. This issue was traced to the case type rule not being created properly as part of the application creation, and has been resolved by updating pzDoesClassRequireBasicSave to not include Rule-Obj-CaseType in rows so the new application process performs a standard Save instead of an Obj-Save. In addition, it was not possible to save associated rules for selected data type when data type was in a locked ruleset and the pxUpdateRecord API was not setting pyrulename correctly when doing a save-as of the rule; these issues have also been corrected.

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-B74689 · Issue 323378

Marketing data flow run made more robust

Resolved in Pega Version 7.3.1

After upgrade, it was observed that Pega Marketing Campaigns were failing if there were no customers in the Audience configured on the Campaign, generating the error message "The run failed, because it exceeds the maximum number of failed records, which is currently set to 0". The cause of this was executing a distributed data flow with a database as primary source on an empty table, leading the run to fail as a table without any partition was considered in the handling. The database dataset has now been updated to differentiate the case when there's no partition available from the case when there's a single partition for every record, ensuring the DB data set now returns 'all' records when there is no partition key defined, and the data flow handles the no values for partitions in a more robust way.

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