Recently we shifted to running Unattended on that same PC and after the first of the year, we'll be shifting to a VM. But then things like Windows upgrades and power outages and other stuff always seem to make the session die. This is how we first started with RPA in that I just had a PC up and running in the corner that was always logged into the account. You can run attended but that means that you have to turn off session timeouts and logouts on your Windows session so that the original session for the RPA is always available. I'm not even sure that last part is true. What we have figured out is that "bot" for unattended RPA is a magical combination of a VM and an Environment (mostly an Environment) and only one bot running at a time. So attended vs unattended licensing is really not very clear. Specialist - Service Management Analytics
Can anyone help me understand what a bot is in this case ? Is it the one service account or is it each RPA flow that i run under this service account? I may have to cancel my subscription if the Attended RPA license won't accomplish what i need, so any information you can provide would be great. My question to all you experts is can this be done with a "Per User Attended RPA License" or do i need an "Unattended Addon" ? The Per User attended RPA License is 40$ per month while the Unattended add on is 150$ a month per bot. I want to put these RPA Flows on a schedule to automatically run weekly, monthly etc. Most of my RPA Flows involve the bot logging into SAP, running an SAP transaction, exporting the data to excel and saving the excel output to SharePoint. I have several RPA processes under this service account using Power Automate Desktop. This machine is logged into using it's own service account credentials.
My IT team set me up a windows 10 virtual Machine.
0 kommentar(er)
