Embedded Files
Add an RPA automation
Here is our plan for this lesson:
Create a Maestro Agentic Process in Studio Web.
Import the .bpmn diagram that you just created.
Trigger a Robot from the Maestro workflow.
Learn how process inputs and outputs work.
Let's start by creating a new Agentic Process and importing the BPMN diagram we created in the previous lesson.
In the Studio Web home page click on Create New button and select Agentic Process. This will create a new project for our Agentic Orchestration workflow that will perform Invoice and PO matching.
Create a new project in Studio Web
Now let's import our BPMN diagram. Open Project Explorer, right-click on the Agentic Process and click Import BPMN.
Select the .bpmn diagram that you have exported in the previous lesson or use this one:
The art of keeping your projects organized is rooted in habits — and habits are nurtured through consistent practice.
Generated by a wise ancient LLM
So, don't forget to reinforce your good habits and clean up your project:
delete the automatically generated empty process ("Process.bpmn")
rename your solution and process into "2-Way Matching Solution" and "2-Way Matching Process".
Unlike static BPMN tools, Maestro allows modeling our diagram, which means execute it by following connections and decisions.
Try to run it by clicking "Debug" button in the upper left corner, and then understand why it went the way it went. It should look like this:
Transaction data retrieval
Transaction data retrieval
In our scenario, company processes hundreds of Invoices per day, ranging from Office Supplies and Computer Equipment. Data is stored in ERP and Accounts Payable or billing systems that unfortunately not always have APIs or database access, and therefore RPA automation using UI interaction is the only way to extract that data.
Let's assume that there is a queue of Invoices for processing and an external transaction handling mechanism which allows to wait and extract the next Invoice for processing. Automation retrieves Invoice, extracts data from PDF, then finds and retrieves associated original Purchase Order that was sent to Supplier originally. It outputs details of both documents in JSON format for our Agentic Automation to process.
RPA Process called "RetrieveInvoiceDocument" will simulate retrieving data and output sample Invoice as a PDF File. It will also point to file name in Storage Bucket.
Here is a sample invoice document that you might get from the RetriveInvoiceDocument automation. Quite standard.
The process has already been configured in Orchestrator in folder "2-Way Matching IXP".
Get familiar by giving it a run and explore it's inputs and outputs.
Once you have validated that process has everything to run, let's go back to Studio Web and update our Task:
Open the properties panel by clicking on the task
pick "Start and wait for RPA workflow" in the task's Action type.
Search for RetrieveInvoiceDocument process from the right folder (2-Way Matching IXP) and select it.
Maestro will load Inputs and Outputs for this RPA automation right away.
Don't forget to set some value for in_FailureProbability - this is probability in percent of Invoice not matching the PO. Value 90 sounds just fine - this way we can go through validation path very often, as long as you need it. You can change it any time later before publishing final version.
Next, try launching the Maestro Orchestration Process from Studio Web by clicking "Debug" button. Observe provisioning and execution, then validate that task generates correct output. At this step we don't need to worry about configuring any input/output parameters - variables will be automatically created for subsequent steps.
Have a look at the execution details: if you see a file name - you have completed this second lesson, and it's time to move to next one!
Page updated
Report abuse