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-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() .
SR-B72326 · Issue 325267
EmailListener handling updated for addressee errors
Resolved in Pega Version 7.3.1
When messages are handled by the EmailListener with more than one recipient (more than one TO: header and even sometimes more than one CC: header), the EmailListener activity will create a (sub-)case for each of these recipients, based on their email addresses from the TO: or CC: list. If an error was generated by one of the recipient email addresses in one of the groups (TO: or CC:) being invalid, only the invalid address was returned to the EmailListener for further processing. This meant the other addresses in the same group were ignored and no (sub-)case created for them. To address this issue, the handling has been changed: If an exception occurs while processing a recipient's name, the system will iterate through the Message to get recipients one by one. If the Address is valid it will be added to the list, and if it's invalid then extractEmailAddress API will be used to attempt to extract a valid email address and add it. If the extraction did not obtain a valid email address it will be logged and ignored. Please note that all this processing will be done if FailOnAddressException DSS is set to false (the existing behavior).
SR-B73213 · Issue 322353
CMIS-GetPropertiesResponse property mapping fixed
Resolved in Pega Version 7.3.1
The CMIS properties' data was improperly mapped to a "pyProperty" Page List property which was not part of the CMIS-GetPropertiesResponse data model, rather than mapping the data into the proper "pyProperty" Page List properties in the CMIS-GetRepositoriesResponse data model such as pyPropertyBoolean, pyPropertyInteger. This was caused by a defect in the Pega engine's CMISConnector module caused by changes made to simplify and consolidate the "map Properties" logic. The CMISConnector module has been repaired so that it correctly derives data type when giving a pointer to a PropertyDataObject:
SR-B57228 · Issue 325976
Timer exit error fixed for STS SOAP
Resolved in Pega Version 7.3.1
If STS was enabled for a SOAP Connector and if a valid STS token was already available, hundreds of error messages about attempting to stop the timer were logged. This was traced to a step order error which started the timer and then exited before stopping it, and the missing step has been added.
SR-B65469 · Issue 330983
Connect-SQL documentation updated to clarify no milliseconds in Oracle TIMESTAMP
Resolved in Pega Version 7.3.1
The documentation for Connect-SQL rules has been updated to clarify that the datetime hint in rdb-save will not store millisecond precision in the TIMESTAMP column type of an Oracle database.
SR-D24527 · Issue 504402
Improved requestor cleanup
Resolved in Pega Version 8.2.5
Batch- and Browser-type Requestors were building up over time in both the Admin Studio and in the PegaRULES log and not removed until the system was restarted. This has been resolved by adding two extra cleanupRequestor calls to the Email Listener implementation.
SR-D29034 · Issue 500681
Added support for JSON mapping of deep nested pagelist objects
Resolved in Pega Version 8.2.5
An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.
SR-D33003 · Issue 511230
Queue Batch activity correctly passes chlld process access group
Resolved in Pega Version 8.2.5
When users attempted to create an index using the schema tools landing page, an error displayed in the table history stating "Create index failed". Investigation showed that this happened when a user was authenticated without the PegaRULES:DatabaseAdministrator role and then switched to an Access Group with the PegaRULES:DatabaseAdministrator role. The issue was traced to the activity that launched the batch requestor missing the parameter pzUseCurrentAccessGroupForChild due to the Queue Batch activity only passing the default access group authorization. This has been resolved by adding code to pass the additional authorization which will allow users to create an index in this scenario.