SR-A6108 · Issue 217715
Node validation check added to SOAP services
Resolved in Pega Version 7.2
Code has been added to SOAP Services to check whether the node is usable or not before processing the request.
SR-A5671 · Issue 215223
Node validation check added to SOAP services
Resolved in Pega Version 7.2
Code has been added to SOAP Services to check whether the node is usable or not before processing the request.
INC-157196 · Issue 629298
Deprecated service package features now require authentication
Resolved in Pega Version 8.5.3
Authentication has been added to deprecated features of the standard service package to improve security. If issues are encountered during product migration, please use the Deployment Manager.
INC-150610 · Issue 627428
Argument number exception handled for SERVICES-PAL log configuration
Resolved in Pega Version 8.5.3
An issue with being unable to configure the SERVICES-PAL log file has been resolved by adding handling for an unlogged "wrong number of arguments" exception.
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-A6949 · Issue 216721
Revised class display properties to avoid looping
Resolved in Pega Version 7.2
When running Service Wizard using the setting 'Service Purpose for Rule-InsProd-Product', the browser would become unresponsive while attempting to display the properties. This was traced to a displayed properties loop caused by creating service from the service wizard and specifying a class name which has siblings and a parent class containing a page of the child class. To avoid this condition, a check has been added to handle cases where if a page class is descendant of the class which contains the page, the properties of that page will not be displayed.
SR-A6223 · Issue 214939
Resolved WSDL SOAP exception when using target namespace
Resolved in Pega Version 7.2
When adding a well-defined XML ParseRule as a Request Header, saving and checking in the rule caused the Deployment results link to generate the error "Caught exception while creating WSDL for service package: : com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException Header message is included with method namespace instead of targetnamespace" This was an error in the code handling a target namespace for Request Headers (configured on the Service Soap -> Requests tab), and has been fixed.
INC-157194 · Issue 620153
CheckRevisionDeployment requires authentication
Resolved in Pega Version 8.5.3
Authentication has been added to the CheckRevisionDeployment service package.
INC-155813 · Issue 629506
SAML SSO redirects to correct URL when application and authentication aliases match
Resolved in Pega Version 8.5.3
Whenever there was a match in the authentication service alias and the application alias, the application alias was replaced with empty after logoff instead of making the authentication service alias empty. For example, given an authentication service with the alias XYZ ("login with XYZ" alias option) and an application name XYZMyOps, the application alias was being changed from XYZMyOps to appMyOps after logoff. As a result, a blue screen error resulted when clicking on button "login with XYZ" again because it redirected to appMyOps, which didn't exist. This has been resolved by removing authservicealias and modifying AuthServiceAliasHelper.adjustPathIfAuthServiceAliasPresent() to change the method for calculating the pathinfo to string tokenizing
SR-A8788 · Issue 217912
Updated reference mapping to resolve JMS error
Resolved in Pega Version 7.2
If the Request Message Type was set to Map on the Service Tab, adding message data on the request tab to any connect-jms or service JMS rule failed to save and generated the error "Message Key value must be specified for map messages". Setting the same information on the Message Properties area worked as expected. This occurred due to improper mapping of the property references, and the mapping has been corrected.