Hover Mouse

The Hover Mouse action An instruction within a botflow. hovers the mouse over a target, such as an application or browser page, for a specified amount of time. You can use this action to hover the mouse pointer above a specific element in your target.

Some examples of applications you can use as targets for the Hover Mouse action using the Selector tool are:

  • Browser-based web applications
  • Controls that show another set of options
  • Menu commands and navigation

Note: The Hover Mouse action can also be created in a Mouse Sequence using the Record Mouse tool.

Jump to: 

Add a Hover Mouse action to a botflow

  1. Drag the Selector tool from the Build Pane Area to add new actions and edit existing actions. and drop it onto an application to display the Target Preview.
  2. Select Hover Mouse from the Mouse actions list.

    3. The Action Builder window for Hover Mouse displays.

  3. To set the Hover Mouse action settings, enter a numeric value to adjust the hover time.
  4. If needed, adjust the Rule settings to modify how Nintex RPA LE finds the application target.
  5. If needed, adjust the Run Error Task settings and Timing settings to fine tune how the action runs.
  6. View the action Details settings.
  7. If needed, adjust the Run Switch setting to create the action without running it.
  8. (Optional) Add an action Note.
  9. Click OK to add the Hover Mouse action to the botflow.

Hover Mouse action field and button descriptions

Field or button Description
Selector Tool

The Selector Tool allows you to choose the target element the botflow interacts with, such as a button, text field, or check box.

Ensure that your machine's Windows Settings (Start Menu > Settings) are set as follows when using the Selector Tool:

  • Windows Display Scale and layout set to 100% (Settings > System > Display).
  • Windows Display Make text bigger set to 100% (Settings > Ease of Access > Display).

You can use the Selector Tool to:

  • Click a button in an application.
  • Send information to a web page or Windows application.
  • Copy information from a web or Windows application.

Drag the Selector Tool from the Task Pane Area to create and manage actions within a specific task. onto the desired application target An element within an application Nintex RPA LE interacts with, such as a button, text field, or checkbox. and select the appropriate action from the Build Pane Area to add new actions and edit existing actions..

Smart Target and Screen Target options

The Selector can be used with the Smart Target or Screen Target options. The options are displayed as shown in the image below. Smart Target is selected by default.

  • Smart Target: Smart Target sets the target based on the selected element and is used to reliably and most accurately locate and interact with the element.

  • Screen Target: Screen Target sets the target based on a specific fixed X/Y coordinate on the entire screen. Use this as a potential alternative to target an element when the application’s element can't be targeted with a Smart Target due to application limitations. For example, target a cell within a table that can not be selected with Smart Target or use it to target an image in a screen by getting the X/Y position of the image as a variable to click on.

Selector Tool
Build Pane

The Build Pane displays after you select a targeted element in a Windows application. In the Build Pane, you can:

Selected target elements display in the Build Pane with a list of actions supported by the targeted item. The Build Pane also displays how long the item has been targeted.
Recent Target

The most recent target may be accessed by clicking the Recent Target button to the right of the Selector.

This is useful when creating Excel, Emulator, and Web Table Targets allowing you to create new actions with existing targets.
Field or button Description
Hover Mouse Options/Settings

General

  • Hover (secs): Type a numeric value to adjust the hover time, use the up/down arrows to increase/decrease the numeric value, or use the Expression Builder to build the action settings using variables or other token values.
Rules

Some actions have rules required to locate a target and vary based on the targeted application. Rules of a targeted application element are configured and saved with the action. The rules are then used to locate the proper targeted element, such as a Microsoft Excel workbook. Other notes about rules:

  • Some targets provide no rules.
  • Most targets provide at least the text of the target, such as 'Log in' for a log-in screen action.
  • Some targets provide a name to identify the target (a unique developer-defined control name).
  • Some targets provide an ID (a unique identifier that locates an item based on how it appears in the target).
  • Some rules include parents to aid in finding the targets.
  • All targets use the following rules:
    • Ignore: Ignores the value of the selected rule.
    • Exact Match: Uses an exact match when considering the value of the rule.
    • Best Match: Uses a best match when considering the value of the rule and uses a variety of information to locate the target.
    • Left Match: Uses leading characters when considering the value of the rule based on a specified number of leading characters.
    • Right Match: Uses trailing characters when considering the value of the rule based on a specified number of trailing characters.

To set up the most common rules:

  1. Click Rules on the Build Pane Area to add new actions and edit existing actions. or Action Builder Provides access to the tools needed to add and modify actions or instructions within a botflow. .

    2. The Rules window displays the rules available for the selected targeted application.

  2. Select Use Smart Targeting to enable smart targeting with up to six rules. With this feature, you can:

    • Select to Ignore or find an Exact Match for rules.

    • Click the arrows next to the rules to change the order and priority in which the rules are followed. After the target has been found, the rest of the rules are ignored.

    • Manually edit rules. This is an advanced feature should only be used if you know how Google Chrome queries work.

    • If tables can be bridged, select Yes or No next to Table Bridge to turn on or off this feature. Bridging web table searches allows you to search, move highlight, get list, and complete other actions across multiple tables on a web page that have the same number of columns. It also improves targeting on web pages and apps (for example, in Salesforce and Navigator).

    • If you want to enable legacy smart targeting rules, select Apply Fallback Legacy Targeting. This option allows you to enable old targeting rules when the Nintex Bot selector fail to find the target. Nintex Bot will fail the action instead of using the Best Match rule. The default is deselected.

  3. Adjust the available rules, as required.
  4. Select Ignore Invisible Elements to turn on a legacy targeting rule that ensures that Nintex Bot only considers visible elements (elements that can be seen) and disregards all invisible elements (elements that have "visible:hidden" and/or "display:none" style properties) during action execution. When selected, this setting disregards all cached/invisible elements in the dom as these elements can be the original target (the target element used to create the action). Selecting this setting can improve reliability during the action execution when interacting with elements that look identical but are actually overlaid. Note that this feature is only available for targeting using Google Chrome technology (Google Chrome and Microsoft Edge).
  5. Click OK to save the rules.
Preview All actions created using the Selector tool include a preview of the targeted element.
Details

When directed by Nintex Support, click Details from the Preview Panel of the Action Builder. If needed, Nintex Support will supply additional information.
Timing Settings

Some actions have timing settings and vary based on the targeted application. The timing settings of a targeted application element are configured and saved with the action. The timing settings are then used to control when the action starts.

  1. Click Wait up to 1 sec.
  1. Open the Time drop-down list and select the required setting:
    • Do not wait: Immediately attempts to execute the action and applies any error settings or rules.
    • Wait up to: Waits up to one (1) second to execute the action per any configured rules. The time specified is the wait time prior to continuing the botflow. In the event of an application being unavailable, the action adheres to the error settings. Time units include numeric settings for seconds, minutes, and hours.
    • Wait forever: Waits until the target application is in a ready state and applies any error settings or rules.
  1. Click X to close the drop-down list and save the setting.
Run error task
  1. Click Run error task.
  2. Open the On Error drop-down list and select the required setting:
    • Run error task: A botflow containing an error task automatically runs the error task in the event of an error. If the botflow does not contain an error task, the botflow stops in the event of an error.
    • Stop on error: The botflow stops in the event of an error.
    • Ignore errors: The action is skipped in the event of an error and the botflow attempts to execute the next action.
  1. Click X to close the drop-down and save the setting.
Note

(Optional) Type a Note to document any special instructions or functionality.    
Run Switch

The Run Switch toggle controls how Nintex Bot runs an action when adding or editing an action in a botflow.

  • Run: To run the action automatically when you click OK, switch the toggle to Run.

  • Don't Run: If you do not want to run the action automatically when you click OK, switch the toggle to Don't Run.
OK/Cancel Click OK to save the action or click Cancel to discard the action or any changes.