Click

Estimated reading: 3 minutes 89 views

The activity allows users to interact with applications by clicking on specified target elements.

Properties

INPUT

DelayAfter: It assists the user to add a delay before initiating subsequent activities in milliseconds. By default, it is set to “300” milliseconds. When the option is left blank, the delay will not be considered.

DelayBefore: It assists the user in adding a delay before starting the execution of the activities in milliseconds. By default, it is set to “200” milliseconds. When the option is left blank, the delay will not be considered.

ExecuteBy: *Automatically populated after selecting the Active Application. It contains a set of attributes associated with the specific detected element.

WaitTime: It enables the user to introduce a delay before initiating subsequent activities in milliseconds.
By default, it is set to 10000 milliseconds. Leaving the option blank will result in no delay being applied.

Action_by / Perform: Specifies how the action on the detected element will be executed.

Native: The action is performed in the background once captured in the spy window (default option).
Human: The action is performed as if a human is interacting with the element after it is detected.

Mouse_buttonSpecifies which mouse button to use for the click action.

1. When Native is selected in Action_by, the default action is used and cannot be changed.
2. When Human is selected, you can choose the button:

a. LeftClick: Performs a left-click.
b. RightClick: Performs a right-click.
c. MiddleButton: Performs a middle-click (scroll button) action.

MISC

Click Type: Determines the type of click action to perform on the element.

When Native is selected in Action_by, the default click action is used and cannot be changed.

When Human is selected, you can choose the click type:

Single Click: Performs a single click on the element.

Double Click: Performs a double click on the element

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”
True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

RESULT

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”
True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

* Represents mandatory fields to execute the workflow.

Share this Doc

Click

Or copy link

CONTENTS