Input actions such as clicking or typing (setting) are always executed directly within an open application. Since these applications sometimes require different input methods, you have the option to choose between three different types of input methods.
Clicking
| Method | Compatibility | Speed |
|---|---|---|
| ApiCall | 80% | 100 |
| Element Coordinates | 100% | 50 |
| WindowMessages | 80% | 50 |
ApiCall is a mouse simulation from automation libraries. Depending on the automation provider, it performs a click element using the respective APIs.
ElementCoordinates performs a visual click in the given coordinates. First, the mouse cursor will move to the specified location, then it will perform the simulated event.
OS Windows uses a message-passing model. We simulate this model using Windowmessage to simulate mouse or keyboard events. In this activity, window messages simulate mouse input elements in the form of an internal message for the Windows system.
Typing
| Method | Compatibility | Speed | Auto Empty Field |
|---|---|---|---|
| ApiCall | 80% | 100 | Yes |
| Focus and Send Keys | 100% | 50 | Yes |
| Window Messages | 80% | 50 | Yes |
ApiCall is a keyboard simulation from windows api. It uses functions to insert events into mouse or keyboard input streams. It is useful in general when working on OS Windows. Note that sending keystrokes in RDP sessions like Citrix will not work with this method. For this use AutoIt or VirtualKeyboard.
FocusandSend keys is a way to send a text. This method is an extension of ApiCall, before generating the keystroke, it sets the focus in the target element where the text should be inserted.
OS Windows uses a message-passing model. We try to simulate this model by using WindowMessage for simulating mouse or keyboard events. In case of this activity, window messages simulate setting text to the elements in the form of an internal message for windows system
Per default, the method is always set to ApiCall. But it can be changed inside the properties of the activity.