SR-A7508 · Issue 218320
Resolved Connect REST Accelerator JSON response error
Resolved in Pega Version 7.2
When there was a property present in the @baseclass and the JSON object to create the data model has the JSON key, an exception was thrown due to mode conflict created when the Rest response contained properties which were already present in @baseclass. This has been resolved by modifying the code to rename the property if it already exists, and additional updates were made to the ServiceHelper class to improve JSON performance.
SR-A9136 · Issue 221836
Added loop avoidance when Service SOAP wizard encounters parent class with sub-pages
Resolved in Pega Version 7.2
The Service SOAP wizard was presenting properties as Input Parameters that appeared to have a repeating reference not actually present in the Data Class specified to process. The initial reported issue showed the wizard presenting Input Parameters such as "RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1.RequestPage1...." increasing in length on each line. This was caused by a loop created while creating the service from the Service Wizard and specifying a class name which has siblings and a parent class containing pages of the child class. To avoid this, the system will break the loop if the parent contains the page property of the child class.
SR-A9959 · Issue 220317
Removed screen capture control authentication requirement from portal launch
Resolved in Pega Version 7.2
A portal containing references to the UserOCXReferences html fragment was trying to install all of the cab files included in the portal when launched, requiring admin credentials to proceed further. Per design, the referred cab is not required in the portal and is required only in the documentation wizard to provide screen shots. It has now been removed from the UserOCXReferences rule.
SR-A8595 · Issue 218942
Security updated for SAML Rule keystores
Resolved in Pega Version 7.2
Password encryption has been updated for the Keystores records used by SAML Rule forms for signing and decryption in the auth service rule data.
SR-A10162 · Issue 220915
Data-Admin-Security-Keystore caching added
Resolved in Pega Version 7.2
Previously, the query to pr_data_admin would retrieve and read DATA-ADMIN-SECURITY-KEYSTORE on each connect-soap call. In order to improve scalability and performance, the data instances of type keystore will be cached as part of the rule instance cache.
SR-A7518 · Issue 219402
EJB Connector wizard fetches fully qualified class names for compile
Resolved in Pega Version 7.2
When using a JNDI Server referencing remote EJBs, configuring Connect EJB through the wizard resulted in compilation errors. This was due to incorrect wrapper class generation, and the generation has been updated to use fully qualified class names.
SR-A5714 · Issue 213993
Connect-SOAP SSL configuration merge corrected
Resolved in Pega Version 7.2
An error in the merge function caused an issue with configuring SSL certificates at the connector level if the keystore and truststore were configured in the connector. This has been corrected.
SR-A12614 · Issue 224476
Added JDBC connectivity handling to MQ listener
Resolved in Pega Version 7.2
The MQ listener was going inactive and throwing the error 'Timed out borrowing service requestor from requestor pool for service package?, leading to the indication that all the requestors in the pool were active and no free requestor was available. This was traced to incorrect recovery from a JDBC connectivity issue to the database: the requestor pool would lose the requestor and cause inconsistent pool size. In order to resolve this, handling has been added to ensure the requestor pool and requestor state are consistent irrespective of any JDBC connection issue.
SR-A11696 · Issue 224612
Namespaces considered while constructing WSDL type maps
Resolved in Pega Version 7.2
Previous versions that had repeating complex elements used as references ended up with "type2" appended to those elements when the WSDL was generated after upgrade. This format was put in place to avoid namespace collisions when duplicate names are used for the same complex types in a schema with different targetnamespace. However, even though the WSDL was semantically correct, it caused backward compatibility when generating stubs out of WSDL and created the need to regenerate the stubs. To resolve this, changes have been made to XMLTreeViewUtils.addDocElementDeclaration() to consider namespaces while constructing the type definition map.
SR-A13436 · Issue 225301
Security update for Apache commons-collection
Resolved in Pega Version 7.2
The Apache commons-collections library has been updated to v3.2.2 to close a vulnerability that permitted code execution when deserializing objects involving a specially constructed chain of classes.