SR-B65652 · Issue 315008
Corrected datasource used to update pr_extract_time
Resolved in Pega Version 7.3.1
If the "use last updated time as start" filter was used for a class which mapped to a table in an external database, a database permission error was thrown when trying to access the pr_log table in the PegaRULES database. This has been corrected by updating pr_extract_time using the connection from Pega-Extract-Time instead of the extract class.
SR-B65744 · Issue 315671
Repaired use of custom case ID search
Resolved in Pega Version 7.3.1
After upgrade, custom search criteria for case IDs generated an error when pulling data from the database. This was traced to a change that removed CommonTLP as a fallback, and that default has been restored.
SR-B66204 · Issue 316885
XSS sanitizing added to clientID field
Resolved in Pega Version 7.3.1
During the time of construction of a ServiceRequest in the engine , the clientID field will be sanitized with the StringUtils.crossScriptFiltering API to avoid XSS attacks.
SR-B69133 · Issue 317298
Carriage returns stripped from ExtractIdentifier value
Resolved in Pega Version 7.3.1
If the pzInskey value in the extract rule xml file had extra carriage returns, the pxExtractIdentifier was generated with extra carriage returns in the value. Downstream processing was failing because of these extra carriage returns. To correct this, all carriage returns will be stripped from the pxExtractIdentifier value.
SR-B69409 · Issue 317548
CLOB type handling enhanced in Marketing
Resolved in Pega Version 7.3.1
Pega Marketing uses the out-of-the-box DSM activity pxRunDDFWithProgressPage for triggering Data flow runtime. After upgrade in DB2 environments, the DF execution completed but the activity returned a failure. It was found that if a CLOB column is present in the filter of a NativeSQL object invoked from an activity, the status had an error message even though functionality was fine. To ensure consistent behavior, CLOB has been added to supported data types so the severity of the exception can be changed so as to not show error message in activity's status.
SR-B70051 · Issue 324690
Enhanced Dnode Pulse logging
Resolved in Pega Version 7.3.1
Enhanced pulse logging has been added for DNode errors
SR-B75443 · Issue 324603
Property filter execution updated for better backward chaining
Resolved in Pega Version 7.3.1
in cases where the strategy is cyclically called and backward chaining is enabled, the declarative network was looking to load the value of a property which did not exist, leading to an error. The evaluateWhen function in the proposition filter rule execution has been modified to reset backward chaining.
SR-B76502 · Issue 325128
BIX extract exceptions and missing XML fixed
Resolved in Pega Version 7.3.1
StringIndexOutOfBoundsException and ClassCastException were being generated during BIX extract and some tags were missing in the extracted XML. This has been fixed.
SR-B50950 · Issue 308958
Connect-SOAP passivation tuned
Resolved in Pega Version 7.3.1
Connect-SOAP implementation uses requestor instance to cache STSConfigContext and Axis2 ServiceClient objects; these are not serialize-able and were leading to requestor passivation failure. As part of the fix, these objects will be de-referenced from the requestor page and instead the system will use a requestor scoped data page to cache STSConfigContext and Axis2 ServiceClient objects.
SR-B55660 · Issue 316375
Removed "SHA1" hard coding from SAMLRedirectBindingHandler
Resolved in Pega Version 7.3.1
SAML logout failure was seen after using SHA256 signature encoding on an IDP that does not support SOAP. Previously,"SHA1" was hard coded to be used for verification of certificate during logout in the case of HTTP-Redirect Binding; this hard coding has now been removed from SAMLRedirectBindingHandler.verify() .