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

Fault Data Classes & Parse XML Rule not created

SA-17059

Summary



Faults Data Classes and Parse XML Rule are not being created through the Connector Wizard.


Error Messages



NA


Steps to Reproduce



1. Place WSDL and XSD on a web server.
2. Go to Designer Studio -> Integration -> Connectors -> Create SOAP Integration.
3. Select option “Upload WSDL via URL” and enter the URL of the WSDL.
4. Select all operations.
5. Set the desired Name and Parent Class.
6. Click Create.
7. Check for Fault Data Classes.


Root Cause



An issue in the custom application code or rules .
 

Resolution



PRPC doesn't create fault data classes and properties when it referenced from wsdl, it is as per design. But there is a local change with which you can manually configure the SOAP Connector to map to the SOAP Fault data in 6.x version.

Steps for configuring SOAP Fault Detail mapping for a generated SOAP connector rule.
 

After executing the Connector and Metadata wizard to generate the SOAP connector configuration, run it again to generate the parse rules and supporting classes and properties for mapping the SOAP fault data. This time, select Generate Data Mapping Rules as the Purpose, and XSD as the Metadata Type. Use the same base class that was used for the connector generation.

Load the XSD document that contains the SOAP fault element declaration.

Select the SOAP fault element from the list of element declarations.
 

Generate classes, properties, and XML parse rules.
 

Open the Parse XML instance from the results tab.

The parse rule contains all the data mappings for the SOAP fault detail element.
 
 

In order to use the parse rule in the SOAP connector, Save As into the generated SOAP connector class.

You will get a validation error because the property references of the Applies To class are no longer valid. To fix this, double-click on the root node of the tree view.
 

Add a property reference in the Context Page field. The property should be a Page property of the original class of the parse rule. Since this property will not exist, you can create it on-the-fly by clicking the Open button to the right of to the Context Page input box.

Create the embedded page property with the correct page class.

Save the parse rule after changing the Context Page value on the root node.

Open the Connect SOAP rule that was generated in the first run of the Connector and Metadata wizard. On the Faults tab, add Single Value (type Text) property references to all fields that need to be mapped. In later versions of PRPC, these fields are filled in automatically by the accelerator using existing property references from @baseclass.

In the activity that calls the SOAP connector, add a transition to the Connect-SOAP step. The transition should jump to an error handling step when an exception is thrown. The error handling step should call the Apply-Parse-XML method to map the SOAP fault detail element content using the Parse XML rule created in the previous steps. The step should have a precondition that checks whether the Single Value property that holds the SOAP Fault Detail XML has a non-blank value.
 

Suggest Edit

Published January 31, 2016 - 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