Adding Steps to an Orchestration

Each component (service request, rule, cross reference, white list) that you add to an orchestration is an orchestration step. It is recommended that you create the component that you want to add to an orchestration before you add it as an orchestration step.

You can use the Refresh Cache button on the Run Orchestrations page in the Orchestrator Studio 9.2.4 to access the objects (such as service requests, orchestrations, and so on) those created or edited outside of your current session. For the objects that were shared while the session is open, you will have to close it and sign in again to the EnterpriseOne application to access the shared objects.

The following image shows an orchestration that contains multiple rule, cross reference, and service request steps:

Each row in the Orchestration Steps grid represents a step in the orchestration. The grid displays the following information about each step:

• Type. Displays the component type: Rule, Service Request, Cross Reference, or White List.

• Action. Use this column to define which subsequent step is invoked based on the criteria in the preceding rule. See Defining the Actions Between a Rule and Dependent Components for details.

• Iterate Over. Use this column to pass a data set retrieved from a form request or data request to a subsequent orchestration step. See Passing a Data Set to a Subsequent Orchestration Step for more information.

• Name. Displays the name of the component.

Use the "Insert Step Before" and "Insert Step After" buttons to add a step before or after another step in the orchestration. For example, if you determine that you need to add a white list to an existing orchestration, you can insert the white list as an initial step before the other steps.