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.
SR-B65837 · Issue 317187
Handling added for blanks when copying parameter pages
Resolved in Pega Version 7.3.1
After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.
SR-B67171 · Issue 317155
Handling added for blanks when copying parameter pages
Resolved in Pega Version 7.3.1
After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.
SR-B41213 · Issue 310710
Ruleset sorting/comparison updated for DB2/zOS EBCIDIC
Resolved in Pega Version 7.3.1
After upgrade to a DB2/zOS split schema, accessing the UI Gallery landing page (DS -> User Interface -> UI Gallery) did not show any results. It was possible to search for rules and open them without issue, and altering the query to use a wildcard for pzRuleSetListHash found the rules as expected. The problem was traced to EBCIDIC character set ordering being different than ASCII & UTF-x based char ordering. UTF-based character encodings hold that A is greater than 9 when being used for comparison, but in an EBCIDIC sort, A's value is less than 0. Due to IBM DB2 on zOS using EBCIDIC ordering for character string comparisons (e.g. greater than, less than), the pzRuleSetVersionMinorPatch column that contains the String for the Minor and Patch versions was not ordering the needed rulesets as expected. To resolve this, the code has been updated to rarely use character string comparisons (greater than) in DB queries for greater compatibility.
SR-B43868 · Issue 310711
Ruleset sorting/comparison updated for DB2/zOS EBCIDIC
Resolved in Pega Version 7.3.1
After upgrade to a DB2/zOS split schema, accessing the UI Gallery landing page (DS -> User Interface -> UI Gallery) did not show any results. It was possible to search for rules and open them without issue, and altering the query to use a wildcard for pzRuleSetListHash found the rules as expected. The problem was traced to EBCIDIC character set ordering being different than ASCII & UTF-x based char ordering. UTF-based character encodings hold that A is greater than 9 when being used for comparison, but in an EBCIDIC sort, A's value is less than 0. Due to IBM DB2 on zOS using EBCIDIC ordering for character string comparisons (e.g. greater than, less than), the pzRuleSetVersionMinorPatch column that contains the String for the Minor and Patch versions was not ordering the needed rulesets as expected. To resolve this, the code has been updated to rarely use character string comparisons (greater than) in DB queries for greater compatibility.
SR-B50727 · Issue 310068
Repaired checking for forward links on cached references
Resolved in Pega Version 7.3.1
After upgrade, a Null Pointer Exception was thrown when updating a case due to missing handling for forward links on cached references. To correct this, a check has been added when trying to regenerate missing back links to verify whether the forward link is valid or not; if it is valid, only then will the system try to regenerate the back link. Otherwise it will pass back the old link itself.