Hi all, first if this is the wrong section then I’m sorry. I couldn’t find a better place.
My issue is the following:
I have created a very simple Maestro-project which should do the following: When an item is added to a SharePoint-list I want to write an element to a queue.
So my Maestro flow contains the following:
A Start Event
A Task Event with the Wait for connector event → List Item Added Trigger.
So my problem is that I cannot for the life of me get this to work using Combination ID. I have used the Microsoft Graph Explorer to find ID’s of both my SharePoint-site and the SharePoint-list. But no matter what I paste in I get “No options”.
The format I have used is guid-for-site|guid-for-list
I can choose my SharePoint-site just fine from the dropdown:
This doesnt seem like a good use case for Maestro.
Maestro has a cost per job, unlike a classic unattended robot, and its not cheap.
I am not sure if I can publicly discuss the pricing at this stage, but using Maestro for things like this will get very expensive, very fast.
I’d suggest doing this with a classic automation project made in Studio.
Yes I know, this project was just for testing purposes. Our company makes extensive use of SharePoint and SharePoint-lists, which is why I wantet to just test it as we have a free trial now.
But thank you for warning about the cost, I agree one has to be careful with the “pay-as-you-go” model as costs will rack up pretty quickly. We yet have to find a good business-case for Maestro.
Fair enough, as long as you know that you are covered and makes sense as a test.
Can I suggest you make this basic flow with the integration service trigger etc in Studio desktop, as a familiar environment, to get your bearings and make sure the concept works and all your connections etc work, then you can switch to Maestro and try to reproduce, in this manner you should have a better grasp of if its a ‘bug or feature’ since you know what should be working and what might not be cause of other issues?
I didn’t realize the cost is per job. I had high hopes for Maestro enabling more overview and control in our normal unattended transactional processing, but if it’s like this, that’s not doable. It might only be worth it now for long-running, complex workflows where to volumes are low. That’s a shame for us
Ja, I assume you have seen the pricing information for Maestro by now and I agree it is impossible to make a justifiable business case for it since you can already do most of what Maestro offers, without Maestro, however I think not everyone knew what was possible with Process Orchestration in Studio making the pricing point very weird.
I’ve given examples directly back to UiPath regarding since I first saw the pricing back in April and tried to demonstrate how if I use the examples given by them as great Maestro cases, it will always end up costing more than processing manually, often doubling operating costs if you include any agent units etc and considering development fees can triple first year costs and then deliver a -100% saving each year…
It has some nice features, and I like the dashboard, but I cannot justify the cost.
If they just enable use setting the Reference on a Job (which is already a property on a Job if you look at the API) and display that in the Jobs overview, that would do most of what is needed to get a better grasp on Orchestration processes.
