Great explanation on the difference between RPA and other types of automation. I think this type of educational content might not only alleviate some people's concerns about automation and the workforce but also drive business owners and organizations to make an informed decision regarding automation.
How are these tools different from traditional test automation tools? Though test automation tools traditionally only focused on automating test scenarios... Can those not be used for automating the processes mentioned in this seminar?
RPA is definitely the future, but what is RPA all about? Why and where should we use RPA? Here’s an article that breaks it all down. Hope it helps you! www.engati.com/blog/what-is-robotic-process-automation
Is a good video and does "touch on" much has to do with the individual's mind set when programming the bot. A large Co used to have an "automated system" with one of the features being able to say "customer service" to shift to a human. In the "Bot Driven" approach, the option was taken away. Concern was too many will just bypass, so they removed the option. Calling in to let them know their lines had been spoofed by scammers and to expect a lot of complaint calls. Not an option for "other". Too funny. It will hurt them and... I am not real sorry about it. If there is an "emergency" (real one, not perceived or fake) then where will they get the notification? Short sighted. Need to figure in the "ok, now what do we do as this is none of the options"? It is the number they have posted everywhere but.... hmmm... a little more thought to what else might come in on those lines.
I've watched plenty videos and read plenty articles on RPA and I'm still not getting this. This is highly inefficient for CPU usage. It locks down the PC or virtual machine that it leveraging this tech so they are single threaded. Most of these don't allow for cloud usage so you have to have those cold machines just sit there when not being used. All of this can be automated in the backend with data transfers and transformation. This is gimmicky as hell.
Perhaps the anthropomorphized approach fits better into existing organization structures? It's hard to explain "backend with data transfers and transformation" to an MBA enough for them to comprehend it, let alone take responsibility for directing it. But running a bot run on a local machine is a lot like looking over the shoulder of a human worker, so maybe peoples' existing skills/experience can transfer to effectively leveraging these "virtual employees".
Great explanation on the difference between RPA and other types of automation. I think this type of educational content might not only alleviate some people's concerns about automation and the workforce but also drive business owners and organizations to make an informed decision regarding automation.
Very well explained. So far the best video I came across for RPA beginners.
Very nice video on RPA
Super ...So this is RPA ...Well done , a great explantion ...5th point is missing in Process Robotics....It took my salary as well and left me dry
Very well explained, thank you.
So this is where Richard Hendricks went after Pied Piper.
Excellent!!
Good Presentation !!
Aaha, well narrated
How are these tools different from traditional test automation tools?
Though test automation tools traditionally only focused on automating test scenarios... Can those not be used for automating the processes mentioned in this seminar?
Kind of. Same tools but different packaging. You'll need to turn it into a product fit for enterprise process automation. Meaning UX, permissions etc.
RPA is definitely the future, but what is RPA all about? Why and where should we use RPA? Here’s an article that breaks it all down. Hope it helps you!
www.engati.com/blog/what-is-robotic-process-automation
Thank you!
Very clear! Thanks :)
AIMBOT!!
Great Video , thanks for sharing this information in a form of video with us , Know more about RPA follow Technogeeks
If it worked Microsoft would use it effectively themselves :)
Is a good video and does "touch on" much has to do with the individual's mind set when programming the bot. A large Co used to have an "automated system" with one of the features being able to say "customer service" to shift to a human. In the "Bot Driven" approach, the option was taken away. Concern was too many will just bypass, so they removed the option. Calling in to let them know their lines had been spoofed by scammers and to expect a lot of complaint calls. Not an option for "other". Too funny. It will hurt them and... I am not real sorry about it. If there is an "emergency" (real one, not perceived or fake) then where will they get the notification? Short sighted. Need to figure in the "ok, now what do we do as this is none of the options"? It is the number they have posted everywhere but.... hmmm... a little more thought to what else might come in on those lines.
I've watched plenty videos and read plenty articles on RPA and I'm still not getting this. This is highly inefficient for CPU usage. It locks down the PC or virtual machine that it leveraging this tech so they are single threaded. Most of these don't allow for cloud usage so you have to have those cold machines just sit there when not being used.
All of this can be automated in the backend with data transfers and transformation. This is gimmicky as hell.
Perhaps the anthropomorphized approach fits better into existing organization structures?
It's hard to explain "backend with data transfers and transformation" to an MBA enough for them to comprehend it, let alone take responsibility for directing it. But running a bot run on a local machine is a lot like looking over the shoulder of a human worker, so maybe peoples' existing skills/experience can transfer to effectively leveraging these "virtual employees".
ภาษาตัวเล็กมากมองไม่ชัด
STM32hzcube A.I.,,,, automation machine (humans)& automation environment machines,,& automation machine (robotics, robot s)2020a.d.,,, United Nations space force---
let's dirupt RPA to protect our job lol