SR-B15749 · Issue 289752
Enhancement for capturing SOAP envelope of Async SOAP Service
Resolved in Pega Version 7.3
The SOAP service request envelope has been available for service activity using the 'pxRequestor.pxReqSOAPEnvelope' property in synchronous execution mode, but that envelope was not available in asynchronous execution mode due to asynchronous execution using a different requestor. In order to support this information in asynch mode, an enhancement has been added to allow the service activity to perform a look-up for the pxReqSOAPEnvelopeinformation in the parameter page.
SR-B159 · Issue 272693
Wizard will halt if rules to be deleted are in locked rulesets
Resolved in Pega Version 7.3
After running the Connector and Metadata wizard using a WSDL metadata file and then locking the current ruleset version, running the same wizard again using the same WSDL file and selecting OverWrite in the OtherConflicts step caused the rules in the locked first ruleset to also be overwritten. To prevent this, the CompleteRuleGeneration activity will cause the wizard to halt if it encounters rules that would be deleted that are in locked rulesets. When the ruleset(s) are unlocked, the wizard will continue.
SR-B16337 · Issue 287224
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B16337 · Issue 288963
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B16825 · Issue 292599
WordMacroManagerDot updated for 64-bit compatibility
Resolved in Pega Version 7.3
The WordMacroManagerDot macro has been updated for Word-64-Bit environment compatibility.
SR-B16921 · Issue 287323
BIX documentation for Obj-Save help updated
Resolved in Pega Version 7.3
The BIX Extracts help file has been updated to clarify which properties are or are not updated when using Obj-save, explicitly noting that pxUpdateDateTime is not updated in the database when the Obj-save method is invoked and that a data transform should be applied to cause an update. Obj-save does update pxCommitDateTime.
SR-B17037 · Issue 289405
Handling added for SP initiated logins
Resolved in Pega Version 7.3
Attempting a Service Provider (SP) initiated login request caused the error "The Response did not contain any Authentication Statement that matched the Subject Confirmation criteria" to appear. This was due to the code used to identify whether the flow is IDP initiated or SP initiated SSO not having the handling for encrypted assertions. The system has now been updated to look for the relay state in the DB: if an entry is present then the SSO flow will be SP initiated, otherwise it will be IDP initiated.
SR-B17080 · Issue 289244
saveAllOrNone API more robust for multi-tenant shared BIX
Resolved in Pega Version 7.3
Intermittent errors appeared when two BIX command line extraction scripts were running in parallel when both used BixUser_Tenant as the operator. This was traced to the saveAllOrNone API, which was not equipped to prevent other nodes from writing data into the DB while the current thread was also trying to write that same data to the DB. Further diagnostics are required to formulate a solution to this intermittent error, but the API has been made more robust: the system will not throw an IllegalStateException when the DB exception is DuplicateKeyException.
SR-B17338 · Issue 294731
Corrected and improved calculations for multiple page Business Calendars
Resolved in Pega Version 7.3
The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.
SR-B17403 · Issue 297717
Resolved concurrent mod exceptions when using getValueInType API
Resolved in Pega Version 7.3
Concurrent modification exceptions were observed in the logs when the getValueInType API was called to fetch property values from multiple threads. To resolve this, the getValueInType API has been made thread safe by synchronizing its access.