Send Value

The Send Value action An instruction within a botflow. sends a value to a target An element within an application Nintex RPA LE interacts with, such as a button, text field, or checkbox., such as a text box. Using this action, you can:

  • Send text data to a text editor.
  • Send shortcut keys to a target.
  • Send a Ctrl+C command to copy information.

Some examples of target applications for the Send Value action using the Target Selector are:

  • Microsoft Excel spreadsheet cells.
  • Nintex Forms.
  • Browser windows.

Jump to: 

Add a Send Value action to a botflow

  1. Drag the Target Selector from the Build Pane Area to add new actions and edit existing actions. The Build Pane displays after you select a targeted element in a Windows application. The center of the Build Pane is referred to as the Task Editor Pane. and drop it onto an application to display the Target Preview.
  2. Select Send Value from the Data actions list.
  3. Enter the value to Send to the target application.

    4. See the Send Value settings for more information about:

    • Hide Value: Hides the sent value.
    • Bypass the keyboard: This setting displays when the target resides in a browser window.
    • Click before sending: Clicks the target before sending the data to the target.
    • Tab after sending: Sends a Tab command after the value is sent.

    • Change case: Changes the sent value to Upper, Lower, or Proper case.
    • Remove spaces: Removes Leading, Trailing, or All spaces from sent values.

    • Mode: Sets the mode of the sent value.
    • Speed: Sets the speed of the sent value.
    • Keystroke delay: Sets the automatic delay of the speed of the keyboard in milliseconds.
    • Use Virtual Key Codes: Allows the application to receive the physical key on which a user strikes on the keyboard to produce the results on the screen.

  4. If needed, adjust the Rule settings to modify how Nintex Bot finds the application target.
  1. If needed, adjust the Run Error Task settings and Timing settings to fine tune how the action runs.
  2. View the action Details settings.
  3. If needed, adjust the Run Switch setting to create the action without running it.
  4. (Optional) Add an action note.
  5. Click OK to add the Send Value action to the botflow Automated steps that you can design for each bot that will run..

Send Value Action field and button descriptions

Field or button Description
Target Selector

The Target Selector 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 Target Selector:

  • 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 Target Selector 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 Target Selector from the Task Pane 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. The Build Pane displays after you select a targeted element in a Windows application. The center of the Build Pane is referred to as the Task Editor Pane..

Smart Target and Screen Target options

The Target 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.

Target Selector
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

Access the most recent target by clicking the Recent Target button to the right of the Target 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
Send Value Options/Settings General
  • Send: Enter the value to send to the target application. Optionally, use the Expression Builder to build the action settings using variables or other token values.

    Tip: If you want to send repeating keystrokes to the target application, use the Expression Builder to create them in a string fashion (for example, [^Tab][^Tab][^Tab]), or if they are the same keystroke, add an index (for example, [^Tab(3)]). If you add an index to send repeating keystrokes, you can manually type the entire keyboard input string or you can place your cursor inside the square brackets and then click the same keyboard value repeatedly.

  • Hide Value: Hides the sent value, such as a password. The value will be protected using Advanced Encryption Standard (AES), as described in Encryption Standards. Once encrypted the value can't be changed.
  • Bypass the keyboard: This setting displays when the target resides in a browser window. This setting can increase the speed of your botflow when supported by the target application.

    • Note: Nintex Bot sends data to a field using the keyboard. Bypass the keyboard sends the information without the physical keyboard. Some applications only respond to changes submitted by an actual keyboard. These applications will not support Bypass the keyboard. To determine if your target application supports this feature, perform the action and confirm that changes have been made.

  • Click before sending: Clicks the target before sending the data to the target. Use when the target application requires focus to the target before sending data, such as when then target application requires first putting the cursor into a text box before typing into that text box.
  • Tab after sending: Sends a Tab command after the value is sent. Some target applications require a tab out of a field before the data is saved.

Format

  • Change case: Changes the sent value to Upper, Lower, or Proper case.
  • Remove spaces: Removes Leading, Trailing, or All spaces from sent values.

Keystrokes

  • Mode: Sets the mode of the sent value.
    • Overwrite: Clears any existing text in the target before sending the value.
    • Append: Moves the cursor to the end and adds the value to the end of the existing value.
    • Insert at Front: Moves the cursor to the beginning and adds the value to the beginning of the existing value.
    • None: Does not clear the existing value. The value is sent to the location of the target's cursor.
  • Speed: Sets the speed of the sent values.
    • Auto: Recommended
    • Very Fast
    • Fast
    • Medium
    • Slow
    • Very Slow
    • Slowest: A noticeable pause precedes keystrokes that are sent at an extremely slow rate.

      • Note: When the keyboard Speed is set to Auto, Nintex Bot attempts to adapt the keystroke speed to the target application. It automatically knows when the target application is ready for the next character to be sent. Navigational keys (such as Tab, Enter, and Right Arrow) are sent using Nintex Bot smart speed technology, causing botflows to be more reliable. A consistent delay is added between each keystroke when using the Very Fast, Fast, Medium, Slow, Very Slow, or Slowest speed. Slowest speed causes a noticeable delay between keystrokes that are sent at an extremely slow rate and is needed in rare cases.

  • Keystroke delay: This setting is only available when the keyboard Speed is set to Auto. Using numbers, variables, or data fields, enter the milliseconds (1 to 9999) to delay the keyboard. This feature is useful when you have a target that is sensitive to how and what is being sent to it and it will block what it does not recognize, or it will erroneously acknowledge valid input as invalid.

  • Use Virtual Key Codes: This setting is only available when the keyboard Speed is set to Auto. It allows the application to receive the physical key on which a user strikes on the keyboard to produce the results on the screen. For a list of virtual key codes, see this Microsoft article. This feature is useful when you have a target that is sensitive to how and what is being sent to it and it will block what it does not recognize, or it will erroneously acknowledge valid input as invalid.

Preview: Shows the exact value that will be sent to the target.
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. The Build Pane displays after you select a targeted element in a Windows application. The center of the Build Pane is referred to as the Task Editor Pane. or Action Builder Provides access to the tools needed to add and modify actions or instructions within a botflow. Located on the left side of the Nintex Bot window. .

    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 Target 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 Target Selector 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.