SR-B68812 · Issue 310862
Activities updated to use class name to access out-of-the-box templates
Resolved in Pega Version 7.3.1
The out-of-the-box templates were not visible in the implementation layer due to the shipped templates having been created in a horizontal layer tied to a horizontal class. To correct this, the pzGetAllMappedFieldsFromTemplate and pzSetInitialSourceInfo activities have been updated to allow for loading mapping data by getting a selected template class name before calling the load template data page.
SR-B69935 · Issue 317991
Pega fetch assignments API updated to call py functions for Robot Manager use
Resolved in Pega Version 7.3.1
The Pega API assignment activity pzGetAssignmentDetailsInternal in ruleset Pega-API:07-10-31 makes a call on line 16 to pzNotifyRobotWorkBasketContainer. This is a platform defect that should have been replaced with pyNotifyRobotWorkBasketContainer. pyNotifyRobotWorkBasketContainer is an extension point activity that is blank in the core platform, but overridden when the Robot Manager app layer is added to the stack. The correct py calls are now present.
SR-B4034 · Issue 306173
Fixed data mismatch from parallel schema migration
Resolved in Pega Version 7.3.1
When a queue method in a loop inside an activity was used to create separate work objects and in parallel migrate work object data from one DB schema to another, running that queue method more than once caused the Source table columns and destination columns to have mis-matched datetime property values after migration. This was an issue where the same DateFormat object was being used by two batch requestors. To resolve this, whenever the requestor object is destroyed, the date format object used for database operations will be made null.
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.