Understanding Orchestrations

Creating an orchestration in the Orchestrator Studio involves:

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

  The input format can be JDE Standard, Oracle Cloud IoT, or Generic.

• Adding inputs to the orchestration.

  The inputs define the data passed to the orchestration from a device, third-party application, custom program, or Cloud service. For example, if designed to receive input from a sensor, the input may include an ID that identifies the sensor and other data that the orchestration will receive, 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 service request, rule, cross reference, or white list. At a minimum, an orchestration requires only 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 defined in each orchestration step, such as inputs in a rule, cross reference, white list, or service request component.

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 components associated with the orchestration. This enables an administrator to save all 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 error.