Embedded Files
Add an RPA automation
Here is our plan for this lesson:
Create an Maestro Agentic Process in Studio Web.
Import the .bpmn diagram that you just created.
Trigger a Robot from Maestro workflow.
Learn how process inputs and outputs work.
Let's start by creating a new Agentic Process and import 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: 2-Way Matching Process.bpmn.
The art of keeping your projects organized is rooted in habits — and habits are nurtured through consistent practice.
Generated by an ancient LLM
So, don't forget to reinforce your good habits and clean up your project:
delete the automatically generated empty process ("Process 2312314...")
rename your process into "2-Way Matching Process"
rename project from "Agentic Process" into "2-Way Matching Project"
Unlike static BPMN tools, Maestro allows modeling our diagram, which means execute it by following connections and decisions.
Try to run it by clicking "Test" button, 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 Billing systems that unfortunately have no 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 documents for processing and an external transaction handling mechanism which allows to wait and extract the next Invoice for processing. Automation 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 "Retrieve.Invoice" will simulate retrieving data and generate sample Invoice & PO documents as JSON objects.
To simplify the implementation, we will only look at few fields and Line Items and not all other typical fields like shipping address and delivery dates.
Here is an example of output document which you can get from the Retrive.Invoice automation:
{
"Header": {
"Company Name": "Brasov Logistics SRL",
"Company Address": "Strada Mureșenilor 50, Brașov, Romania",
"Company Registration Code": "RO23456789"
},
"Lines": [
{ "ID": "1", "Product Name": "Standing Desk", "Unit Price": "850.00", "Quantity": "5"},
{ "ID": "2", "Product Name": "Pencil", "Unit Price": "0.20", "Quantity": "30"},
{ "ID": "3", "Product Name": "Organizer", "Unit Price": "50.00", "Quantity": "4"},
{ "ID": "4", "Product Name": "Stapler", "Unit Price": "3.00", "Quantity": "6"}
],
"Details": {
"Subtotal": "4474.00",
"Tax (VAT 19%)": "850.06",
"Total": "5324.06"
}
}
The process has already been configured in Orchestrator in folder 2-Way Matching.
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" as the task's Action type.
Search for Retrieve.Invoice process from the right folder (2-Way Matching) and select it.
Maestro will load inputs and outputs right away.
Don't forget to set some value for in_FailureProbability - this is probability in percent of Invoice not matching the PO.
90 sounds just fine - this way we can go through validation path very often, if you need it. You can change it any time later before publishing.
Next, try launching the Maestro Orchestration Process from Studio Web by clicking "Debug" button. Observe provisioning and execution, then validate that task generates some JSON output. At this step we don't need to worry about configuring any input/output parameters - variables will be automatically created once we use these outputs.
Have a look at the execution details: if you see generated JSON documents - you have completed this second lesson, and it's time to move to next one!
Page updated
Report abuse