Using the Laserfiche Bot Recorder with Google Chrome

If you are working with the latest version of Laserfiche Bots, you will be prompted to launch a new browser window when recording actions in Google Chrome. Allowing the bot to interact with newly launched browser windows avoids a variety of potential complications.

Note: After you've finished recording your bot, add a Launch application activity (in the bot designer) to have the bot open a new Chrome browser window when it runs. Bots cannot interact with already open Chrome browser windows; only windows the bot has opened itself.

If you want to record in a Chrome browser window that's already open, you can configure Chrome's remote debugger port through the bot local tool.

  1. Open the bot local tool from the Windows Start menu.
  2. Right-click the bot icon in the system tray menu, and select Configure Google Chrome.
  3. Ensure Chrome's remote debugger is using port 0. Learn more.

If you configured Chrome to work with a previous version of Laserfiche Bots, you must update the remote bugger to use port 0. You must update the port even if you used the automatic configuration tool in the latest version.

To update the remote debugger port

  1. If they are open, close the bot recorder and Action History by right-clicking the bot icon in the system tray area of the taskbar, and selecting Exit.
  2. Open Google Chrome's properties wherever users open Chrome from (e.g., desktop shortcut, start menu, tool menu, etc.). Generally, properties can be accessed by right-clicking the Chrome icon and selecting Properties.
  3. In the Google Chrome Properties dialog box, navigate to the Shortcut tab.
  4. In the Target text box, add a space after the last quotation mark and paste:

    5. --remote-debugging-port=0

    ClosedShow me what this looks like.

    Location and contents of the Google Chrome target.

    Note: If you've changed the port number Laserfiche Bots uses, then replace 0 with the updated port number. Note that if multiple users on the same machine have the same port configured, the bot may not run correctly.

  5. Click OK.
  6. Restart the bot recorder, by adding a recording in the bot designer.
  7. Ensure all instances of Chrome are closed, and then restart Chrome.