Service HTTP form
Completing the Service tab

Field

Description

Specify the Applies To class of the service activity.

Optional. Identify a model in the class identified in Page Class. If you do so, the system applies the model immediately after it creates the page.

Enter a page name for the class specified in the Page Class field. This page is the top-level clipboard page that Process Commander uses as the primary page when running the activity called by this HTTP service. The property values can 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 object in a flow, or perform a flow action on an existing work object. 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 an unnamed page to the activity.

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

Parameter values from the incoming request override values set on this tab.

When services in the service package are stateful, select this option to have the system end the requestor after the activity ends and the response is sent.

This option applies only when the Processing Mode field on the service package data instance is set to Stateful. If the services are stateless, this value in this field is ignored.

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 for asynchronous execution, 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 more information, see Pega Developer Network articles PRKB-25029 How asynchronous service processing works and PRKB-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 Response 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.