Understanding Service Requests

At a minimum, an orchestration requires an orchestration component with inputs and a service request component to run. The service request provides the instructions that the Orchestrator uses to invoke and perform a particular task in EnterpriseOne. The service request provides the instructions on how to process the data from the orchestration inputs.

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 the Identifying the Service Request Information for the Orchestration section in this guide for more information.

Use the Service Request design page in the Orchestrator Studio to define a service request, which involves:

• Specifying the EnterpriseOne buttons, fields, columns, menu items, and so forth that are involved in performing a task in EnterpriseOne.

  In the Service Request design page, you can search on an EnterpriseOne application form and view all of the controls and fields for a form.

• Determining the order of execution in which the controls and fields are used to perform the desired task in EnterpriseOne.

Note: You can also use custom Java to execute a custom process or to route data into another database. See Creating Custom Java for Orchestrations.