Convert Browser Actions

You can convert Internet Explorer, Google Chrome, and Microsoft Edge actions into new actions for a different browser. This tool converts all of the actions for the browser that you select. To convert individual browser actions, go to Task.

Important: 

  • Internet Explorer was sundowned on June 15, 2022. However, support for using Internet Explorer mode (IE mode) within Microsoft Edge will be available at least through 2029. Because Internet Explorer and IE mode in Microsoft Edge use the same controls, you can seamlessly run existing botflows that interact with Internet Explorer using IE mode in Microsoft Edge. Nintex recommends upgrading to the latest Nintex RPA LE version and converting your Internet Explorer actions to Google Chrome or Microsoft Edge actions.

  • You cannot convert Open App, Open Chrome, and Open Edge actions. You must instead recreate these actions. If you do not recreate these actions, Nintex RPA LE will open the application in the old browser and the targeted actions will not work.

  • Nintex RPA LE will disable the Detect IE action in converted botflows. After your botflows are running successfully, you can delete this action. If you do not delete it, Nintex RPA LE will ignore it.

  1. Click the Tools menu in the top navigation bar.

  2. Select one of the following options:

    • Convert IE Actions to Chrome. All Internet Explorer actions are saved as new Google Chrome tasks and named using the following naming convention: [TaskName] - Chrome

    • Convert IE Actions to Edge. All Internet Explorer actions are saved as new Microsoft Edge tasks and named using the following naming convention: [TaskName] - Edge

    • Convert Chrome Actions to Edge. All Google Chrome actions are saved as new Microsoft Edge tasks and named using the following naming convention: [TaskName] - Edge

    • Convert Edge Actions to Chrome. All Microsoft Edge actions are saved as new Google Chrome tasks and named using the following naming convention: [TaskName] - Chrome

    After making your selection, all of the actions for the browser are converted into new actions for a different browser.

  3. Test your converted actions before executing them.

    Note: If you converted an Internet Explorer action to Google Chrome and it is not finding the target element when you run the action, it may be because Internet Explorer has a SourceIndex property and Google Chrome does not. The converted Google Chrome action has a new NodePath property to attempt replace the SourceIndex property, but this may fail. If it fails, recreate the action for Google Chrome.

  4. Rename your old Internet Explorer, Google Chrome, and Microsoft Edge actions to avoid confusing them with the newly converted actions.