It’s not natural to think of tasks so granular, but it’s important to understand how robots process them. An important tool here is a pen and a paper.
Do you find it helps?What other situations require defining steps at such a small level? And, if possible, would you automate them?
For any technical question, or to provide feedback, please create a new topic in our Reboot Your Skill category here.
So far StudioX has been great!
Very nice exercise! Like it!
Good exercise to show the importance of mapping the Robot Path. Precision is key when creating the Bot as it can only do what to “tell” it to and without proper mapping of the process the automation my fail.
Actually it’s quite logical to have the steps as granular as possible, otherwise you will not be able to translate it to a Robot. The example is quite useful, also the Double UI app can help with mimiking the use of an ERP app.
2 posts were split to a new topic: I am not able to capture fields
Every time I complete a task, I get more and more exited. The Robot Path exercise, more than a task was an eye opener. Really cool!!
Thanks for the detailed exercises! Learning more by doing.
This one was really fun, especially since I had to opportunity to go back and try to identify a mistake. I kept looking at the e-mail that did not leave the drafts folder, until I realized I forgot to uncheck the Save to drafts box.