Configuring a Connector Service Request to Invoke an Orchestration or a Notification

Note: With Tools release 9.2.4.3, you do not have to create a connector service request to invoke "local" orchestrations or notifications. You can add your own orchestrations and notifications directly as step in the calling orchestration.However, a connector is required to invoke an orchestration or a notification on an AIS Server on another EnterpriseOne system in a multisite operation. (Release 9.2.4.3)

1. Click the Connectors icon on the Orchestrator Studio Home page.

2. On the Connectors side panel, click the New drop-down menu and select Orchestration.

3. Create and name the connector service request as described in Creating a Component.

4. On the Connectors design page, select a connection to the AIS server from the Orchestration drop-down list.

   After you select a connection, the Orchestrator Studio displays the URL of the AIS server next to the Orchestration field.

5. In the Orchestration/Notification drop-down list, select the appropriate option depending on whether you want to invoke an orchestration or a notification.

   Depending on your selection, a pop-up dialog box is displayed with a list of orchestrations or notifications.

6. Search for and select the orchestration or notification that you want to invoke.

   You can click the Search button to reopen the pop-up dialog box that displays a list of notifications or orchestrations. The Search dialog box lists the available orchestrations or notifications, depending on your selection in the previous step. The list is categorized by these UDO status: Personal, Pending Approval, Reserved, and Shared.

   Any inputs defined in the called orchestration or notification appear in the Orchestration Inputs column, with variable names automatically generated in the adjacent Input column.

7. Enable the Use Object for Input toggle if you want to map the entire object as an input to the orchestration connector. This action enables you to pass arrays to an orchestration that is called through a connector. (Release 9.2.4.3)

8. Enable the Fire and Forget toggle if you want the orchestration to execute without waiting for a response. If Fire and Forget is enabled, the called orchestration will run asynchronously. The Output grid is hidden because the REST service response is not processed.

   (Release 9.2.4.4) The Number of Threads option is displayed when you enable the Fire and Forget toggle. This option enables you to select the number of threads for an iterated step for an iterated step.

   For example, if an array of 1,000 records is sent as the iterator for a fire and forget orchestration and the value in the Number of Threads option is 10, only 10 orchestrations will be executed at one time. The remaining orchestrations will be in a waiting state until one of the 10 threads is available again. Similarly, the remaining set of orchestrations are processed until all of them are completed.

9. In the Input column, you can modify the variable names as you want or map a default value by entering a value (without the ${} notation).

10. For an orchestration connector, use the Output grid to specify the values you want to be returned from the called orchestration.

    For a version 3 orchestrations, the Orchestration Connector outputs are used for variables only. Enter a variable for the value to make it an orchestration input, which gives you the option to map the value to a subsequent step in an calling orchestration.

    You have to populate the Variable Name column and that name will be available for mapping in the orchestration.