Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

New field missing issue related to Connect-SOAP

SA-11277

Summary


 
In one of the recent enhancement requirement user has updated WSDL and XSD files which has two new fields added.
In one of the Web-Service Request these two fields are passed and user is able to trace these new fields in the tracer. User verifies the same in Pega logs and also by adding Show-Page(after the Connect-SOAP method in the Activity). External users were able to receive the requests but without the two newly added fields.
 

Error Messages


 
Not Applicable.
 

Steps to Reproduce


 
1. Update the fields in the screen.
2. Click on Submit.
 

Root Cause


 
Issue is related to pyAxisClass of the SOAP connector rules referring to older versions. The pyAxisClass plays important role in SOAP Connector.

In PRPC 5.4 and before, PRPC used the wsdl2java capabilities of Axis 1.2.1 to generate a binding stub class to encapsulate the SOAP client interaction. This class is set at the time the connector is generated from the wizard, and is instantiated using reflection at runtime to execute the connector.

Importing the updated WSDL/XSD in new ruleset only will not override the previous rules.

 

Resolution



The Accelerator does not overwrite existing rules, so user must use the Cleanup function to delete the old rules, first. Cleanup functionality removes only those rules which are generated by the  wizard.
          
For more details, refer http://pdn.pega.com/node/1051 
Suggest Edit

Published August 11, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us