SR-B69447 · Issue 317927
Attachment links with commas open in Google Chrome
Resolved in Pega Version 7.3.1
After upgrade, attachment links containing commas were not opening as expected in Google Chrome. A check has been added to ensure attachments open properly.
SR-B69447 · Issue 317951
Attachment links with commas open in Google Chrome
Resolved in Pega Version 7.3.1
After upgrade, attachment links containing commas were not opening as expected in Google Chrome. A check has been added to ensure attachments open properly.
SR-B39427 · Issue 309252
Export to Excel fixed for DT >50 records
Resolved in Pega Version 7.3.1
After upgrade, clicking the Export button on a decision table with more than 50 records was not sending the data to Excel as expected. This was traced to a Null Pointer Exception generated by encountering an unneeded step page, and the erroneous step has been removed.
SR-B53476 · Issue 313103
JBoss installation config documentation corrected
Resolved in Pega Version 7.3.1
Deploying JBoss in single-user configuration and starting Pega was failing with the error "Services with missing/unavailable dependencies". This was caused by an incorrect configuration, and was traced to an error in the documentation for JBoss that reverted the installation instructions to an earlier version. The JBoss documentation has been corrected to reflect that configuring the adminPegaRULES datasource is not optional. If dual user config is not needed, the same configuration as PegaRULES datasource should be used.
SR-B54273 · Issue 310624
Resolved requestor hang and JVM crash
Resolved in Pega Version 7.3.1
Some application nodes were hanging or intermittently going down one by one after operators became stuck in the building session authorization stage. This was traced to an infinite loop situation in AuthorizationContextmanagerImpl combined with excessive firings of the operations in ContextUtils that expand the Rule App clipboard page and remove unwanted properties. This has been resolved with code improvements that include ensuring the 'while' loop will cycle a maximum of 10 times before exiting.
SR-B54273 · Issue 310713
Resolved requestor hang and JVM crash
Resolved in Pega Version 7.3.1
Some application nodes were hanging or intermittently going down one by one after operators became stuck in the building session authorization stage. This was traced to an infinite loop situation in AuthorizationContextmanagerImpl combined with excessive firings of the operations in ContextUtils that expand the Rule App clipboard page and remove unwanted properties. This has been resolved with code improvements that include ensuring the 'while' loop will cycle a maximum of 10 times before exiting.
SR-B49166 · Issue 309799
Removed unneeded timestamp on DADN rule connection test
Resolved in Pega Version 7.3.1
Test connections were failing for a Data-Admin-DB-Name rule when the connection type was "Use Configuration in Preferences". This failure was caused by "tmp" being appended to the DB name for the connection test, causing the DB name to be different in the prconfig file. Because a timestamp is not required, this has been fixed by not appending it to the DADN name.
SR-B66439 · Issue 315454
prpcServiceUtils component updated to contain Linux Ant files
Resolved in Pega Version 7.3.1
The Ant file was missing in the prpcServiceUtils published in the below article : https://pdn.pega.com/exchange/components/remote-configuration-command-line-tool-prpcserviceutils The issue in the gradle script which caused the Ant file to be missed while creating zip file has been fixed.
SR-B45232 · Issue 306137
Serialized passivation exception fixed
Resolved in Pega Version 7.3.1
A passivation exception was being logged due to a temporary page not being properly cleared after use with serialized properties. The ActivityStatusExceptionHandler activity has been changed to remove the temp page at the end.
SR-B64471 · Issue 315890
PegaCALL Null Pointer Exception fixed
Resolved in Pega Version 7.3.1
After a successful PegaCALL login was initiated and events were populated to the desktop, setting the phone status to Ready then caused some sites to experience sporadic errors that resulted in CTI login problems and events not reaching the desktop. When the issue occurred, it affected an entire instance at a time but cleared on its own after several hours. This was due to missing null handling in the code used for event delivery, and has been fixed.