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-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-B2093 · Issue 277296
Corrected page passivation for parameterized data pages
Resolved in Pega Version 7.3
A null-pointer exception error was generated when performing findPage() on a parameterized Data page after the page/thread was passivated and restored. This was traced to a situation where a page with meta data was not correctly saved while passivating due to a failed condition check on last update time, and has been resolved with changes to the EditDataPageHandler to update the access time whenever page is loaded from findDataPage() method.
SR-B269 · Issue 284289
Multinode SOAP made more robust for rule resolution
Resolved in Pega Version 7.3
After updating an application rule on a multinode environment, SOAP service stopped working and generated the error "Failed to open Rule-Parse-XML record". In this case, the application index was written to the DB after updating in-memory variables, leading rule resolution to search in the DB with the wrong application hash. To avoid this, the system will now write the DB index first then update in-memory variables.
SR-B30305 · Issue 288126
Fixed double encoding from Authorize URL scope
Resolved in Pega Version 7.3
If a scope had multiple values in Authentication Profile, then Pega Platform inserted '+' between them in run-time. This was due to the scope parameter value being double-encoded for the Authorize URL, and has been fixed.
SR-B30485 · Issue 287734
Tenant ID check added to Ruleset Wizard for MT
Resolved in Pega Version 7.3
Attempting to deleting a ruleset in a multi-tenant environment using the Ruleset Wizard resulted in the error message 'Getting records from the database' and the application would hang. This was due to a missing tenant ID in the SQL statement, and a check has been added to the query generation to ensure the prepared values for "pzTenantID" are included.
SR-B30935 · Issue 289403
CMIS files stored according to application config
Resolved in Pega Version 7.3
Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.
SR-B31094 · Issue 288810
Removed uppercase shift from GetColumnInfo and ValidateDBTable
Resolved in Pega Version 7.3
The Connector wizard was failing against external Sybase DBs due to the schema name being sent uppercase. This has been resolved by updating the activities GetColumnInfo and ValidateDBTable to remove the code that converts the names to uppercase.