1. Orchestrator Guide
  2. Exporting Orchestration Components from the Orchestrator Studio

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 of orchestration components, the modifying of shared orchestration components, and 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 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.

(Release 9.2.5) The Orchestrator Studio exports the source XML files in a zip file which is then saved with the name of the UDO.

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

To export orchestration components:

  1. On a component design page, select Export File from the Manage drop-down menu.

    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.