dotNet Connector Form – Completing the Advanced tab

Use the Advanced tab to change which version of Axis or SOAP the system is to use, to modify the schema definitions for XML Page data mappings generated by the Connector and Metadata wizard, or to associate a compensating action with the connector.

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.

Client properties

The Pega Platform dotNet connector architecture uses an Axis client to make the SOAP call and process the SOAP response. Use the fields in this section to specify settings for the Axis client.

Field Description

Field	Description
Axis Version	Select either `1.2.1` or `Axis2`. If you used the Connector and Metadata wizard to generate this connector, it is set to 1.2.1. In such a case, do not change this value to `Axis2` unless you need to: send SOAP with attachments specify SOAP 1.2, or modify the data mapping of an XML object, as described in More about SOAP connectors. Note: If you change the Axis version to `Axis2`, also change the data type of any XML objects from `XMLPage` to `XML Literal`.
SOAP Version	Specify which version of the SOAP specification is implemented by the Web service this connector communicates with. If you used the Connector and Metadata wizard to generate this connector, it is set to `SOAP 1.1`.

Axis Version

Select either 1.2.1 or Axis2. If you used the Connector and Metadata wizard to generate this connector, it is set to 1.2.1. In such a case, do not change this value to Axis2 unless you need to:

send SOAP with attachments
specify SOAP 1.2, or
modify the data mapping of an XML object, as described in More about SOAP connectors.

Note: If you change the Axis version to Axis2, also change the data type of any XML objects from XMLPage to

XML
                    Literal

SOAP Version Specify which version of the SOAP specification is implemented by the Web service this connector communicates with. If you used the Connector and Metadata wizard to generate this connector, it is set to SOAP 1.1.

Web services (ws-*) configuration

If your application requires a secure SOAP connection, you can enable Web Services Security (WSS) below.

Field	Description
Enable ws-security	Select this option to enable Web Services Security on this connector.
Enable ws-addressing	Select this option to include routing data within the SOAP header.
Security profile	Specify the WSS profile to use with this connection. See About WS Security Profile data instances.

Schema definitions

If you used the Connector and Metadata wizard to generate the dotNet connector rule and the WSDL file of the Web service contains a schema description with complex types, the Schema definitions section specifies the data transforms that define the schema of the incoming and outgoing XML objects. Typically, this indicates that the SOAP operation style is document-literal.

On the Request and Response tabs, the Data Type of the XML objects described by the data transforms specified on this tab is set to XML Page.

If this rule was not created by using the Connector and Metadata wizard, leave this section blank. You cannot configure a mapping for a XML object except by using the Connector and Metadata wizard.
If this rule was created using the Connector and Metadata wizard, make changes carefully. You can update the Page name and the Data transform fields. Do not change the Class name field.

Field	Description
Page key	Identify the clipboard page that contains the data values to be mapped to or from the XML object.
Class name	Specify the class of that page.
Data transform	Specify a data transform to use as the schema description of the XML object. In most cases, the generated data transform specified in this field is appropriate. However, the generated data transforms list every property in the class; you may not want to map a value for every property in the class. If you do not need all the properties, create a new data transform that specifies the properties to map in the order they are to be mapped. Then select that data transform in this field.

Compensating action

Note: Use the optional Compensating action and Compensating action data sections to associate a compensating action with a work item when the connector rule succeeds. For more information, see Using Compensating Actions, on the Pega Community.

Field	Description
Work page name	Optional. Specify the name the page that holds the work item. Typically this is `pyWorkPage`.
Action label	Optional. Enter a string that describes the purpose of the compensating action. For example, "Cancels Flight Reservation." PublicAPI methods can use this label to identify this compensating action within a Java step of an activity.
Action activity class	Optional. Identify the Applies To class — first key part — of the activity that performs the compensating action.
Action activity name	Optional. Identify the Activity Name — second key part — of the activity that performs the compensating action.
Compensating action data	Optional. Use this section to store information about the current state of the work item as parameter-value pairs when the purpose of running the compensating action activity is to restore the work item to the state it is in directly after the connector rule runs. In the none field press the Down Arrow key and select the name of a parameter used by the compensating action activity. Then, in the value field, select the property that is to be the source of the parameter value.