Service File form
Completing the Service tab

Field

Description

Select the class for the primary page that is to be used in all activities run with this Service File rule. The system creates an empty page of this class each time it executes a row of the Parse Segments array on the Request tab.

Optional. You can identify a model to be applied to the primary page each time the primary page is created.

Enter a name for the primary page.

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

Complete these fields to describe the processing mode.

Select one of the following:

• Execute synchronously — to have this service run to completion after a request is received. This is the default.
• Execute asynchronously (queue for execution)— to place a service request in a queue, for background processing. If a Final Activity is selected on the Request tab, the activity will be queued and executed as the last request of the last batch. When the queued service request is executed, the execution is performed with the authorization profile of the service.

Optional. If you selected Execute asynchronously as the Execution Mode, identify a service request processor that defines the queue and its queuing and dequeueing characteristics. See About Service Request Processor data instances.

Enter to specify the maximum size of the file to be processed asynchronously when the Processing Method option is set to file at a time on the Method tab.

Enter the number of requests to be processed. These requests are batched together and executed sequentially by the thread responsible for processing the queue item.

After you save this form, click to see a graphic representation of the components of the service. See About the Integration viewer.