Understanding Orchestrations

Creating an orchestration in the Orchestrator Studio involves:

• Naming the orchestration and specifying the input format for the orchestration.

• Adding inputs to the orchestration.

  The inputs define the data that is passed to the orchestration from a device, third-party application, custom program, or Cloud service. For example, an orchestration that is designed to receive input from a sensor, will receive an input that may include an ID that identifies the sensor, and data such as temperature, date, or any other data you want to capture from the sensor.

• Adding steps to the orchestration.

  Each step is a component of the orchestration. A step can be a service request, rule, cross reference, or white list. At a minimum, an orchestration requires a service request step, which provides the actions or the instructions to perform a particular task in EnterpriseOne.

• Configuring transformations.

  You use transformations to map orchestration inputs to inputs that are defined in each orchestration step, such as inputs in a rule, cross reference, white list, service request component, and system variables.

Important: Remember that when you are ready to "request to publish" an orchestration, you need to make sure that you also request to publish all the components that are associated with the orchestration. The request to publish the components ensures that an administrator saves all the required components to the proper directory on the AIS Server for processing by the Orchestrator. If a component is missing, the orchestration process will end in an error.