SR-B75335 · Issue 322757
Improved DSN message handling for Email Listener
Resolved in Pega Version 7.3.1
Email service was failing with a Gmail DSN message exception indicating Inbound data mapping had failed. To resolve this, logic has been added to Email Listener to ensure it properly processes the Gmail DSNs, In addition, error handling has been improved.
SR-B47240 · Issue 305940
File Listener enhanced to support source mask with two asterisks
Resolved in Pega Version 7.3.1
File Listener was not retrieving all files if the source name mask had more than one asterisk. Code has been added to support a maximum of two asterisks: one in the file name and one for extension, ex: *.RDM*.xml
SR-B71077 · Issue 326659
IDP Encrypted connections working on SAML
Resolved in Pega Version 7.3.1
IDP initiated SAML 2.0 was not working, and generated the error "Unable to process the SAML WebSSO request : Missing Relaystate information in IDP Response". Authentication worked fine with unencrypted SAML token. This schema validation failure happened because encrypted attributes were previously being ignored by Pega due to an issue in the underlying openSAML library. To resolve this, a custom PegaSAMLValidator has been inserted to validate the assertion and honor encrypted attributes.
SR-B45960 · Issue 303751
Request & Response logs include POST method submits
Resolved in Pega Version 7.3.1
When using the POST method to send a request, request & response data was not showing up the in DEBUG logs of the Connect-REST execution. This has been corrected, and request & response data is now being added to DEBUG logs in Connect-REST execution.
SR-B49398 · Issue 306482
Request & Response logs include POST method submits
Resolved in Pega Version 7.3.1
When using the POST method to send a request, request & response data was not showing up the in DEBUG logs of the Connect-REST execution. This has been corrected, and request & response data is now being added to DEBUG logs in Connect-REST execution.
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.