C Creating Orchestrations with Orchestrator Studio 5.1.0

Note:

This appendix describes how to use Orchestrator Studio 5.1.0 that was available starting with EnterpriseOne Tools 9.2.1.4.

To use Orchestrator Studio 7.0.x.0, the latest version available with EnterpriseOne Tools 9.2.3, see:

This appendix contains the following topics:

C.1 Understanding the Orchestrator Studio and Orchestrations

The Orchestrator Studio is a web-based application for creating orchestrations and the components that comprise an orchestration. The Orchestrator uses these components to process a single orchestration instance on the AIS Server.

Use the Orchestrator Studio to create the following components:

  • Orchestrations. An orchestration is the master component that provides a unique name for an orchestration process. The orchestration is where you define the inputs for the orchestration, the expected incoming data. The orchestration also includes orchestration steps, which are invocations to the other components described in this list. When the Orchestrator invokes an orchestration, it processes the steps defined in the orchestration to enable the transfer of data from a third-party to EnterpriseOne.

  • Service Requests. A service request can contain instructions to perform a business transaction or query data in EnterpriseOne, send a message to EnterpriseOne users or external users, execute a custom process such as routing data into another database, or invoke another orchestration or REST service through a "connector" service request.

  • Rules. A set of conditions that the input to the orchestration is evaluated against to produce a true or false state. With rules, a false outcome or true outcome can invoke further orchestration steps. You can also nest rules, in which an outcome of one rule can invoke a different rule, to produce complex evaluations. You can also use custom Java to define rules.

  • Cross References. A set of data relationships that map third-party values to EnterpriseOne values. For example, a device's serial number can be cross-referenced to a JD Edwards EnterpriseOne Equipment Number for use in service requests.

  • White Lists. A white list contains an inclusive list of values permitted in the orchestration and terminates the orchestration process if the data is not recognized.

A simple orchestration requires at a minimum an orchestration and a service request to run. When you save an orchestration in the Orchestrator Studio, the name of orchestration is used to define an endpoint on the AIS Server. The endpoint URL is:

http://<server>:<port>/jderest/orchestrator/<orchestrationname>

To invoke an orchestration, third-party applications or devices use a post operation to this url, where <orchestrationname> is the name of your orchestration.

Figure C-1 shows the drop-down list of steps that you can add to an orchestration. Each step in an orchestration is simply a reference to a cross reference, rule, service request, or white list component.

Figure C-1 Orchestration Steps in the Orchestrator Studio

Description of Figure C-1 follows
Description of ''Figure C-1 Orchestration Steps in the Orchestrator Studio''

C.1.1 Reusable Orchestration Components

Orchestration components are reusable. You can include the same component, such as a rule or cross reference, in more than one orchestration. If a component is used as a step in more than one orchestration, you should evaluate how it is used in the other orchestrations before modifying it.

To determine if a component is used by other orchestrations, select the component and then click the "i" button to display a pop-up window that lists the orchestrations where the component is used.

When in doubt, use the "Save As" button to create a new component from an existing one. This enables you to give it a new name and modify it as necessary, and eliminates the risk of breaking other orchestrations where the component is used.

C.1.2 Orchestrations as User Defined Objects

All orchestration components created in the Orchestrator Studio are stored as user defined objects (UDOs) in EnterpriseOne. The Orchestrator Studio includes UDO features for creating, sharing, and modifying orchestration components as UDOs. See User Defined Object (UDO) Features for a description of the UDO features.

C.2 Accessing the Orchestrator Studio

The Orchestrator Studio is a web application that runs in a web browser. Ask your system administrator for the URL to the Orchestrator Studio.

Important:

Before users can access the Orchestrator Studio, an administrator must set up security to authorize access to the Orchestrator Studio design pages and determine the actions Orchestrator Studio users can perform. See Chapter 11, "Administering the Orchestrator Studio and Orchestrations" for more information.

To access the Orchestrator Studio:

  1. In a web browser, enter the URL to the Orchestrator Studio:

    http://<adf_server>:<port>/OrchestratorStudio/faces/index.jsf

  2. On the Orchestrator Studio Sign In screen, enter your EnterpriseOne User credentials, environment, and role.

    Note:

    It is highly recommended that you enter an EnterpriseOne environment used for testing, not a production environment.
  3. Click the Login button.

In the Orchestrator Studio, click the drop-down menu in the upper-right corner to view the path to the AIS Server. The drop-down menu also provides a link to log out of the Orchestrator Studio.

C.3 Navigating the Orchestrator Studio

The orchestration component icons on the Orchestrator Studio Home page take you to the design pages for creating and modifying each orchestration component. You can click the Home icon at the top left of the Home page to display a side panel, which provides another way to access the orchestration component design pages. You can also access this side panel within the component design pages for easy navigation between the different design pages. Figure C-2 shows the Home page with the side panel enabled.

Figure C-2 Orchestrator Studio Home

This image is described in surrounding text.

The Tools link in the upper-right corner of the Home page provides access to the Orchestrator Studio Tools page. This page provides links to the Orchestrator Client for testing orchestrations, the Import tool for importing orchestration files, and the JD Edwards EnterpriseOne web client. For more information, see the following topics:

C.4 Working with Orchestrator Studio Design Pages

This section describes:

C.4.1 Design Page Features

All Orchestrator Studio design pages contain the following features, which are highlighted in Figure C-3:

  • Component list. Displays a list of existing components.

    Use the vertical divider next to the component list to adjust the size of the list. You can click the raised tab on the divider to hide or show the component list.

  • Group Filter drop-down list. Enables you to display components in the component list by UDO status: Personal, Pending Approval, Rework, Reserved, Shared, or All.

  • Search field. Search for an existing component in the list.

  • New <Component> button. Create a new component.

  • i (About). Takes you to the About page which provides the Status, Detail, Description, and Object Name of the selected component. It also shows a list of the orchestrations where the component is used.

  • Restore All or Restore <Component>. Restore the component to its original state if you made a mistake and do not want to save your changes.

  • Export File. Export the component file to your local machine, which you should use only to inspect the XML of the component. See Exporting Orchestration Components from the Orchestrator Studio in this guide for more information.

  • Close. Exit the design page.

Figure C-3 Orchestrator Studio Design Page Features

Description of Figure C-3 follows
Description of ''Figure C-3 Orchestrator Studio Design Page Features''

C.4.2 User Defined Object (UDO) Features

Orchestration components are saved and managed as UDOs in EnterpriseOne. As such, the Orchestrator Studio contains UDO features, highlighted in Figure C-4, to create orchestration components for your own personal use, publish or "share" orchestration components, and modify shared orchestration components created by other users.

Note:

The actions that you are allowed to perform in the Orchestrator Studio depend on the UDO security permissions granted to you by a system administrator. See Setting Up UDO Security for Orchestrator Studio Users (Release 9.2.1) in this guide for more information.

Orchestration components as UDOs enables administrators to use EnterpriseOne administration tools to manage the life cycle of orchestration components. For more information about the life cycle management of UDOs, see "UDO Life Cycle and Statuses" in the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide.

Table C-1 describes the UDO buttons in the Orchestrator Studio design pages and the life cycle status enacted by each UDO action.

Table C-1 Description of UDO Features in Orchestrator Studio Design Pages

UDO Button Description

Save and Save As

Saves the orchestration component to a status of "Personal." This means that the component has not been shared. Components with a status of "Personal" are components that you are developing and have not been shared for publishing to the AIS Server.

Request to Publish

Sends the orchestration component for approval for sharing. An administrator or approver must approve it in order for the UDO to be shared. The component status changes to "Pending Approval" in the component list and then changes to "Shared" once it is approved. If rejected, that status changes to "Rework." At that point, you can edit the component and then use the Request to Publish button to send it for approval again.

Reserve

Reserves a shared UDO so you can modify it. When reserved, no other users can make changes to it. The component status changes to "Reserved."

Unreserve

Cancels the reserved component, which returns the status of the component to "Shared."

Delete

Deletes a "Personal" UDO. You cannot use this button to delete a shared UDO. Shared UDOs can only be deleted by an administrator.

Notes

Available when the component is in the "Pending Approval" status, this button enables you to add an additional note to send to the approver of the UDO. The Notes button is active only if there was a note added the first time the UDO was sent for approval using the "Request to Publish" button. This feature enables you to add an addendum to the original note.


Figure C-4 Design Page UDO Features

Description of Figure C-4 follows
Description of ''Figure C-4 Design Page UDO Features''

C.4.3 Working with the Graphical Representation of an Orchestration

The initial Orchestrations design page shows a graphical representation of an orchestration with all its components, as shown in Figure C-5.

Figure C-5 Initial Orchestrations Design Page

Description of Figure C-5 follows
Description of ''Figure C-5 Initial Orchestrations Design Page''

The graphic area includes the following features:

  • Navigation toolbox

    Click the Control Panel icon in the upper-left corner of the graphic area to display a toolbox for navigating. Use the directional controls to pan left, right, up, and down, as well as zoom in or zoom out. Click "Zoom to Fit" to display the entire graphical representation in the window. Use the layout buttons to change the layout to vertical, horizontal, tree, radial, or circle. This helps to view more complex orchestrations that contain multiple components.

  • Informational hover help

    Hover your mouse over a component in the graphical area to view an enlarged image of the component. Hovering over the labels on the lines between a rule component and its child components magnify the "True" or "False" label. A "True" label indicates the child component will be invoked if the conditions in the rule are met. A "False" label indicates the child component will be invoked when the condition of the rule is not met.

  • Isolate and Restore buttons

    Click the Isolate button on the left side of a component to show only that component in the graphic area. Click Restore to display all orchestration components.

  • Access to the design page for editing the component

    When you click a box representing a component, the Orchestrator Studio takes you to the design page for modifying that particular component.

C.5 Creating Service Requests

This section contains the following topics:

C.5.1 Understanding Service Requests

A service request component provides the instructions the Orchestrator uses to invoke and perform a particular task in EnterpriseOne. You can configure a service request to perform a business transaction, query data, send a message to EnterpriseOne users or external users, execute a custom process such as routing data into another database, or invoke another orchestration or REST service.

The following list describes the service request types you can create in the Orchestrator Studio:

  • Form Request

    A form request contains the instructions for the orchestration to perform a particular task in EnterpriseOne.

  • Custom

    Use custom Java or Groovy to execute a custom process or to route data into another database.

  • Data Request

    Use a data request in an orchestration to query and return values from an EnterpriseOne table or business view. You can also configure a data request to perform an aggregation on data to return aggregate amounts.

  • Message

    Use a message request if you want an orchestration to send a message to an email address or EnterpriseOne users through the EnterpriseOne Work Center.

  • Connector

    Use a connector request to invoke an orchestration or a REST service. For a connector to an orchestration, a connector can invoke a local orchestration or an orchestration on another AIS Server, such as an AIS Server on another EnterpriseOne system in a multisite operation.

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

C.5.1.1 Understanding the Application Stack Option in a Form Request

Use the Application Stack option to create a form request that establishes a session for a specific application and maintains that session across calls. With application stack processing, the form request can invoke multiple forms in different applications to complete a business process. Without application stack processing, each form in a form request is opened independently.

If you use the Application Stack option, the form request must include instructions for navigating between forms. Without the navigation, additional forms cannot be called.

Only values from the last form in the application stack can be returned; return controls specified for any form except the last form are ignored.

C.5.2 Creating a Service Request

To create a service request:

  1. Access the Service Request design page:

    • On the Orchestrator Home page, click the Service Requests icon.

      OR

    • After adding a Service Request step to an orchestration, click the Service Request step row.

    The Orchestrator Studio displays the initial Service Requests design page.

  2. On this page, click Create Service Request, and from the drop-down list, select the type of service request that you want to create:

    • Form Request

    • Custom

    • Data Request

    • Message

    • Connector

  3. (Studio 5.1.0) Click the Product Code drop-down list to select a product code to associate with the service request.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  4. On the Service Request Type design page, complete these fields:

    • Service Request. Enter a name for the service request. You should include the service request type, such as "form request" or "data request," in the name to distinguish it from other service requests listed in the Service Request design page.

    • Short Description. In the space provided, enter a description with a maximum of 200 characters. This description will appear below the service request name in the component list.

  5. (Optional) Click Long Description to provide additional details about the purpose of the service request.

  6. Click Save.

    The first time a new service request is saved, it is saved as a "Personal" UDO. After configuring the service request, you can use the UDO buttons described in the User Defined Object (UDO) Features section to move the service request to the appropriate status.

  7. Refer to the appropriate section for instructions on how to configure the service request type: form request, custom Java, data request, message, or connector.

C.5.3 Configuring a Form Request

After creating the form request as described in Creating a Service Request, perform these tasks:

Load the EnterpriseOne Application Form Fields and Controls

  1. In the Available Actions area, complete the following fields:

    • Application

    • Form

    • Version

  2. Click the Form Mode drop-down list and select the appropriate form mode: Add, Update, or Inquiry.

    At runtime, the controls that appear on an EnterpriseOne form are dependent on the form mode as specified in Form Design Aid (FDA). The form mode ensures that you can see all of the form controls in the Orchestrator Studio that are available in the form at runtime.

  3. (Optional) Click the Application Stack check box to enable application stack processing.

    Use this option to create a form request that establishes a session for a specific application and maintains that session across calls. With application stack processing, the form request can invoke multiple forms in different applications to complete a business process. Without the application stack processing, each form in the form request is opened independently.

    If you use the Application Stack option, the form request must include instructions for navigating between forms. Without the navigation, additional forms will not be called.

  4. Click the Load Form button.

    The Orchestrator Studio loads the controls and fields in the grid. The name of the form is displayed in the first row in the grid.

    If a form request needs to invoke more than one application to complete the desired task, you can load controls and fields for additional application forms as needed.

Configure Form Request Actions

In the Available Actions area, shown in Figure C-6, specify the application fields to which you want to map orchestration inputs, and specify the controls used to carry out the desired task or business process in EnterpriseOne.

Figure C-6 Available Actions Area in the Form Request Design Page

Description of Figure C-6 follows
Description of ''Figure C-6 Available Actions Area in the Form Request Design Page''

Use the following features in the Available Actions area to configure the fields and controls for a form request. After configuring each item, click the Add Action button at the end of each row to add it to the Order of Execution area.

  • Description (informational only)

    This column displays the controls and fields for each form in a collapsible/expandable parent node named after the EnterpriseOne form. Child nodes categorize other items and include a Buttons and Exits node, a node for displaying the available Query by Example (QBE) fields in a grid (if applicable), and a node for displaying all available columns in a grid.

  • Mapped Value

    Use this column to map inputs from the orchestration to fields in the EnterpriseOne form. In this column, enter a variable name for the input.

    The only fields to which you can map inputs are EnterpriseOne editable fields. The variables names for the inputs in the form request should match the inputs defined in the orchestration to which you add the form request. If they do not match, you can use the "Transformations" feature to map input names after you add the form request to an orchestration. See Adding Inputs to an Orchestration and Mapping Inputs in the Transformations Area for more information.

    Instead of a mapped value, you can enter a hard-coded value in the Default Value column or you can click the "Text substitution" check box to combine inputs into a text string.

    This field is also available if you want to populate multiple rows in multiple grids. See Populating Multiple Grids with Repeating Inputs for more information.

  • Default Value

    • For an editable field to which you want to map an input, use this column to enter a hard-coded value. You can also add a hard-coded value to use if the mapped value returns a null.

    • For a check box or a radio button, you can select it to include it. If there are multiple radio buttons grouped together on a form, select only one. If you select more than one, only the last radio button in the Order of Execution list will be used.

    • For a combo box control (a list of items in a drop-down menu), the Studio displays a drop-down menu in the Default Value column in which you can select the appropriate item from the list.

  • Row Number for Update (row)

    If the task requires updating a particular row in an input capable grid, then map the appropriate input value containing the row number to the "Row Number for Update" row, or specify the row number in the Default Value column.

  • "Text Substitution" check box column

    Use text substitution to combine input values into a text string for an input into an EnterpriseOne field. For example, you can create a text string such as "Temp was {0} at {1}" that contains input values for temperature and time.

    Note:

    If you use text substitution for the input, the field cannot contain a mapped value. The substituted text string becomes the default value for the field when you add it to the Order of Execution list.
    1. Click the Add Text Substitution button (plus symbol) in the row that contains the field for which you want to substitute the input with text.

    2. In the Text Substitution field in the pop-up box, use a variable for the first input by entering {0} (with brackets).

    3. In the Variable field, enter the input variable name.

    4. Click the Add (plus symbol) to add the variable for the text substitution.

    5. Add the next variable, {1}, and then in the next blank row below the Variable field, enter the input variable name.

    6. Click Add to add it to the text substitution.

    7. Click OK to save the variables.

      The following image shows an example of variables added for a temperature input value and a date input value:

      Description of text_sub.png follows
      Description of the illustration ''text_sub.png''

  • ID (informational only)

    This column displays the ID of the control or field in EnterpriseOne.

  • Form Mode (informational only)

    If a form mode was selected, this column displays the form mode in the form row.

  • Return

    Select the check box in this column for fields that contain values that you want returned in the orchestration response. If you do not specify any return values, all values on the form will be returned. Return values may be used by customized third-party gateway programs or devices to do further processing based on the values returned from EnterpriseOne applications.

    Caution:

    If using the Application Stack option:
    • Only values from the last form in the application stack are returned; return controls specified for any form except the last form are ignored.

    • If you use a form to add or update a value that upon saving exits to another form, such as a Find/Browse form, the return values will come from the last form that appears after the save. In this scenario, you need to add the last form to the application stack and select the return controls from the last form.

  • Variable Name

    Enabled after selecting the Return check box, use this field to enter a variable name for the return value. When you add the service request to an orchestration, this name appears in the orchestration inputs grid, which makes the returned value available for mapping to subsequent steps in the orchestration.

  • Return Hidden Fields (left arrow icon in the Return column)

    Use this feature to return data from "hidden" fields or grid columns not displayed in the Available Actions area. Hidden fields are fields that appear only after performing a particular action in a form. In the EnterpriseOne web client, use the field-level help (Item Help or F1 key) to identify the control IDs for hidden fields and grid columns. The control ID is displayed in the Advanced Options section in the help pop-up window.

    To return a hidden field:

    1. In the Available Actions area, in the row of the form that contains the hidden fields, click the left arrow in the Return column.

      A dialog box appears displaying the control IDs and associated variable names of any return fields already selected in the Available Actions area.

    2. For hidden fields, enter the control ID of the hidden field in the Return Form Ids field. Optionally, you can enter a variable name to represent the return value in the associated Name field.

      For multiple controls, use a bar delimiter to separate the values in both fields, making sure the order of the values in each field match.

    3. For hidden grid columns, enter the control ID for the grid column in the Return Grid Ids field. Optionally, you can enter a variable name to represent the return value in the associated Name field.

      You must enter a variable name for the return value if you want it to appear in the orchestration inputs list in the orchestration.

      An example of the notation for multiple grid columns in a grid is: 1[32, 34, 42]

      Where 1 represents the first grid in the form (because some forms can have multiple grids), and 32, 34, 42 each represent a column in the grid.

      Use a bar delimiter to separate the variable names, making sure the order of the variable names matches the order of the grid control IDs, as shown in the following example:

      Description of return_fields.png follows
      Description of the illustration ''return_fields.png''

  • Select First Row

    For forms that require selecting the first row in a grid to perform a particular action, the grid displays a row named "Select First Row." Add this row to the Order of Execution if required for the desired task.

  • (Optional) "Options" icon (at the end of the first row in the grid)

    This option contains settings that determine how the AIS Server processes the form request. See Configuring Form Request and Data Request Processing for details.

Configure the Order of Execution

After actions are added to the Order of Execution grid, you can reorder them using the up and down arrow buttons to the right of each row. You can also delete any actions using the Delete (X) button. Figure C-7 shows the Order of Execution area.

Figure C-7 Order of Execution in the Service Request Design Page

Description of Figure C-7 follows
Description of ''Figure C-7 Order of Execution in the Service Request Design Page''

C.5.3.1 Populating Multiple Grids with Repeating Inputs

You can configure a form request to map repeating inputs into one or more grids.

In the Available Actions area, all editable grids have an editable Mapped Value column that will default to GridData. This value can be used to associate a set of repeating inputs to the grid. If you need to populate more than one grid in an orchestration, change this value to identify each grid. And then make sure that the "name" tag that identifies the repeating inputs in the detail inputs section of the orchestration input matches this value.

C.5.4 Configuring a Custom Service Request with Java (Advanced)

You can create a service request that uses custom Java to execute a custom process or to route data into another database. Before you can create a custom Java service request, you must create the custom Java as described in Chapter 8, "Creating Custom Java for Orchestrations".

(These steps have been updated in support of Orchestrator Studio 5.1.0.)

  1. After naming the custom service request as described in Creating a Service Request, select the Java option.

  2. In the Fully Qualified Class field, enter the Java class.

    This is the custom Java class that you created for the service request.

  3. In the first grid, complete the following fields:

    • Input. Enter the name of the field in the class.

    • Input Value. Enter the input variable name. If the attribute is a boolean and you pass in "true", then you could use a default value.

    • Default Value. Enter a default, hard-coded value if there is no mapped value. You can also add a hard-coded value to use if the mapped value returns a null.

  4. (Optional) In the second grid, enter a variable name for an output if you want to use the output value in subsequent steps in the orchestration or to another orchestration.

  5. If you make a mistake, click the Restore Custom Java button to return the custom Java to its last saved state.

  6. Click the Save button.

    The Orchestrator Studio saves the custom Java request. You can then access the orchestration in the Orchestration design page and add this custom Java service request as a step in the orchestration.

C.5.5 Configuring a Custom Service Request with Groovy (Advanced) (Studio 5.1.0)

You can create a service request that uses Groovy scripting to execute a custom process or to route data into another database. To use Groovy for a service request, the Orchestrator Studio provides an edit area that contains a sample Groovy script with instructions on how to modify the script. You can use the Find and "Go to Line" fields and Undo and Redo buttons to work with the script. Chapter 9, "Using Apache Groovy for Custom Service Requests, Rules, and Manipulating Output (Orchestrator Studio 5.1.0 and Higher)" provides information on how to work with the sample Groovy script.

To configure a customer service request with Groovy:

  1. After naming the custom service request as described in Creating a Service Request, select the Groovy option.

  2. Configure the script to perform the desired action.

  3. In the "Input" grid, enter the names of the inputs.

    The inputs will be placed in the inputMap of the "main" function and can be retrieved in the script by following the commented out example code.

  4. Click the Load Outputs button.

    This reads the script and adds any values added to the returnMap in the script to the Output grid.

  5. (Optional) In the "Output" grid, enter a variable name for an output if you want to use the output value in a subsequent orchestration step.

    When you add this service request to an orchestration, this name appears in the orchestration inputs grid, which makes the returned value available for mapping to subsequent steps in the orchestration.

    Note:

    Even if no variables are used, all defined outputs are available for mapping using the Orchestration Output feature. See Working with Orchestration Output for more information.
  6. To test the script:

    1. Enter a value in the Test Value column for one or more inputs.

    2. Click the Test button.

      Orchestrator Studio executes the script using the inputs you entered. If successful, it populates the results in the Test Output column of the Output grid.

      If you included orchAttr.writeWarn or orchAttr.writeDebug statements in the script, a Logging popup displays after execution. At runtime, log statements are included in the AIS Server log, which can be used for debugging script issues.

      The following example shows the Logging popup, which you can use to verify the values passed to the inputs:

      Description of groovy_test.png follows
      Description of the illustration ''groovy_test.png''

  7. Click the Save button.

    The Orchestrator Studio saves the custom Groovy service request. You can then access the orchestration in the Orchestration design page and add this custom Groovy service request as a step in the orchestration.

C.5.6 Configuring a Data Request

You can configure a data request to:

  • Query and return data from an EnterpriseOne table or business view.

  • Perform an aggregation of data from a table or business view and return aggregate amounts.

In a standard data request that returns data directly from a table or business view, you can use variables to define the return fields. In a data request that performs an aggregation, you can use variables to define the "group by" fields and the returned aggregate amounts. You define a variable by typing a name next to the field or item that represents the returned value.

When you add a data request to an orchestration, any variables that you define are automatically added to the orchestration as inputs. This enables you to map the returned data to subsequent steps in an orchestration.

Important:

Variables are only supported in the first row of a response. If a query contains multiple rows, only the values from the first row will be available as variables.

After creating a data request as described in Creating a Service Request, perform these tasks:

Load the Fields from a Table or Business View

You need to know the name of the table or business view that contains the data you want returned. If you do not know the table or business view name, but you know the application that uses the table or business view, you can use the JD Edwards EnterpriseOne Cross Reference Facility (P980011) to identify the table or business view associated with the application. From the Cross Reference form, click the "Interactive Applications" tab, then click the "Business Views Used by an Interactive Application" or "Tables Used by an Interactive Application." If you do not have access to the Cross Reference Facility, ask an administrator to look up this information for you.

  1. In the Available Actions area, enter the name of the table or business view in the Table/View Name field.

  2. Click the Load button.

    The Orchestrator Studio loads all fields from the table or business view into the grid.

Configure a Data Request to Return Field Data

After loading fields from a table or business view, set up filtering criteria and specify the fields that contain data that you want returned.

For example, a business analyst wants to add a data request to an orchestration that returns a customer's credit limit amount. The orchestration has "Customer Number" defined for one of its inputs. To configure the data request, the business analyst:

  • Sets up filter criteria with a condition that filters on Address Number.

  • Selects the Credit Limit and Alpha Name fields for the return data.

  • Adds the data request to the orchestration, mapping the Customer Number input in the orchestration to the Address Number in the data request.

    When the data request is added to the orchestration, the Credit Limit and Alpha Name fields automatically become additional inputs to the orchestration, which the business analyst can then map to subsequent orchestration steps.

To configure a data request to return field data:

  1. Define the filtering criteria for the data request:

    1. In the Fields grid on the left, click the "Filter" icon next to the field or fields that contain data that you want to filter on.

      The Orchestrator Studio displays each field in the Filter Criteria area on the right.

    2. For each field in the Conditions box, select the appropriate operand and in the adjacent field, enter a hard coded value or a variable.

      A variable appears in the field by default. If you modify the variable name, make sure the syntax includes the $ sign and brackets, for example:

      ${Address Number 1}

    3. Select the Match All or Match Any option to determine how the conditions are applied.

      You can also click the Options button, and from the Query drop-down list, select a predefined q uery to use for the filtering criteria. You can use a query instead of or in combination with the filtering criteria defined in a data request. The queries that you can see in this list are based on UDO security permissions.

  2. Specify the data you want returned:

    1. In the Fields grid, click the "Return" icon next to each field for which you want data returned.

      Each field appears in the "Return Fields and Variable Names" on the right.

    2. (Optional) You can use a variable for the return by entering a name for the variable in the adjacent blank field.

      Note:

      Return variables do not need the ${} notation. This notation is only necessary for input variables to distinguish between a variable and a hard coded value.

      When you add a data request to an orchestration, these variables are automatically added to the orchestration as inputs, which you can use to map return data to subsequent orchestration steps.

  3. (Optional) For the return data, determine the order by which you want the data returned:

    1. In the grid on the left, select the Order By icon next to any field that was selected for the return data.

      The Orchestrator Studio adds the field name to the Order By area on the right.

    2. In the drop-down list next to the field name, select Ascending or Descending.

  4. (Optional) Click the Options button to configure settings that control how the AIS Server processes a data request at runtime. See Configuring Form Request and Data Request Processing.

Configure a Data Request to Perform an Aggregation

To configure a data request to return aggregate amounts:

  1. After loading the fields from a table or business view, slide the Aggregation toggle to the right.

    This enables the aggregation features in the Fields grid.

  2. Click the "Filter" icon next to the fields that contain the data that you want to filter on.

    The Orchestrator Studio displays each field in the Conditions area on the right.

  3. Set up conditions for filtering data:

    1. For each field in the Conditions box, select the appropriate operand and in the adjacent field, enter a hard coded value or a variable.

      A variable appears in the field by default. You can modify the variable name, but you must use the $ sign and brackets in the syntax, for example:

      ${Address Number 1}

    2. Select the Match All or Match Any option to determine how the conditions are applied.

      You can also select the Options button, and from the Query drop-down list, select a predefined q uery to use for the filtering criteria. You can use a query instead of or in combination with the filtering criteria defined in a data request. The queries that you can see in this list are based on UDO security permissions.

  4. Click the "Aggregate" icon next to the fields that contain the data for the aggregation.

  5. In the pop-up window, select the type of aggregate that you want to perform.

    The aggregate options displayed depend on whether the field contains a numeric value or a string.

  6. (Optional) In the Aggregations and Variable Names section, click the Include Count check box if you want the response to include a count of the records returned. To use the returned count in a subsequent orchestration step, enter a variable name in the adjacent field.

  7. (Optional) Use the following features in the Fields grid to further define the data aggregation:

    • "Having" icon. Click this icon next to a field for which you want to provide additional filtering criteria on an aggregation.

      The Data Request design page displays the field in the Having section on the right.

      a. Click the drop-down list next to the field and select the operand.

      b. In the adjacent field, enter a hard coded value or variable.

    • "Group By" icon. Click this icon next to any field that you want the aggregate results grouped by. In the "Group By and Variable Name" section on the right, you can enter a variable name.

      Using "Group By" may result in multiple rows being returned, one for each unique combination of a group. For example, you might return total orders for an entire year for customers, and group the results by customer. In this case, the data request response will return a unique row for each customer with the customer's total orders for the year.

      Note:

      Variables are only supported in the first row of a response. If a query contains multiple rows, only the values from the first row will be available as variables.
    • "Order By" icon. For any fields used in an aggregate or "group by," click this icon to arrange return data in ascending or descending order.

  8. (Optional) Click the Options button to configure settings that control how the AIS Server processes a data request at runtime. See Configuring Form Request and Data Request Processing.

C.5.6.1 Viewing and Copying JSON Code of a Data Request

After configuring a data request, you can click the Preview button to view and copy the JSON code for a data request. Developers can use this code to develop AIS client applications that can make data request calls directly to the AIS Server rather than through an orchestration. See the JD Edwards EnterpriseOne Application Interface Services Client Java API Developer's Guide for more information.

C.5.7 Configuring a Message Request

Add a message request to an orchestration to send emails to external email systems or the EnterpriseOne Work Center email system. The following EnterpriseOne Work Center and workflow features are supported in a message request:

  • Workflow distribution lists to send messages to a predefined group of EnterpriseOne users.

  • Message templates from the data dictionary that contain boilerplate text and values related to a particular business process.

  • Shortcuts to EnterpriseOne applications.

For more information about these workflow features, see the JD Edwards EnterpriseOne Tools Workflow Tools Guide.

In a message request, you can include variables to pass data from an orchestration input into a message request. You can include variables in the recipient fields, the subject and body, a message template, and a shortcut.

To configure a message request:

  1. Create and name the message request as described in Creating a Service Request.

  2. To enter recipients (To, Cc, or Bcc), select a recipient type:

    • Select Address Book to send a message to a single EnterpriseOne user. Enter the address book number of the EnterpriseOne user.

    • Select Contact to send a message to an individual in a user's contact list. Enter the address book number of a user and then the number of the contact.

    • Select Distribution List to send a message to the members of an EnterpriseOne distribution list. Enter the address book number of the list in the Parent Address Number field and select its structure type. For more information about structure types, see "Structure Types" in the JD Edwards EnterpriseOne Tools Workflow Tools Guide.

    • Select Email to enter an email address for the recipient.

  3. In the Subject and body fields, enter text, variables, or a combination of both. To insert variables, see step 6.

  4. To include boilerplate text from a message template in the data dictionary:

    1. Expand the Data Dictionary Text section.

    2. In the Data Item field, enter the name of the message template data item and click Load.

    3. If the message template contains variables, use the grid in the right to override the variables with text substitution.

  5. To include a shortcut to an application:

    1. Expand the JD Edward EnterpriseOne Shortcut section.

    2. Complete the Application, Form, and Version fields to specify the form that you want the shortcut to launch.

    3. Click Load.

    4. In the grid, you can use variables to pass in data to the application when the application is launched from the shortcut.

  6. To include variables in the recipient types, subject, body, message template text, or shortcut:

    1. Right-click in a field and click Insert Variable.

    2. In the variable that appears, rename variable as appropriate, but make sure the syntax includes the $ sign and brackets, for example:

      ${creditmanager}

      Description of message_request.png follows
      Description of the illustration ''message_request.png''

C.5.8 Configuring a Connector

In the Orchestrator Studio, you can configure a connector service request to enable an orchestration to:

  • Invoke another orchestration on your local system or on an AIS Server on another EnterpriseOne system in a multisite operation.

  • Invoke a REST service. (Orchestrator Studio 5.1.0) This enables outbound REST calls to external systems as an orchestration step. For example, an orchestration could make a REST call to a Cloud service and use the data in the response in subsequent orchestration steps.

When you configure a connector, you select a connection to the system where the orchestrations or REST service resides. This provides a list of orchestrations or the REST service that you can configure a connector service request to invoke.

Before you can create a connector service request, an administrator must set up a connection to the system with the orchestrations or REST service. See Creating Connection Soft Coding Records for Connector Service Requests for details.

C.5.8.1 Configuring a Connector to Invoke an Orchestration

  1. Create and name the connector service request as described in Creating a Service Request.

  2. On the Connector design page, click in the Connection field and select an Orchestrator connection.

    Connections to orchestrations appear under "Orchestrator." After you select a connection, the Orchestrator Studio displays the URL to the AIS Server next to the Connection field.

  3. You can click the Test Connection button to test the connection to the AIS Server.

  4. Select an orchestration from the Orchestration drop-down list.

    The inputs in the orchestration appear in the Orchestration Input column. A variable for each input is automatically generated in the adjacent Input column.

  5. You can modify the variable names as desired or map a hard coded value by entering the value (without the ${} notation).

C.5.8.2 Configuring a Connector to Invoke a REST Service (Studio 5.1.0)

To configure a connector to a REST service, you specify an HTTP method and then provide the following additional details to complete the request:

  • The path to a particular endpoint in the REST service.

  • Parameters, if required by the endpoint.

  • Key-value pairs for the HTTP header.

In the Orchestrator Studio, you can test the connector to view the JSON response of the REST service call. You can also use Groovy scripting to refine the data in the connector output. For example, you can configure a Groovy script to refine the contents of the REST service response so that the connector output contains only the data required by the consuming device or program.

To configure a connector to invoke a REST service:

  1. Create and name the connector service request as described in Creating a Service Request.

  2. On the Connector design page, click the Connection field and select a connection under the REST category.

    The Orchestrator Studio displays the URL to the REST service available through the connection.

  3. Click the HTTP Method drop-down list and select the appropriate method.

  4. Slide the Fire and Forget toggle to the right if you want the orchestration to execute without waiting for a response. If Fire and Forget is enabled, the Output section is hidden because the REST service response is not processed.

  5. Expand the Pathing section and use the Value grid to build the path to a REST service endpoint.

    Each value you enter in the Value grid is appended to the path, separated by a forward slash (/). You can use variables in the path by adding a value inside ${}. Click the Delete button at the end of a row to delete any values from the path.

    The following image shows an example of a path to an endpoint that includes variables.

    Description of pathing.png follows
    Description of the illustration ''pathing.png''

  6. If the REST service takes parameters, use the Parameters section to append parameters to the endpoint.

    Parameters are appended to the endpoint after a "?" and are separated by a "&". You can include variables by specifying a value inside ${}.

  7. In the Headers section, enter key-value pairs for the header in the Key and Value columns. You can also choose any known values from the drop-down menu in each column.

  8. In the Body section (which is not used or displayed if the HTTP method is GET or TRACE), if the HTTP method requires it, specify a payload to send to the REST service.

  9. In the Output section, use the following sections to identify the outputs:

    Note:

    The outputs are based on the JSON response of the REST service call. You can see the response after running a successful test of the REST service using the Test button.
    • Manipulate Output (advanced). Use Groovy scripting to manipulate the output of the REST call. For example, if you only need certain data in the output, you can use Groovy scripting to refine the data displayed in the output. See Groovy Template for Manipulating Output from a REST Connector Response for more information.

    • Output grid. If the value you want is nested in JSON objects, you can get to the value by separating each JSON object name by a period (.). If the value you want is in an array, you can access it by adding the proper index of the array inside [].

    The following image shows an example of outputs defined in the Output section:

    Surrounding text describes connector_output.png.
  10. To test the connector:

    1. Click the Test button.

    2. If the connector includes variables, enter values for the variables in the popup box.

      If successful, the Orchestrator Studio displays the response.

    3. Click the Show Output button displayed at the end of the response to apply the instructions defined in the Output section, including the Groovy script if specified.

      Use the results to validate the path to the output values specified in the Output section.

C.5.9 Configuring Form Request and Data Request Processing

In the Orchestrator Studio, you can configure settings that control how the AIS Server processes a form request or data request in an orchestration at runtime.

For form requests, these settings are available from the Options icon at the end of the first row of each form listed in the Available Actions grid.

For data requests, these settings are available from the Options button on the Data Request design page.

The settings include:

  • Maximum Records. 0 is for All Records.

  • Query Name. From this drop-down list, you can select a predefined query to use for the filtering criteria. You can use a query instead of or in combination with the filtering criteria defined in a data request. The queries that you can see in this list are based on UDO security permissions.

  • Output Type. Select one of the following format types for the format of the JSON response. Formats include:

    • Default. The default format is Version 2 output type for version 1 orchestrations (orchestrations created prior to Orchestrator Studio 5.0.1). The default format is Grid Data output type for version 2 orchestrations (orchestrations created in Orchestrator Studio 5.0.1 and higher).

    • Grid Data. Returns grid data in simplified name-value pairs. This is the default output type for version 2 orchestrations (orchestrations created in Orchestrator Studio 5.0.1 and higher).

    • Version 2. Returns cell-specific information for each grid row as well as information about each column such as column ID, whether it is visible, editable, and so forth. This is the default output type for orchestrations created prior to Orchestrator Studio 5.0.1, which are referred to as version 1 orchestrations.

  • Stop on Warning check box (form requests only). Click this check box if you want the processing to stop if the invoked EnterpriseOne form produces a "Warning" message. Keep this check box clear if you want processing to continue after a warning message.

  • Turbo Mode (form requests only). Use this option to reduce processing time of form requests. See "Using Turbo Mode" in the JD Edwards EnterpriseOne Application Interface Services Client Java API Developer's Guide for more information.

  • Caching: Allow. Click this check box to enable caching of the service request response. If the "Enable Caching by Default" option is enabled in Server Manager, this parameter is ignored and all responses for Read operations will be cached.

  • Caching: Force Update. Click this check box to force the system to fetch the data from the database for the service request. If the "Enable Caching by Default" setting is enabled in Server Manager, then this parameter for the individual service request is ignored.

  • Caching: Time Stored - Milliseconds. Enter the amount of time in milliseconds for the service request to use the cache for the response. This setting overrides the value in the "Default Read Cache Time To Live" setting in Server Manager.

C.6 Creating Rules

This section contains the following topics:

C.6.1 Understanding Rules

A rule contains conditional logic that the Orchestrator uses to evaluate conditions, such as true or false conditions that determine how the orchestration processes the incoming data. You can define a rule with a list of conditions or you can define a more complex rule using Groovy (Studio 5.1.0) or a custom Java class.

An orchestration rule with conditions functions similar to an EnterpriseOne query in that each rule has:

  • A "Match Any" or "Match All" setting.

  • One or more conditions defined, each being a binary operation on two values.

After creating a rule and adding it to an orchestration, you use the Action column in the Orchestration design page to determine the orchestration step that is invoked when the conditions in the rule are met. See Defining the Actions Between a Rule and Dependent Components for more information.

C.6.2 Creating a Rule

Create a rule component to define the conditions for an orchestration.

To create a rule:

  1. Access the Rules design page:

    • On the Orchestrator Home page, click the Rules icon. And then on the Rules design page, click the New Rule button.

      OR

    • After adding a Rule step to the grid in the Orchestration design page, click the Edit button next to the step.

    The Orchestrator Studio displays the Rule design page.

  2. In the Rule field, enter a name for the rule.

  3. (Studio 5.1.0) Click the Product Code drop-down list to select a product code to associate with the rule.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  4. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the rule name in the component list.

  5. Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.

  6. Select the Match Value drop-down menu and select one of the following values:

    • Match All. Select this option if all conditions in the rule must be met.

    • Match Any. Select this option if any conditions in the rule can be met.

  7. In the first row in the grid, complete the following columns to add a condition:

    • Rule Type. Click the drop-down menu and select String, Numeric, or Date depending on the format of the input.

    • Value 1. Enter a variable for the input name.

    • Operator. In the drop-down menu, select from the list of operands which include: >, <, >=, <=, =, !=, startsWith, endWith, contains, between, inList.

    • Literal. Click this check box to indicate a literal value.

    • Value 2. If you selected the Literal check box, manually enter a value.

    • Literal Value Type. If you selected the Literal check box, click the drop-down menu and select the format of the literal value: string, numeric, data.

  8. Add additional conditions to the rule as needed. If you add a condition by mistake, you can delete it by clicking the Remove button at the end of the row with the condition.

  9. Click the Save button.

    The first time a new rule is saved, it is saved as a "Personal" UDO. Thereafter, you can use the UDO buttons described in the User Defined Object (UDO) Features section to move the rule to the appropriate status.

    After adding a rule and a service request to an orchestration, in the Orchestration design page, you must define the action for the rule to invoke the service request. See Defining the Actions Between a Rule and Dependent Components for more information.

C.6.3 Creating a Custom Rule with Java (Advanced)

You can create complex rule using custom Java. Before you add a custom Java rule in the Orchestrator Studio, you must create a custom Java class to use for the rule as described in Chapter 8, "Creating Custom Java for Orchestrations".

To create a custom Java rule:

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

  2. On the Rules design page, click the New Custom button.

  3. Select the Java radio button.

  4. In the Rule field, enter a name for the custom rule.

  5. (Studio 5.1.0) Click the Product Code drop-down list to select a product code to associate with the rule.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  6. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the rule name in the component list.

  7. Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.

  8. In the Fully Qualified Class field, enter the fully qualified path to the Java class, which includes the name of the Java class.

    This is the custom Java class that you created to use for the rule.

  9. Complete the following fields in the grid:

    • Attribute. Enter the name of the field in the class.

    • Input Value. Enter a variable for the input name. If the attribute is a boolean and you pass in "true", then you could enter a hard-coded default value.

    • Default Value. Enter a hard-coded value if there is no mapped value. You can also add a hard-coded value to use if the mapped value returns a null.

  10. If you make a mistake while configuring any of the fields, you can click the Restore Rule button which refreshes the custom Java rule to its last saved state.

  11. Click the Save button.

C.6.4 Creating a Custom Rule with Groovy (Advanced) (Studio 5.1.0)

Use Groovy to create a custom rule when conditions in a standard rule will not suffice.

To create a custom rule with Groovy:

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

  2. On the Rules design page, click the New Custom button.

  3. In the Rule field, enter a name for the custom rule.

  4. Click the Product Code drop-down list to select a product code to associate with the rule.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  5. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the rule name in the component list.

  6. Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.

  7. Select the Groovy radio button.

    The Orchestrator Studio displays an edit area that contains a sample groovy script with instructions on how to work with the script. Use the Find and "Go to Line" fields and Undo and Redo buttons to help edit the script. See Chapter 9, "Using Apache Groovy for Custom Service Requests, Rules, and Manipulating Output (Orchestrator Studio 5.1.0 and Higher)" for more information about the sample Groovy script.

  8. Configure the script to perform the desired action.

  9. In the "Input" grid, enter the names of the inputs.

  10. To test the script:

    1. Enter a value in the Test Value column for one or more inputs.

    2. Click the Test button.

      If you included orchAttr.writeWarn or orchAttr.writeDebug statements in the script, a Logging popup displays after execution. At runtime, log statements are included in the AIS Server log, which can be used for debugging script issues.

      A Logging dialog box displays the test results which you can use to verify the values passed to the inputs, as shown in the following example:

      Description of groovy_rule_test.png follows
      Description of the illustration ''groovy_rule_test.png''

  11. Click the Save button.

C.7 Creating Cross References

This section contains the following topics:

C.7.1 Understanding Cross References

The Orchestrator uses a cross reference component to map incoming data (third-party data) to an EnterpriseOne value. The EnterpriseOne value identified in the cross reference is considered the output of the cross reference. The output from the cross reference becomes the data passed to another orchestration step.

For each cross reference that you create in the Orchestrator Studio, you have to create a cross reference record in P952000 in EnterpriseOne. When defining cross reference records for orchestrations in P952000, you must use the "AIS" cross reference type. For more information on how to create these cross reference records in P952000, see Chapter 5, "Setting Up Cross References and White Lists in EnterpriseOne (P952000)" in this guide.

Note:

If a cross reference lookup fails in an orchestration, the orchestration is terminated.

C.7.2 Creating a Cross Reference

You must define the orchestration inputs before you can create a cross reference. See Adding Inputs to an Orchestration for more information.

To create a cross reference:

  1. Access the Cross Reference design page:

    • On the Orchestrator Home page, click the Cross References icon. And then on the Cross References design page, click the New Cross Reference button.

      OR

    • After adding a Cross Reference step to the grid in the Orchestration design page, click the Edit button next to the step.

    The Orchestrator Studio displays the Cross Reference design page.

  2. In the Cross Reference field, enter a name for the cross reference.

  3. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the cross reference name in the component list.

  4. Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.

  5. In the Object Type field, enter a name for the object type.

    This is the object type used to categorize the orchestration cross references in EnterpriseOne. See "Adding Orchestration Cross References" in the JD Edwards EnterpriseOne Tools Interoperability Guide for more information.

  6. (Studio 5.1.0) Click the Product Code drop-down list to select a product code to associate with the cross reference.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  7. Complete the Input Key and Output Key columns to map the inputs to EnterpriseOne fields:

  8. If you enter any values by mistake, you can click the X button next to the field to delete the entry.

  9. Click the Save button, which saves the white list as a "Personal" UDO.

    The first time a new cross reference is saved, it is saved as a "Personal" UDO. Thereafter, you can use the UDO buttons described in the User Defined Object (UDO) Features section to move the rule to the appropriate status.

    The output values in the cross reference are now available for mapping in subsequent orchestration steps.

C.8 Creating White Lists

This section contains the following topics:

C.8.1 Understanding White Lists

A white list contains a list of IDs permitted in the Orchestrator. By adding a white list to an orchestration, only inputs with IDs listed in the white list are permitted for processing by the Orchestrator. You add a white list component as a step in the orchestration.

In addition to specifying the permitted IDs in the white list, you must also specify the white list IDs in P952000 in EnterpriseOne. This is the same application that you use to set up and store orchestration cross references. As with cross references, use the "AIS" cross reference type in P952000 for a white list. In P952000, the Third Party App ID should have a value of WHITELIST. The EnterpriseOne value is not used for white lists and will default to NA.

If a white list lookup fails in an orchestration, the orchestration is terminated.

C.8.2 Creating a White List

  1. Access the White List design page:

    • On the Orchestrator Home page, click the White Lists icon. And then on the White Lists design page, click the New White List button.

      OR

    • After adding a White List step to the grid in the Orchestration design page, click the Edit button next to the step.

    The Orchestrator Studio displays the White Lists design page.

  2. In the White Lists design page, click the New White List button.

  3. In the White List, enter a name for the white list.

  4. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the white list name in the component list.

  5. Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.

  6. In the Object Type field, enter a name for the object type.

    The value you enter in the Object Type field must match a cross reference object type in the EnterpriseOne Business Services Cross Reference application (P952000).

    The cross reference object type is a named group of records in P952000. For example, you may have thousands of records in P952000. You can use cross reference object types, for example "Equipment" or "Alert_Notification_Recipients" to group cross reference records into manageable categories. You define the cross reference object types as needed. See Chapter 5, "Setting Up Cross References and White Lists in EnterpriseOne (P952000)" for more information.

  7. (Studio 5.1.0) Click the Product Code drop-down list to select a product code to associate with the white list.

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  8. In the Input Key column, enter the input that you want to add as a permitted input.

  9. Click the Save button.

    The first time a new white list is saved, it is saved as a "Personal" UDO. Thereafter, you can use the UDO buttons described in the User Defined Object (UDO) Features section to move the white list to the appropriate status.

C.9 Creating Orchestrations

This section contains the following topics:

C.9.1 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. See Supported Input Message Formats for more information about which input format to use.

  • Adding inputs to the orchestration.

    The inputs define the data passed from the device to the orchestration. This may include an ID that identifies the device as well as other data that the orchestration will receive from a device, such as temperature, date, or any other data you want to capture. Each input has a name and a type which can be string, numeric, or various date formats.

  • 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.

C.9.2 Creating an Orchestration

To create an orchestration:

  1. On the Orchestrator Studio Home page, click the Orchestrations icon.

  2. On the Orchestrations page, click the New Orchestration button.

  3. On the Orchestration design page, enter a unique name for the orchestration in the Orchestration field.

    All orchestrations created in Orchestrator Studio 5.0.1 or higher are saved as version 2 orchestrations. You cannot change this value in the Orchestrator Version drop-down list. If you want to update a version 1 orchestration created in a previous version of the Orchestrator Studio, see Updating Version 1 Orchestrations to Version 2 Orchestrations.

    Note:

    When you save an orchestration, the orchestration name is used to define an endpoint on the AIS Server. The endpoint URL is:

    http://<server>:<port>/jderest/orchestrator/<orchestrationname>

    To invoke this orchestration, third-party applications or devices use a post operation to this url, where <orchestrationname> is the name of the orchestration.

  4. Click the Product Code drop-down list to select a product code to associate with the orchestration. (Studio 5.1.0)

    This gives an administrator the option to manage UDO security for orchestration components by product code.

  5. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the orchestration name in the component list.

  6. Click the Edit Long Description button to provide more detail about the component.

    Use this field to describe the purpose of the orchestration and any details that differentiate the orchestration from other orchestrations that you create.

  7. Click the Input Format drop-down menu and select the appropriate format:

    • JDE Standard (default)

    • Oracle Cloud IoT

    • Generic

    See Supported Input Message Formats for more information about which input format to use.

  8. At this point, you can click Save before defining inputs or steps for the orchestration.

    The Orchestrator Studio saves the orchestration as a "Personal" UDO. Next, add inputs to the orchestration as described in the Adding Inputs to an Orchestration section.

You can also use the Save As button and rename an existing orchestration to create a new one.

Caution:

If you use Save As to create a copy of an orchestration, only the orchestration is copied. The Orchestrator Studio does NOT create a copy of the components that are associated with the orchestration's steps. That is, both the original orchestration and the new orchestration use the same components that comprise the orchestration. Therefore, in the new orchestration, do NOT modify the components in any way that would break other orchestrations that use the same components.

C.9.3 Adding Inputs to an Orchestration

Orchestration inputs identify the data an orchestration consumes from external devices. In the orchestration, you enter names for the inputs. For example you can enter "SensorID" to pass a sensor ID value to an orchestration and you can enter "TemperatureReading" to pass a temperature value to the orchestration.

You also use these orchestration inputs to configure other components used by the orchestration, such as a service request, rule, white list, or cross reference. For example, if the orchestration requires a rule, you use the orchestration inputs to define the conditions for the rule. If an incoming value from a device does not match an EnterpriseOne value, you can create a cross reference that uses the orchestration input to map third-party data to data in EnterpriseOne.

To add the orchestration inputs:

  1. In the first empty row in the Orchestration grid, enter the name of the input in the Input column.

  2. In the Value Type column, select the input value type. Valid values are:

    • String

    • Numeric

    If the input is a date, you can use any of the following date formats:

    • dd/MM/yyyy

    • dd/MM/yy

    • yyyy/MM/dd

    • MM/dd/yyyy

    • MM/dd/yy

    • yy/MM/dd

    You can also use the following date formats, which create additional inputs derived from the passed value:

    • Milliseconds

    • yyyy-MM-dd'T'HH:mm:ss.SSSZ

  3. Click Save to save your changes.

C.9.4 Adding Steps to an Orchestration

When you add a service request, rule, cross reference, or white list to an orchestration, you add it as a step in the orchestration. It is recommended that you create the component before adding it as a step in an orchestration.

The Orchestrator Studio provides "Insert Step Before" and "Insert Step After" buttons so you can add a step before or after another step in the orchestration. Therefore, you do not have to determine whether or not you need to add a particular step, such as a white list, to an orchestration before you add other steps.

Figure C-8 shows an orchestration that contains multiple rules, cross references, and service requests, which are displayed in the grid on the Orchestration design page:

Figure C-8 Steps in the AddConditionBased Alert Sample Orchestration in the Orchestrator Studio

Description of Figure C-8 follows
Description of ''Figure C-8 Steps in the AddConditionBased Alert Sample Orchestration in the Orchestrator Studio''

In the grid, the Type column shows the type of step and the Name column shows the name of the component for the orchestration step. The "True" or "False" values in the Action column determine the actions the orchestration performs based on the conditions set in the rules. See Defining the Actions Between a Rule and Dependent Components for information about defining the actions in an orchestration.

To add steps to an orchestration:

  1. To add the initial step to an orchestration, click the Add Step button (+ symbol).

  2. In the "Enter Type of Step" pop-up field, select one of the following steps to add to the orchestration, and then click the Ok button.

    • Cross Reference

    • Rule

    • Service Request

    • White List

    The Orchestrator Studio displays the first step in the grid.

  3. Add a component to the step:

    1. To use an existing component for the new step, click the drop-down menu in the Name column and select a component.

    2. To create a new component for the step, click the Edit button (pencil icon) at the end of the row to access the design page for creating the new component.

      After creating the component, when you return to the Orchestration design page, you will need to select the component from the drop-down menu in the orchestration steps grid to add it.

    See the appropriate topics in this chapter on how to create each type of orchestration component.

  4. In the Transformations area on the right side of the page, configure the transformations for each orchestration step as described in the Mapping Inputs in the Transformations Area section.

  5. To add additional steps to an orchestration:

    1. Select a step in the grid, and then click either the Insert Step Before or Insert Step After button to add an additional step before or after the selected step.

    2. In the "Enter Type of Step" pop-up dialog box, select the step that you want to add.

    3. Click the Ok button.

To remove a step from an orchestration:

Caution:

Before you delete a step, make sure the step is not used by any other component in the orchestration.
  1. Select the step that you want to remove.

  2. Above the grid with the steps, click the Remove Step button (the X button).

If you make a mistake when updating an orchestration, click the Restore All button in the upper-right corner of the design page to restore the orchestration to its last saved version, which erases any changes made since the last save.

C.9.4.1 Defining the Actions Between a Rule and Dependent Components

The Orchestration design page contains an Action column for defining the actions between a rule step and other orchestration steps in an orchestration. After you create a rule with conditions and add it as a step to an orchestration, you need to define the action the orchestration takes if the condition in the rule is met. For example, if a rule contains a condition that when met should invoke a service request step, then in the row with the service request step, you set the Action column to True.

You can also define a False action to invoke a different orchestration step when a condition in the initial rule is NOT met. A False action can invoke a different Service Request step or another rule step that contains additional conditions for which the incoming data is evaluated against. Thus, you can design an orchestration with as many rules and service requests as your business requirements necessitate.

Figure C-9 shows an example of an orchestration with two rule steps and two service request steps, with the following defined actions:

  • For the first service request step, the action is set to True to instruct the orchestration to invoke this service request step when the condition in the first rule step is met.

  • The action for the second (nested) rule step is set to False to instruct the orchestration to invoke this rule when the condition in the first rule is NOT met.

  • The action for the second service request step is set to True to instruct the orchestration to invoke this service request when the condition in the second rule is met.

Figure C-9 Defining the Orchestration Actions

Description of Figure C-9 follows
Description of ''Figure C-9 Defining the Orchestration Actions''

To set the Action column to True or False:

  1. In the Orchestration design page, in the appropriate Rule or Service Request step row, click in the Action column.

  2. Select either True or False as appropriate.

  3. Click the Save button.

    After completing the orchestration, you can use the Orchestrator Client to test the orchestration in a test environment. You can access the Orchestrator Client from the drop-down menu in the upper-right corner of the Orchestrator Studio. See Chapter 10, "Testing Orchestrations in the EnterpriseOne Orchestrator Client" for more information.

C.9.5 Mapping Inputs in the Transformations Area

Use the Transformations area on the Orchestration design page to map orchestration inputs to inputs defined in an orchestration step, such as inputs in a rule, cross reference, white list, or service request component. The Transformations area includes an Auto Map button that automatically maps any matching inputs in the orchestration and orchestration step.

If an orchestration and an orchestration component use different input names to identify the same data, you can use the grid in the Transformations area to map the inputs. This facilitates the reuse of components, so you can avoid having to create a new component simply to match the input names (input from a device) in a new orchestration.

To better understand how you use transformations, consider the following scenario which is depicted in Figure C-10:

  • You have an existing service request that creates alerts in the EnterpriseOne Condition-Based Alerts Revisions application (P1311). This service request includes an input called EquipmentNumber that is mapped to the Asset Number field in P1311.

  • You want to reuse this service request as a step in a new orchestration, but the new orchestration will consume data from devices that supply the EquipmentNumber as "SerialNumber."

  • To reuse the existing service request designed to consume data labeled as EquipmentNumber, in the new orchestration, you can create a transformation to pass the SerialNumber input to the EquipmentNumber input in the service request.

  • Create the new orchestration with SerialNumber as one of the inputs, and then add the existing service request as a step.

  • When you click the Service Request step in the orchestration steps grid, the Service Request column in the Transformations table displays all of the inputs defined in the service request. Notice in Figure C-10 that EquipmentNumber, not SerialNumber, is defined as an input in the Service Request Input column.

  • Next, you click the Transformations Auto Map button, which automatically maps the matching inputs. Figure C-10 shows the SiteNumber, Latitude, and Longitude inputs in the Orchestration Input column, which were populated automatically after clicking Auto Map.

  • Finally, to map the SerialNumber input in the orchestration to the EquipmentNumber input in the service request, you click the drop-down menu in the Orchestration Input column and select SerialNumber, as shown in Figure C-10.

Figure C-10 Transformations Example

Description of Figure C-10 follows
Description of ''Figure C-10 Transformations Example''

Initially, when you have a small number of orchestrations in your system, it is recommended to keep all input names consistent among the orchestration and all components (orchestration steps) used by orchestration. But as your library of orchestrations and orchestration components increases, instead of creating new components with input names that match the orchestration inputs, you can use transformations to map the orchestration inputs to an existing component.

To map inputs:

  1. In the Orchestration design page, select an orchestration step to which you want to map orchestration inputs.

  2. Click the Transformations Auto Map button to map any matching input names. Matching inputs automatically appear in the Orchestration Input column next to the matching input in the "<orchestration step> Input" column.

  3. To map an orchestration input to an orchestration step input that does not have the same name:

    1. In the Transformations table, click the drop-down menu in the Orchestration Input column next to the orchestration step input.

    2. Select the orchestration input to map to the orchestration step input.

    For example, in Figure C-10, SerialNumber is mapped to EquipmentNumber in the Service Request Input.

  4. You can map a literal value to the orchestration step input by entering a value in the Default Value column.

C.9.6 Updating Version 1 Orchestrations to Version 2 Orchestrations

When executed by the Orchestrator on the AIS Server, orchestrations programmatically call AIS services on the AIS Server to perform specific actions in EnterpriseOne.

Starting with EnterpriseOne Tools 9.2.1.2 is the availability of version 2 AIS services. Version 2 AIS services include all services originally available on the AIS Server (referred to as version 1 services), plus additional services that enable you to create an orchestration that includes the following types of service requests:

  • Data request

  • Message

  • Connector

All orchestrations that you create with Orchestrator Studio 5.0.1 or higher use version 2 AIS services and are referred to as version 2 orchestrations.

All orchestrations created prior to Orchestrator Studio 5.0.1 use version 1 AIS services and are referred to as version 1 orchestrations.

In Orchestrator Studio 5.0.1 or higher, you can update version 1 orchestrations. However, if you add any of the components in the preceding list that rely on version 2 AIS services, you must save the orchestration as version 2 by selecting Version 2 from the Orchestrator Version drop-down list.

Caution:

If you save a version 1 orchestration as version 2, the following parameters are used for the service request by default:

  • Output Type = grid data

  • Turbo Mode = low

This changes the format of the response, which will affect any device consuming the output returned from the orchestration.

C.9.7 Working with Orchestration Output

Use the Orchestration Output page to view the JSON representation of orchestration output. Viewing the output enables you to validate the fields that contain the data you want returned in the orchestration output for output mapping.

Orchestration output can include values from fields and grid columns that you specify as returns when setting up a form request, data request, or cross reference in an orchestration. It can also include the response from a connector, custom service request, or the result of a rule (true or false).

On the Orchestration Output page, you can use Groovy scripting to manipulate the contents of the response to refine the orchestration output as required by the parameters in the consuming device or program.

Note:

Orchestration output is available only with version 2 orchestrations created in Orchestrator Studio 5.0.1 or higher. For orchestrations created prior to Orchestrator Studio 5.0.1, you must update them to version 2 orchestrations to view orchestration output.

To work with orchestration output:

  1. On the Orchestration design page, click the Orchestration Output button.

  2. If you want to view the JSON code of all return fields in an orchestration, click Add All.

    The grid displays all of the components or steps in the orchestration that contain return fields, as shown in the following example:

    Description of orch_out_returns.png follows
    Description of the illustration ''orch_out_returns.png''

  3. Instead of Add All, you can individually select the return fields for which you want to preview the JSON code:

    1. Click Add to view a list of all steps (orchestration components) in the orchestration that contain return fields.

      You can expand each step to see the return fields. The Output Field column displays the variable name defined for a return field.

    2. In the Select column, click the check box next to any return field that you want to add to your orchestration output, and then click OK.

      The field will be returned in JSON format, which you can also preview on the design page.

  4. To modify the return fields for which you want to see the JSON representation:

    • You can change the variable name for the return field in the Output column.

    • Click Delete (X) at the end of row to remove a return field from the JSON preview.

    • Click Add (+) to add any additional grid controls not currently selected for output.

  5. Click the Preview button.

    The following image shows an example of the JSON code for three grid return fields: 2nd Item Number, Item Description, and Order Number.

    Description of orch_out_json.png follows
    Description of the illustration ''orch_out_json.png''

  6. In the Preview area, you can click the Copy to Clipboard button so you can paste the JSON code into your program.

  7. (Advanced) In Orchestrator Studio 5.1.0, edit the provided Groovy script template in the Manipulate Output area to manipulate the contents of the response to refine the orchestration output.

    See Groovy Template for Manipulating Output from an Orchestration Response for more information.

  8. Click the Test button to view the output.

    The Orchestrator Studio displays a preview of the output manipulated by the Groovy script.

  9. To save the orchestration outputs, return to the Orchestration design page and click Save.

C.10 Reloading Orchestrations and Orchestration Components

Reload Files enables you to reload orchestrations and orchestration components to the state in which they were last saved in the Orchestrator Studio. Use this feature if you do not want to save any modifications that you made.

To reload all files, click the drop-down menu in the upper-right corner of the Orchestrator Studio and then click the Reload Files link.

Each individual orchestration component panel also contains a Restore button that you can use to restore an individual component.

C.11 Supported Input Message Formats

The Orchestrator supports three input message formats for orchestrations: a standard JD Edwards EnterpriseOne format, a generic format, and Oracle Cloud IoT format. Example C-1 and Example C-2 show an example of the code for each format.

Example C-1 Standard JD Edwards EnterpriseOne Input Message Format

{
     "inputs": [
         {
             "name": "equipmentNumber",
             "value": "41419"
         },
         {
             "name": "description",
             "value": "test"
         },
         {
             "name": "date",
             "value": "1427774400000"
         },
         {
             "name": "time",
             "value": "12:15:15"
         },
         {
             "name": "temperature",
             "value": "99"
         }
     ]
}

Example C-2 Generic or Oracle Cloud IoT Input Message Format

{
      "equipmentNumber": "41419",
      "description": "test",
      "date": "1427774400000",
      "time": "12:15:15",
      "temperature": "99"
}

C.11.1 Additional Supported Input Message Formats for the Generic Input Format

Additional formats are supported when using the generic input format, as long as the orchestration input values are defined using the full path to the elements used. You may have a deeper JSON structure like this.

{
    "equipmentNumber": "41419",
    "equipementDetail": {
        "type": "thermometer",
        "readingDetail": {
            "temperature": 200,
            "units": "F"
        }
    }
}

To reference the temperature within the orchestration, you can use the full path delimited by periods, for example:

equipmentDetail.readingDetail.temperature

C.11.2 Differences Between Input Message Formats

The following list describes the differences between the input message formats:

  • The iterateOver attribute for the orchestrationStep element is supported only by the standard JD Edwards EnterpriseOne input message format.

  • When using the "detail" form action type with the standard format, it will automatically iterate over all detailInputs and repeatingInputs in order to add multiple rows to a grid. If the generic format is used, only a single grid row can be added.

As shown in Example C-3, "detailInputs" would correspond to grid data; "repeatingInputs" would correspond to individual rows that contain "inputs" that correspond to columns.

If you have a power form with two grids, you could populate both grids using two "detailInputs" structures with different "name" values that correspond to the different grids. "repeatingInputs" would contain a list of rows and for each row you would define a list of "inputs".

You could also define a CrossReference orchestration step with iterateOver="GridData" that converts the item value into an EnterpriseOne specific item number. For example, if A123=220 and A124=230, the single orchestration step would convert both.

Example C-3

{
    "inputs": [
        {
            "name": "BranchPlant",
            "value": "30"
        },
        {
            "name": "customer",
            "value": "4242"
        }
    ],
    "detailInputs": [
        {
            "name": "GridData",
            "repeatingInputs": [
                {
                    "inputs": [
                        {
                            "name": "item",
                            "value": "A123"
                        },
                        {
                            "name": "Quantity",
                            "value": "3"
                        }
                    ]
                },
                {
                    "inputs": [
                        {
                            "name": "item",
                            "value": "A124"
                        }
                    ]
                }
            ]
        }
    ]
}

C.12 Setting Up Orchestration Security

Before the EnterpriseOne Orchestrator can process an orchestration, authentication of the JD Edwards EnterpriseOne user ID and password must take place. It is the responsibility of the originator of the service request to tell the orchestration about the user. The user's credentials must be supplied in a basic authorization header or in the JSON body of the request. The user must also have authorized access to the EnterpriseOne application in which the resulting transaction takes place. The following code is an example of credentials in the JSON body of the request:

{
                "username":"JDE",
                "password":"JDE",
                "environment":"JDV900",
                "role":"*ALL"
}

The AIS service used with orchestrations is stateless; each call passes credentials to establish a separate EnterpriseOne session. After the transaction is complete, the session closes.

In addition to passing credentials for authentication, you can employ a second level of security for the Orchestrator through whitelisting. Whitelisting enables an initial rudimentary pass/fail check of the incoming device signature against a predefined list of signatures. A white list provides an additional layer of security to the Orchestrator security. If a value passed to the Orchestrator is not a valid value included in the orchestration's white list, the Orchestrator rejects the input. For more information, see Creating a White List in this guide.

C.12.1 Restricting Access to Exposed Orchestrations

If you expose orchestrations for business partners or customers to invoke, it is recommended to use an http proxy to allow access to only the endpoints required to execute the orchestration. Configure the proxy to restrict all endpoints except /orchestrator, /discover, /tokenrequest, and /tokenrequest/logout. This allows external users set up with the proper UDO security to discover and call orchestrations.

C.12.2 How to Maintain a Single Session for Multiple Calls to an Orchestration

You can maintain a single AIS Server session for multiple calls to an orchestration by first performing a token request to get a session token. Otherwise, each call to an orchestration on the AIS Server establishes a separate session, which can decrease AIS Server performance.

When performing a token request, a session is established and the AIS Server returns an AIS token in the response. The token is then used for all orchestration calls in the same session.

The amount of time the session remains open is established through the session lifetime settings in the AIS server. The third party client is responsible for ensuring a valid token is available or re-requesting a new token once a previous token has timed out. If a valid token is not available, the client will receive an error in the response stating the token is invalid.

C.13 Exporting Orchestration Components from the Orchestrator Studio

Caution:

Do not use the Export and Import tools to share orchestration component files with other users. With orchestration components stored as UDOs in EnterpriseOne, the management of orchestration components, including the sharing and modifying of shared orchestration components and promoting of orchestration components to the appropriate AIS Server directory for test or production purposes, is administered through the life cycle management tools in EnterpriseOne.

You can export any of the orchestration component types from the Orchestrator Studio to view the source XML files of the components. This is only recommended for advanced users for troubleshooting purposes or for making manual customizations. The Orchestrator Studio exports the source XML files in a zip file.

To export an orchestration component, the Orchestrator Studio gives you the option to export only the selected orchestration component or to export the orchestration component and all components associated with it. For example, if an orchestration has a service request component and a rule component associated with it, if you export all components, the zip file will contain XML files for the orchestration, service request, and rule.

To export orchestration components:

  1. On a component design page, select the component to export and then click the Export File button in the upper-right corner.

    If you are exporting an orchestration, a dialog box appears in which you can click All or Orchestration Only.

  2. Follow the instructions in the browser to save the zip file to a location on your local machine.

C.14 Importing Orchestration Files in the Orchestrator Studio

Caution:

Do not use the Export and Import tools to share orchestration component files with other users. With orchestration components stored as UDOs in EnterpriseOne, the sharing and modifying of shared orchestration components, as well as the promoting of orchestration components to the appropriate AIS Server directory for test or production purposes, is administered through the life cycle management tools in EnterpriseOne.

You might need to import orchestration component XML files that were exported from the Orchestrator Studio for advanced troubleshooting or customization purposes. The Orchestrator Studio Import tool enables you to import individual orchestration XML files or a zip file containing XML files.

Caution:

You cannot import orchestration component files that were exported from the EnterpriseOne Object Management Workbench - Web application. The zip file created from an OMW - Web export stores the XML files in a structure that cannot be read by the Orchestrator Studio Import tool.

If importing a zip file that contains orchestration XML files and dependent orchestration component XML files, the zip should contain the following folders with each of the XML files stored in the appropriate folder:

Surrounding text describes importzip_folders.png.

If you import an XML file that has the same name as a current orchestration component (UDO) in the Orchestrator Studio, you have the following options:

  • If the UDO is at a status of "Personal" or "Reserved," you can overwrite the UDO with the XML file.

  • If the UDO is in a "Shared" status, you cannot overwrite it. But you are given the option to import it as a new UDO with a status of "Personal."

To import files:

  1. On the Orchestrator Studio Home page, click the Tools link in the upper-right corner.

  2. On the Tools page, click the Import Files icon.

  3. On Import Files, click the Choose File button.

  4. Locate the orchestration component XML files or zip file that contains the orchestration component files that you want to import.

    After selecting the files to import, the Import tool checks the XML files that you selected against the current UDOs in the Orchestrator Studio and displays the options that are available for importing the files, as shown in the example in Figure C-11.

    Figure C-11 Orchestrator Studio Import Tool

    This image is described in surrounding text.
  5. Review the import option for each file to determine how to proceed with the import. The options are:

    • No update allowed at current status.

      The XML file name is the same as an existing component, which has a status of "Pending Approval," so it cannot be overwritten.

    • Select to add or else reserve record and re-import to update.

      A component with the same name exists in the Orchestrator Studio in a "Shared" status. Click the check box if you want to import the file as a new UDO. A new name will be generated for the new component upon import.

      If you want to overwrite the current component in the Orchestrator Studio, clear the check box. And then change the status of the current component to "Reserved" and reimport the XML file to overwrite the component.

    • File already exists.

      The XML file matches a component that is in a "Personal" or "Reserved" status. Click the check box to import it and overwrite the current component.

    • File is ready to submit.

      The XML file is unique and does not already exist in the Orchestrator Studio. Click the check box to import it.

  6. You can also click the Select All check box to import all XML files that are available for importing.

  7. Click the Submit button.

    The Orchestrator Studio imports the selected components into the components list on the respective design page.