Leapwork Documentation

Click Element

The Click Element block is used to simulate a user clicking an element, such as a button or other interactive component, within a D365 F&O web application. It is automatically generated when the user performs a click action during recording.

Note: This block works only in browser windows launched using the Login block or within the current D365 recording session.

When executed, the target element is automatically scrolled into view and clicked using the selected button type.

Fully expanded, the D365 Click Element block shows the following properties:

The Block Header

The green input connector at the top left triggers the block’s execution when the automation flow reaches this step.

The green output connector activates once the click action has been successfully completed.

The block title (“Click <element name>”) reflects the name of the clicked element and can be renamed by double-clicking the header and entering a custom title, useful for better readability when working with longer flows.

Not Found

This green output connector will be triggered if the specified element is not found within the defined timeout period. It is typically used to handle exceptions or alternate paths in the flow.

Source Element

This property can be set if you want the element locator to search only within a specific parent element.

In Early Access versions this setting is not yet configurable.

Browser Window

This field allows the user to specify the browser window instance in which the element should be found.

In Early Access versions, only a single browser session is supported, and this setting is not yet configurable.

Default timeout

If the Default Timeout property checkbox is not selected, then the timeout value is 10 seconds. If the property checkbox is selected, then the Default timeout value selected in the flow settings will be applicable.

Timeout

The maximum time spent extracting the specified information before giving up and triggering the Not Found connector (see above).

Note: All cases have a “global timeout” that can be configured in the “Settings” panel. This is unrelated to the timeout of a single building block. However, a running case will automatically be cancelled if it runs for longer than the global timeout.

Created 22.04.25