Complete the Service tab to identify the activity that this Service SAP rule calls. See More about Service Packages.
|Primary page class||Specify the Applies To class of the service activity.|
|Data transform||Optional. To identify a data transform that the system applies after creating the page, select a data transform in the class that you chose in the Primary page class field.|
|Page name|| Enter a page name for the class specified in the Primary page
class field. This is the top-level clipboard page that the Pega Platform uses as the primary page by the activity being called
through the SAP 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.)
|Activity name||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 Primary 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 Parameters section 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.
|Style and use|| Specify the style (RPC or Document) and the use (literal or encoded) of the
SOAP messaging format for this service. The Pega Platform
supports the following bindings:|
|Enable MTOM||Select to apply the W3C Message Transmission Optimization Mechanism formatting to binary data in SOAP messages. Selected by default as the recommended format.|
|End requestor when done||Select to have the system end this requestor session when the activity
This check box affects only stateful processing. This check box is
ignored when the Processing Mode on the service package data instance is set to
|Method is read-only||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.|
|Execution mode|| There are four options, two each for synchronous and asynchronous (queue for
execution) modes. Each pair has an option for using Request/Response, and a "one
way" option for sending the service call and only receiving the HTTP Response status
code (i.e., 2xx). |
Synchronous - Select one of these options when you want the service to run the request immediately:
Asynchronous - Select one of these options when you want the service to queue the request. Choose one of these options 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 a queued service request executes the execution is performed with the authorization profile of the service.
|Request processor||If you select Execute asynchronously in the
Execution mode field or you configure a |
|Enable service SLA with fallback activity||Optional. This option is displayed for asynchronous execution modes. When
selected, you can configure a fallback activity for a time-out. For example, when
the service activity is not finished after a configured amount of time and the
maximum number of violations has occurred, the fallback activity is called. No
further requests are attempted until the retry interval has passed. If the next
attempt is successful, normal processing is resumed. |
Using a service SLA ensures that a logical response is made in a timely manner. Configure the fallback activity on the Methods tab. If a fallback activity is not configured, the default response is sent back.
|Maximum duration for service activity (milliseconds)||This option is displayed when you select Enable service SLA with fallback activity. Enter the amount of time, in milliseconds, after which the service activity is considered to have failed. The default is 500 milliseconds.|
|Maximum consecutive violations||This option is displayed when you select Enable service SLA with fallback activity. Enter the number of SLA violations that must occur before the fallback activity is called. The default is 3.|
|Retry interval (seconds)||This option is displayed when you select Enable service SLA with fallback activity. Enter the amount of time, in seconds, to wait before attempted to process the service activity. The default is 10 seconds.|
|Fallback activity name||This option is displayed when you select Enable service SLA with fallback activity. Select a fallback activity for the response when the SLA fails. For example, the fallback activity can display a default offer to an ATM customer instead an offer based on the particular customer's data. If you do not select a fallback activity, the default response is sent back.|
|Parameters||If a parameter value is the same for every service request, you can set that parameter's value rather than requiring a client application to supply it in each request.|