Back Forward dotNet Connector Form
Completing the Advanced tab

 About Connect dotNet rules

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 Accelerator), or to associate a compensating action with the connector.

Client Properties

The Process Commander 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
Axis Version

SmartPrompt is available. 5.4 PROJ-315 Select either 1.2.1 or Axis2. If you used the Accelerator 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.

NoteIf you change the Axis version to Axis2, also change the data type of any XML objects from XMLPage to XML Literal.
SOAP Version

SmartPrompt is available.Specify which version of the SOAP specification is implemented by the Web service this connector communicates with. If you used the Accelerator to generate this connector, it is set to SOAP 1.1. If you specify SOAP 1.2, set the Axis version to Axis2.

Web Service Security

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

Field

Description
Enable WS Security

Select this option to enable Web Services Security on this connector. BUG-3072
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

C-500 If you used the Connector and Metadata accelerator to generate the dotNET connector rule and the WSDL file of the Web service contains a schema description with complex types, this section of the Advanced tab specifies the model rules 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 models specified on this tab is set to XML Page.

Field

Description
Page Key

Identify the clipboard page that contains the data values to be mapped to or from the XML object.
Class Name

SmartPrompt is available.Specify the class of that page.
Model Name

SmartPrompt is available.Specify a model rule to use as the schema description of the XML object.

In most cases, the generated model specified in this field is appropriate. However, the generated models 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 model that specifies the properties to map in the order they are to be mapped. Then select that model rule in this field.

Compensating Action

Advanced featureOptional. Use the Compensating Action and Compensating Action Data section of this tab to associate a compensating action with a work object when the connector rule succeeds. For more information, see PDNUsing Compensating Actions, a document on the Integration section of the Pega Developer Network.

Field

Description
Work Page Name

C-766 R-11238 Optional. Specify the name the page that holds the work object. 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

SmartPrompt Optional. Identify the Applies to class — first key part — of the activity that performs the compensating action.
Action Activity Name

SmartPrompt 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 object as parameter-value pairs when the purpose of running the compensating action activity is to restore the work object to the state it is in directly after the connector rule runs.

Click the  none   button and enter 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.

Up About dotNet Connector Rules