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 return 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 EnterpriseOne users through the EnterpriseOne Work Center.

• Connector

  Use a connector request to invoke an orchestration, notification, REST service or database. For a connector to an orchestration, a connector can invoke a local orchestration or an orchestration on another AIS Server, such as an AIS Server on another EnterpriseOne system in a multisite operation. (Connectors to a notification and database are available starting with Orchestrator Studio 6.0.x.)

  Starting with Orchestrator Studio 6.1.0, you can configure a connector to use FTP or a REST call to transfer report output or other files to an external server.

• Custom

  Use custom Java or Groovy to execute a custom process.

• Watchlist (Orchestrator Studio 6.0.x)

  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 (Orchestrator Studio 6.1.0)

  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.