Creates a complex mouse action on an element or a position of the web page.

This statement allows to trigger complex mouse events, provided that attributes of the accessed DOM element manage such events.
Supported mouse events, defined in the Action property, are the following:

• click: simulates a mouse click event,
• mousedown: simulates a mousedown event (first part of a mouse click event, when mouse button is clicked),
• mouseup: simulates a mouseup event (second part of a mouse click event, when mouse button is released),
• mouseover: simulates a mouseover event (mouse is moved onto an element),
• mouseout: simulates a mouseout event (mouse is moved out of an element),
• mousemove: simulates a mousemove event (mouse is moved anywhere),
• mousedrag: simulates a mousedrag event (mouse drags an object),
• dblclick: simulates a dblclick event (mouse double-clicks an object),
• dragdrop: simulates a dragdrop event (mouse drags and drops an object).

The XPath defined in XPath property is applied on the web page to retrieve the element on which the event has to be performed. If the XPath property is empty, the mouse position can be used to find an element on which perform the event.
The mouse position can be defined using the Client X and the Client Y properties or the Screen X and the Screen Y properties.
Note: For simple actions, prefer to use the Mouse action statement.

Property Type Category Description
Action String standard Defines the JavaScript action corresponding to the event to perform.
Depending of the statement, this property can take several values. These values are indicated in the object’s description.
Button JS expression standard Defines which mouse button is used during the mouse event.
Some mouse events are triggered by the depression or release of a mouse button. This property is a JavaScript expression that is evaluated during the transaction execution and indicates which mouse button is used during this state change.
This property can take the following values:

• zero: left button,
• one: middle button, if applicable,
• two: right button.

For mouse devices configured for left-handed use, in which button actions are reversed, values are reversed too (from right to left).
Client X JS expression standard Defines the client (web browser) relative X coordinate (in pixels).
This property is a JavaScript expression that is evaluated during the transaction execution and gives the horizontal coordinate, relatively to the top left corner of the DOM layout, at which the event should occur.
Client Y JS expression standard Defines the client (web browser) relative Y coordinate (in pixels).
This property is a JavaScript expression that is evaluated during the transaction execution and gives the vertical coordinate, relatively to the top left corner of the DOM layout, at which the event should occur.
Comment String standard Describes the object comment to include in the documentation report.
This property generally contains an explanation about the object.
Delay if XPath not found long standard Defines the maximum delay the statement waits if the XPath doesn’t currently exists.
When no node in the page DOM matches the XPath defined in XPath property, the statement waits for it to match up to this delay, set in milliseconds.
Convertigo tries to evaluate the specified XPath while receiving a web page or executing JavaScript in it. Once the XPath matches at least one node of the page, the statement continues its action.
Note: It is equivalent to defining a statement Wait synchronization with an XPath synchronizer before this statement, waiting for the same XPath.
Is active boolean standard Defines whether the statement is active.
Press alt key JS expression standard Defines whether the “alt” key is to be depressed when firing the event.
This property is a JavaScript expression that is evaluated during the transaction execution as a boolean defining if the alt key should be depressed when firing the event.
On some platforms, the alt key may map to an alternative key name.
Press ctrl key JS expression standard Defines whether the “ctrl” key is to be depressed when firing the event.
This property is a JavaScript expression that is evaluated during the transaction execution as a boolean defining if the ctrl key should be depressed when firing the event.
On some platforms, the ctrl key may map to an alternative key name.
Press meta key JS expression standard Defines whether the “meta” key is to be depressed when firing the event.
This property is a JavaScript expression that is evaluated during the transaction execution as a boolean defining if the meta key should be depressed when firing the event.
On some platforms, the meta key may map to an alternative key name.
Press shift key JS expression standard Defines whether the “shift” key is to be depressed when firing the event.
This property is a JavaScript expression that is evaluated during the transaction execution as a boolean defining if the shift key should be depressed when firing the event.
On some platforms, the shift key may map to an alternative key name.
Screen X JS expression standard Defines the absolute screen X coordinate (in pixels).
This property is a JavaScript expression that is evaluated during the transaction execution and gives the horizontal coordinate, relatively to the top left corner of the screen, at which the event should occur.
Screen Y JS expression standard Defines the absolute screen Y coordinate (in pixels).
This property is a JavaScript expression that is evaluated during the transaction execution and gives the vertical coordinate, relatively to the top left corner of the screen, at which the event should occur.
XPath JS expression standard Defines the XPath expression of elements on which the statement applies.
Depending on the statement, the execution of this XPath on the web page DOM can result in a single Node or a NodeList.
Synchronization TriggerXMLizer expert Defines how to synchronize the statement.
A synchronizer states how and when accessed pages are considered fully loaded. Only then are data extracted and new pages re-detected.
There are several types of synchronizers, that are described hereafter:

• Document completed: The synchronizer waits for a number of documents to be completed. Specify here how many “document completed” events Convertigo has to wait for before assuming that the page is complete. In many cases, when the target application uses HTTP META redirects or JavaScript redirects, the document is loaded several times. You can monitor
==== start parse ======
and
==== Parse end ==(XXXms )====================
traces in the Engine console (debug mode) to count the number of “document completed” events needed for the synchronizer. The Document completed synchronizer can be configured to also stop on alert messages that could pop up. Alert messages do not trigger a “document completed” event and are not detected by this synchronizer. To activate this option, check the Stop on alert checkbox.
• XPath: The synchronizer waits until a specified XPath is found. Convertigo tries to evaluate the specified XPath while receiving a web page or executing JavaScript in it. Once the XPath matches at least one node of the page, the synchronizer returns.
• Wait time: The synchronizer waits until a specified time is reached (in ms, set via the Timeout property).
• Screen Class: The synchronizer waits for one of the selected screen classes to be detected. Several screen classes can be selected to be waited for. The synchronizer returns when one of them is reached.
• Download started: The synchronizer waits for a download request. This is the perfect synchronizer to use before a Get attachment statement.
• No wait: The synchronizer doesn’t wait and execution proceeds directly.

For all synchronizer types, the maximum waiting time is set using the Timeout property.