Service SOAP form
Completing the Service tab

Field

Description

Specify the Applies To class of the service activity.

Optional. You can identify a data transform in the class identified in Page Class. If you do, the system applies the data transform immediately after it creates the page.

Enter a page name for the class specified in the Page Class field. This is the top-level clipboard page that PRPC uses as the primary page by the activity being called through the SOAP service. The activity property values may be written to or read from this page.

Enter any page name, or accept the default value MyServicePage. (This page name has no special characteristics.)

Specify the name of the activity that provides the processing for this service rule. For example, the activity can start a work item in a flow, or perform a flow action on an existing work item. This activity is known as the service activity.

The system uses the value you enter in the Page Class field as the Applies To key part of the activity. The system creates a page with the name provided in the Page Name field and passes it to the activity as the primary page. If the Page Name field is blank, the system passes the activity an unnamed page.

You can use the  Params   button to provide constant values for the parameters of the service activity, in case not all values are being mapped from the inbound service request data.

For example, if a parameter value is the same for every service request, you can set that parameter's value here rather than requiring a client application to supply it in each request. If a service activity starts a flow for a work item and the organization is always the same, you can specify the name of the organization on this tab.

If a parameter value is set here and also mapped from inbound request data, the inbound request data value overrides the value set on this tab.

Specify the style (RPC or Document) and the use (literal or encoded) of the SOAP messaging format for this service. PRPC supports the following bindings:

• Document/literal
  The preferred style when all request and response data is contained in XML literal parameters. Use when all data is mapped using XML mapping rules.
• RPC/encoded
  This style is not WS-I compliant. This style is deprecated, but provided for backward compatibility.
  
• RPC/literal
  The preferred style when either the request or response data contains simple parameter values. Use when mapping data to or from the clipboard.

Select to apply the W3C Message Transmission Optimization Mechanism formatting to binary data in SOAP messages. Selected by default as the recommended format.

Select to have the system end this requestor session when the activity completes.

This checkbox affects only stateful processing. This checkbox is ignored when the Processing Mode on the service package data instance is set to Stateless.

Leave cleared in most cases. Select to indicate that each use of this service is not to count as a service invocation under the terms of your license agreement. See Working with the License Compliance facility.

Select one of the following options:

• Execute synchronously — select this when you want the service to run the request immediately.
• Execute asynchronously — select this when you want the service to queue the request, return the Queue Item ID to the external application, and end the service call while the processing starts. Choose this option only if a Service Request Processor data instance (Data-Admin-RequestProcessor-Service class) exists with a key that matches the Service Package key part of this service rule.

When the queued service request executes, the execution is performed with the authorization profile of the service.

For instructions and an example, see PDN articles 25029 How asynchronous service processing works and 25030 How to create a service that processes requests asynchronously.

If you select Execute asynchronously in the Execution Mode field or you configure a Queue When condition on the Faults tab, select the name of the service request processor (instance of Data-Admin-RequestProcessor-Service). The list in this field displays only the request processors that are defined for the same service package as this service rule.

After you save this form, click to view a tree of the components that comprise the service package. See About the Integration viewer.