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.
SR-B65908 · Issue 314482
Serialization fixed for multi-node pre-activity dataflow
Resolved in Pega Version 7.3.1
Attempting to trigger a dataflow run with pre-activity configured to run on every node was failing with a serialization exception. This was caused by the task being distributed across the cluster having a member variable that was not serializable; this has been fixed.
SR-B56530 · Issue 312902
Reworked destination assumptions for child dataflows
Resolved in Pega Version 7.3.1
When activating a Real time data flow run containing a Stream dataset as input which was then output to two child dataflows containing different event strategies, an IllegalArgumentException error appeared. This was traced to the pzDataFlowContainsEventStrategy activity assuming that the last shape had "Destination" in the ID. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but will default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.
SR-B66844 · Issue 317078
RD modified to allow more than 1000 entries in a filter value
Resolved in Pega Version 7.3.1
A DB exception was thrown when a report definition was run with more than 1000 entries in a filter value. This was due to the DB limitation, and the system has been updated to pass the "pyReportParamPageName" parameter to RD to avoid the exception.
SR-B50800 · Issue 311591
Fixed sorting of nested repeat grid with one child-grid column
Resolved in Pega Version 7.3.1
A Null Pointer Exception was generated when performing a sort in a nested Repeat grid when the child-grid had one column and sort was enabled. The sort worked as expected when there was more than one row in the embedded/child grid. This was due to a loss of the content div after the first sort, and has been corrected.
SR-B41245 · Issue 315783
Query Generation layer Null Pointer Exception handling added to support Sybase and other DBs
Resolved in Pega Version 7.3.1
A Null Pointer Exception was generated while running a report that connected to a table on a Sybase database which had a nvarchar column. In order to handle Sybase requests or other unexpected DBs used with Pega, the DB_Type.GENERIC in mapDatabaseType in DatabaseUtils.java class has been updated to handle any Null Pointer Exceptions that might be encountered in the Query Generation layer.
SR-B42679 · Issue 303776
Report definition popup display overwrites single window
Resolved in Pega Version 7.3.1
Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.
SR-B42679 · Issue 305263
Report definition popup display overwrites single window
Resolved in Pega Version 7.3.1
Activating the autogenerated "Report Definition" action on a UI control multiple times opened each report in its own popup window, but interacting with a report which was not the most recently opened caused incorrect content to be displayed: report 1 opened and displayed as expected, but after opening report 2, focusing on report 1 again caused the report 2 content to show in that window. This was due to the implementation of the Report Definition action not specifying a window identifier when it opened a popup, causing a new popup to open for each report but using the same content for all existing windows. To resolve this, the JS has been modified to pass a target param and overwrite a single popup window with the contents of the requested report. This makes the behavior consistent with previous versions of Pega.