Defining Files as Orchestration Input (Release 9.2.6)

You can provide a file or files directly as orchestration input and you can choose to process the files individually or as an array. You can use the file content in many ways after you add the file content as an input to the orchestration. You can write a custom script to read and parse the contents of the file for use in subsequent orchestration steps, or pass the content as input to an external system in an outbound REST connector, or upload the file to EnterpriseOne as a media object attachment.

The Files(0) button is enabled in the Run Orchestrations window for orchestrations that have a defined file input, and you can upload the files.

To define a file as an input to an orchestration:

1. On the Orchestrations design page, click the Start node.

   The action control icons are displayed above the Start node.

2. Click the Inputs and Values icon.

3. Click the File Inputs tab.

4. Select from these options:

   1. No File Inputs: This option is selected by default.

   2. Process Files Individually: Select this option to process the files individually.
      1. Enable the Overwrite Existing Files option to use the original file name for all the files throughout the processing. Disable this option to assign a unique file name to each file.

      2. Enable the Keep Temp Files option to save the files in the root temporary directory for an indefinite period of time. If you disable this option, the files will be saved in the user’s session temporary directory and all the files will be deleted when the session ends.

      3. To define an individual file name pattern, enter a name in the File Name Pattern field and select the required content type from the Content-Type drop-down menu. The system automatically displays the values in the Variable Name field as fileName_0, fileName_1, and so on. You can override the system generated values in the Variable Name field.

         For example, if you enter the file name patterns as order* and detail*, and select the content type as application/pdf and image/jpeg, respectively, the orchestration will accept only two files, one is a file with a name starting with order that has a content type of application/pdf, and the other is a file with a name starting with detail that has a content type of image/jpeg. The system will display an error message if you try to add any file with a name that is not starting with order or detail, or if you add a file other than the specified content type.

         You can enable the Required option to mark a file as required and click the Delete icon to delete a file name pattern.

         
      Note: The system displays a blue dot on the File Inputs tab to indicate that the files are defined for orchestration input.

   3. Process Files As An Array: Select this option to process an iterative array of files.

      1. Enable the Overwrite Existing Files option to use the original file name for all the files throughout the processing. Disable this option to assign a unique file name to each file.

      2. Enable the Keep Temp Files option to save the files in the root temporary directory for an indefinite period of time. If you disable this option, the files will be saved in the user’s session temporary directory and all the files will be deleted when the session ends.
      3. In the File Array Name field, enter an array name.
      4. Select a value from the Content-Type drop-down menu. If you leave this field blank, you can process the files with any content type.
      5. Enable the File Array Required option to mark the file array as required.
5. You can now access the Run Orchestrations window, and click the Files(0) button to drag and drop, or browse and upload files. The system updates the number next to Files in the button title depending on the number of files you upload. For example, if you upload two files, the button name is displayed as Files(2). Click the Run button to process the input files and verify the results in the Output tab.
   Note: In the Run Orchestration window, the Content-Type field displays the value as multipart/form-data by default, when file inputs are defined in the orchestration.

> quick tour: Click here to view a recording of this feature.

> oracle by example: Click here to view an OBE of this feature.