Service dotNet form - Completing the Request tab

Field

Description

Enter the external name of the request header.

Enter a text description.

Select how the system maps the request header values to the clipboard:

• Clipboard — The system maps the data value to the scalar property specified by the Map To Key field.
• Username — The system authenticates the user name using the value provided. This is useful for client applications that do not support HTTP Basic Authentication.
• Password — The system authenticates the password using the value provided. This is useful for client applications that do not support HTTP Basic Authentication.

If more choices appear, they each identify a custom function rule in a MapTo library. Review the function rule to determine what it does.

If the Map To value is Clipboard, enter the property name to which the data is to be mapped. Use the form Param.name parameter name to set a parameter value on the parameter page of the service activity.

If the Map To value is Username or Password, leave this field blank.

Field

Description

Select the XML schema data type of the parameter value. Select any primitive data type in the W3C XML Schema standard. See How to complete data mapping for SOAP and dotNet services for details on data types.

Select XML Page for a complex parameter, to cause the system to create a clipboard page containing the elements of a portion of the XML document. (Complete the XML Page tab in this case.)

Enter the external name of the parameter, with no spaces.

Enter a text description.

Select how the system maps the request parameter values to the clipboard. The choice you make for this field depends on what you select for Data Type:

• Clipboard — The system maps the data value to the scalar property specified by the Map To key value. If you selected XML Page as the Data Type, this is the only choice.
• Username — The system authenticates the user name using the value provided.
• Password — The system authenticates the password using the value provided.
• XML ParseRule — Indicates that the incoming data value from the sending application is a stream of XML that can be parsed using the data mappings specified in a Parse XML rule.
• HTML PostData — Indicates that the incoming data value from the sending application is a stream of data from an HTML form that contains property key/value pairs in POST format.

Identify a destination for the Map To selection:

• If the Map To value is Clipboard, enter the property name to which the data is to be mapped. (If the Data Type is XML Page, enter the name of a Page mode property.)
• If the Map To value is XML Parse Rule, enter the Namespace name (second key part) and the Element Name name — third key part — of the appropriate Parse XML rule. Separate the Namespace from the Element Name with a space. That is, use the syntax "NamespaceName ElementName" and not "NamespaceName.ElementName." The system uses the page class of this service rule as the first key part of the parse rule.

• To maintain backward compatibility for service rules created in releases before PRPC Version 5.2, you can specify a data mapping with only a Namespace value. In that case, the system determines the Element Name key at run time from the root element of the incoming XML document. However, this mapping works only if the Parser Type of the Parse XML rule is set to DOM and validation is not enabled. As a best practice, specify both the Namespace Name and the Element Name of the rule.

• If the Map To value is HTML PostData, leave this field blank. The name/value pairs in the string are mapped to the parameter page of the service activity rather than the primary page.
• If the Map To value is Username, Password, or HTML PostData, leave this field blank.