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

Additional top level abstract class with Create SOAP Integration



User upgraded their DEV environment from Pega 7.1.8 to 7.2. After the upgrade, they are finding a change in behavior w.r.t the class structure created in PRPC 7.2 after importing a WSDL file. In Pega 7.1.8 when they go to "Designer studio>Integration>Connectors>Create SOAP Integration", to consume a WSDL and generate appropriate classes, connect-soap rules etc, the SOAP Integration wizard generates one top level class (For example: Org1-Soap1-Work-Test) and all corresponding classes as per WSDL definition beneath this top level class.  In Pega 7.2 the SOAP Integration wizard doesn't run using the same WSDL file, two top level classes are created (For example: Org1-Soap1-Work-Test and Org1-Soap1-Work-Test-). The additional top level class has dash (-) appended to it but has the same name as the other top level class (created without dash). In Pega 7.1.8 just one top level class (without a dash appended to it) is created on importing the WSDL.

In Pega 7.2 both the top level classes (For example: Org1-Soap1-Work-Test and Org1-Soap1-Work-Test-) have the same class definitions beneath them as per WSDL definition. The connector and data mapping rules are created within the class having a dash appended to it (For example: Org1-Soap1-Work-Test-) where-as in Pega 718 the connector and data mapping rules are created within the class without the dash (For example: Org1-Soap1-Work-Test).

Error Messages

Not Applicable

Steps to Reproduce

  1. Import a WSDL file in Pega 7.2 and in Pega 718 using Create SOAP Integration wizard.
  2. In Pega 7.2 we can see two two level classes being created (one having a dash appended to it and other without a dash appended to its name).
  3. In Pega 718 we can see only one top level class being created that doesn't have a dash appended to it.

Root Cause

A defect in Pegasystems’ code or rules is identified as the root cause of this issue in Pega 7.2.


Apply HFix-26386 to resolve the issue.

Published March 16, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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