Skip to main content

SAP Connector form - Completing the Faults tab

Suggest edit
Updated on April 6, 2022

The Faults tab is optional, but as a best practice use this tab to map any SOAP faults returned by the Web service. That way you can include an error-handling step in the connector activity and have the activity respond appropriately if the connector receives a SOAP fault instead of the response message it expects. To capture exceptions triggered by the Connect-SAP method, configure the error handling fields on the Service tab first.

Note: This tab is displayed for the SOAP connector type only.
Important: Connect SAP rules are no longer being actively developed, and are being considered for deprecation in upcoming releases. Using Connect SAP rules does not follow Pega development best practices. Use Connect SOAP rules instead. For more information, see Connect SOAP rules.

SOAP envelope content

FieldDescription
Target propertySelect or enter the name of a single-value text property to store the entire contents of the SOAP envelope that contains the fault message. To create a new property, enter its name and click Open to open the New property form.

Fault message fields

FieldDescription
Fault code propertyOptional. Select or enter the name of a Single Value text property to store the value of the fault code returned in the response.
Reason propertyOptional. Select or enter the name of a Single Value text property to store the value of the fault reason string returned in the response. The fault reason string holds an explanation of the fault code.
Detail propertyOptional. Select or enter the name of a Single Value text property to store the value of the fault detail string returned in the response. The fault detail string holds application-specific information about the fault.
  • Previous topic SAP Connector form - Completing the Response tab
  • Next topic SAP Connector form - Completing the Advanced tab
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us