Input actions such as clicking or typing (setting), are always performed directly in an open application. Because these applications sometimes require different input methods, you can choose between the input methods Api Call, Element Coordinates, and Window Message.
By default, the method is always set to Api Call. However, you can change this setting in the properties of the activity.
Clicking
| Method | Description | Compatibility | Speed |
|---|---|---|---|
| Api Call | A mouse simulation from automation libraries. Depending on the automation provider, it executes a click element using the respective APIs. | 80% | 100 |
| Element Coordinates | Performs a visual click in the specified coordinates. First, the mouse cursor moves to the specified location, then it performs the simulated event. | 100% | 50 |
| Window Message | Simulates mouse or keyboard events. In this activity, window messages simulate mouse input elements in the form of an internal message to the Windows system. | 80% | 50 |
Typing
| Method | Description | Compatibility | Speed | Auto Empty Field |
|---|---|---|---|---|
| Api Call | A Windows API keyboard simulation. It uses functions to insert
events into mouse or keyboard input streams. It is generally useful
when working with the Windows operating system. Note: Sending keystrokes in RDP sessions like
Citrix will not work with this method. Use AutoIt or
VirtualKeyboard for that.
|
80% | 100 | Yes |
| Focus And Send Keys | 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. | 100% | 50 | Yes |
| Window Message | The Windows operating system uses a message passing model. We try to simulate this model by using Window Message to simulate 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 systems. | 80% | 50 | Yes |