Advanced UI Interaction 2.2
98.5 هزار بار بازدید -
8 سال پیش
-
What you’ll learn in this
What you’ll learn in this video:
Input actions are the ones where you, or in this case the robot, take some direct actions on the application or web page you’re automating: things like clicking, typing, keyboard shortcuts, and so on.
Output actions are those actions that get information OUT of the app, and into UIPath for further processing. They are not recordable because all apps are made for humans, whose main output method is reading the results on a display. UiPath has various methods for simulating all the actions that a human can make, and we’ll look at them in detail.
There are 3 main INPUT methods:
1. Default. The default method uses the mouse and keyboard drivers to simulate a human operating them. It’s the method that works every time, but with a few downsides, like speed and the requirement to have the application active. So it’s a good idea to start with this method to make sure everything works, and then change it to one of the other 2 methods.
2. Simulate Type. The fastest, but there are limitations of this method, that can be solved by adding a GetText before the Type into method and appending your text to it.
3. Window Messages. Converts all text to lowercase. Also the slowest.
Output methods:
1. FullText is the default method, and it’s the best one for most situations. It’s fast, accurate, and works in the background.
2. The Native method has the advantage of being able to extract word data, like the screen coordinates of each word or character.
3. OCR. As you may know, in general, OCR technology is not 100% accurate, but it does work as a last resort in the situation where none of the other direct methods give us the intended results.
https://www.uipath.com/automate/gui-a...
Input actions are the ones where you, or in this case the robot, take some direct actions on the application or web page you’re automating: things like clicking, typing, keyboard shortcuts, and so on.
Output actions are those actions that get information OUT of the app, and into UIPath for further processing. They are not recordable because all apps are made for humans, whose main output method is reading the results on a display. UiPath has various methods for simulating all the actions that a human can make, and we’ll look at them in detail.
There are 3 main INPUT methods:
1. Default. The default method uses the mouse and keyboard drivers to simulate a human operating them. It’s the method that works every time, but with a few downsides, like speed and the requirement to have the application active. So it’s a good idea to start with this method to make sure everything works, and then change it to one of the other 2 methods.
2. Simulate Type. The fastest, but there are limitations of this method, that can be solved by adding a GetText before the Type into method and appending your text to it.
3. Window Messages. Converts all text to lowercase. Also the slowest.
Output methods:
1. FullText is the default method, and it’s the best one for most situations. It’s fast, accurate, and works in the background.
2. The Native method has the advantage of being able to extract word data, like the screen coordinates of each word or character.
3. OCR. As you may know, in general, OCR technology is not 100% accurate, but it does work as a last resort in the situation where none of the other direct methods give us the intended results.
https://www.uipath.com/automate/gui-a...
8 سال پیش
در تاریخ 1395/05/07 منتشر شده
است.
98,515
بـار بازدید شده