Before You Begin

This 60-minute Oracle by Example (OBE) shows you how to build and test the orchestration.

What Do You Need?

To perform the steps in this OBE, you must have used process recorder to create a Form Request that updates the existing expense report with a new expense and add to an orchestration as explained in the preceding OBE.

Building and Testing the Final Orchestration

1. In Orchestrator Studio, you should already be on the orchestrations page, if not, select Orchestrations from the home page.
2. Click New.
3. Enter the name: OCI receipt to E1 Expense.
4. Click the Start node and select File Inputs tab.
5. Select Process Files Individually.
6. Enter a * in the File Name Pattern.
7. Let the Variable Name default to fileName_0.
8. Enable the Overwrite Existing Files option (so the file name stays the same).
   

   

9. Select the Variables tab, enter these three variables:
   
   1. compartmentId – populate the default value with your OCI compartment ID.
   2. bucketName – populate the default value with the bucket name (in prerequisites).
   3. nameSpace – populate the default value with your OCI namespace.

   

10. Save the orchestration.
11. Double-click the line between the start and end node and select Connector.
12. Enter PUT Object File to find the connector.
13. Click the new connector node and select Transformations.
14. Select the orchestration variables for namespaceName and bucketName.
15. Select fileName_0 for both objectName and fileName.

    

16. Save the orchestration.
17. Test the orchestration so far.
18. You will be using the WalmartReceipt1.jpg image of the receipt for testing, download the image file locally.



19. Double-click the Start node to open the Run Orchestration window.
20. Click the Files button, click the box or drag and drop the WalmartReceipt1.jpg file to send it into the orchestration.



21. Click Run. The orchestration runs, returning a Status OK (200).



22. Open your bucket in OCI, you will see the file uploaded.



23. Close the Run Orchestrations window.
24. Double-click the line after the first step, select Connector.
25. Select OCI Document Key Values.
26. Click the new node, select Transformations and map the following:
    
    • namespaceName= nameSpace(Variables)
    • bucketName = bucketName (Variables)
    • docToProcess = fileName_0
    • compartmentId = compartmentId (Variables)
    • nameSpace = nameSpace (Variables)
27. Click Back on the diagram, and then click the End node and select Outputs and Assertions.
28. Enable the following:
    
    • fileName_0
    • lifecycleState
    • percentComplete (change this to a Numeric value)
    • timeFinished
    • Response Status
29. Save the orchestration.
30. Test the orchestration so far, by opening the Run Orchestration window from the start node.
31. Add the WalmartReceipt1.jpg to the files and click Run. The orchestration runs, returning a Status OK (200).



32. In OCI, view your bucket. You should see a new folder structure with a .json file.
    

    

    If you download the file, you’ll see it has the results of the document understanding API, at the bottom it has identified it as a receipt.
    

    

    The next steps in the orchestration will return these results to use them in the orchestration.

33. Close the Run Orchestrations window.
34. Double-click the line before the end node and select Logic Extension, select Build Object Name.
35. Click the new node and select Transformations. Map the inputs as follows:
    prefix = prefix
    id = id
    namespace = nameSpace
    orig_bucket = orig_bucket
    orig_name = orig_name
    

    The Available Values are outputs for the OCI Document Key Values, except for nameSpace (variable).

    

36. Click the orchestration End node and select Outputs. Enable the objectName in the outputs.
    

    

37. Save and test the orchestration again. The objectName should have a value similar to this example, but with your bucket name (that is jde-oci-documents). The following screenshot shows the path to the .json file we saw above.
    

    

38. Close the Run Orchestrations page.
39. Double-click the line before the end node, select Connector, then select Get Key Value Object JSON.
40. Click the new node and select Transformations. Map the following:
    

    

41. Click back to the diagram, click the end node and select Outputs.
42. Enable all the values from the new step and rename them as necessary. The following screenshot shows the values used to complete the tasks in this OBE:
    

    

43. Save the orchestration and test again. The output should now include details found in the receipt, the result of the Document Understanding service.
    

    

44. Close the Run Orchestrations window to continue building the orchestration.
45. Double-click the line before the end node and select Connector.
46. Select OCI Delete Object. Now that the receipt has been evaluated the orchestration will delete it from the bucket.
47. Click the New node and select Transformations. Map the following:
    namespaceName = namespace
    bucketName = bucketName
    objectName = filename_0
    

    

48. Double-click the line before the end node and select Logic Extension.
49. Select ExtractFieldValues.
50. Map the transformations, matching the two values from outputs of the Get Key Value Object JSON.
    

    

51. Click the end node and select Outputs.
52. Add the values from the two new steps (changing names as needed). The following screenshot shows the values used to complete the tasks in this OBE:
    

    

53. Save the orchestration and test again. The output should include a status (204) for delete and the three values from the receipt.
    

    

54. Check your bucket in OCI, the receipt .jpg file should no longer be there.
55. Close the Run Orchestrations window to continue building the orchestration.
56. Click the start node and select Inputs and Values.
57. Add two inputs:
    • expenseReportNumber, Numeric (set the default value to the expense report you created)
    • expenseCatagory, String (set the default to MISC)
    

    

58. Double-click the line before the end node and select Orchestration.
59. Select AddExpenseToReport.
60. Map the transformations as follows, with the number and category returned from the inputs and the expense date, amount, and merchant returned from ExtractFieldValues step.
    

    

61. Enable the output of report number for the new step in orchestration outputs.
    

    

62. Save the orchestration and test again. The report number should show in the output.
    

    

63. Now return to EnterpriseOne, Expense Entry.
64. Find and select your report. A new line should be added with the date and amount from the receipt.
    

    

65. Click the MISC link for the line to open the record and view the Additional tab. The merchant’s name (Walmart) should be in the record.
    

    

66. The orchestration successfully used the OCI Document Understanding service to gather details from a receipt and those values were entered into an EnterpriseOne expense report.