Understanding Service Requests

A service request provides the instructions that enable an orchestration to carry out a particular task. You can create the following types of service requests in the Orchestrator Studio:

• Form Request

  A form request contains the instructions for the orchestration to perform a particular business transaction in EnterpriseOne.

• Data Request

  Use a data request in an orchestration to query and retrieve values from an EnterpriseOne table or business view. You can also configure a data request to perform an aggregation on data to return aggregate amounts.

• Message

  Use a message request if you want an orchestration to send a message to an external email address (requires an SMTP server) or to EnterpriseOne users through the EnterpriseOne Work Center.

• Connector

  Use a connector request to invoke an orchestration, a notification, a REST service or a database. A connector can invoke an orchestration on an AIS Server on another EnterpriseOne system in a multisite operation.

  Also, you can configure a connector to use FTP or a REST call to transfer report output or other files to an external server.

  Note: With Tools release 9.2.4.3, you do not have to create a connector service request to invoke "local" orchestrations or notifications. You can invoke your own orchestrations and notifications directly as a step in the calling orchestration.

• Custom Request

  Use custom Java or Groovy to execute a custom process. With Tools release 9.2.4.3, you can add a custom request to call a business function.

• Watchlist

  Use a Watchlist service request to use the information from Watchlists, such as critical or warning states, threshold levels, and number of records, within an orchestration.

• Report

  Use a report request to invoke a batch version of a report in EnterpriseOne.

Before you create a service request, you must first identify the EnterpriseOne task or business process that you want the service request to perform. See Identifying the Service Request Information for the Orchestration for more information.