Connect dotNet rules – Completing the Faults tab
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.
Important: Connect dotNet rules are no longer being actively developed, and are
being considered for deprecation in upcoming releases. Using Connect dotNet rules does not
follow Pega development best practices. Use Connect SOAP rules instead. For more
information, see About Connect SOAP rules.
For information about these faults, including a list of SOAP fault codes, see the SOAP specification at http://www.w3.org/TR/soap/.
Note: To capture exceptions triggered by the Connect-dotNet method,
configure the error handling fields on the Service tab.
SOAP envelope content
| Field | Description |
|---|---|
| Target property | Select 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 the Open icon  next to
this field to open the New property form. |
Fault message fields
| Field | Description |
|---|---|
| Fault code property | Optional. Select or enter the name of a Single Value property
to store the value of the fault code returned in the response. |
| Reason property | Optional. Select or enter the name of a Single Value 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 property | Optional. Select or enter the name of a Single Value 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. |