Welcome to Kofax RPA > Design Studio > Migrate a Robot to a Different Browser Engine

Migrate a Robot to a Different Browser Engine

Kofax RPA uses a browser to interact with web sites or web applications. Kofax RPA currently comes with two different browsers, each optimized for different purposes: the Classic engine for legacy web applications and the Default (WebKit) engine for modern web applications. However, these browsers might not be compatible with every internal application or Internet web site. If you encounter problems using any of the browsers, you can migrate your robot to other browser type in the Design Studio using the following procedure.

Migrating a Robot to the Classic Browser

  1. Right-click a robot in the tree view and select Migrate.
  2. Select files that you want to migrate, such as robots and snippets and click Next.
  3. Specify whether to backup your files, select the backup method and click Finish on the Backup step.

    After Kofax RPA migrates your robot, you can see that the color of the robot icon has changed.

    Note When migrating a WebKit robot that has steps with legacy waiting criterion, this waiting criterion is converted to "Wait real time for timer events" and "Max wait for time out."

Migrating a Robot to the Default Browser

  1. Right-click a robot in the tree view and select Migrate.
  2. Select files that you want to migrate, such as robots and snippets and click Next.
  3. Specify whether to backup your files, select the backup method and click Finish on the Backup step.

    After Kofax RPA migrates your robot, you can see that the color of the robot icon has changed.

    Note When migrating a robot from the Classic to the Default browser engine, the robot is checked for the "Wait real time for timer events" or "Max wait for time out" settings in the robot configuration. If the settings are found, Design Studio shows a warning that these configuration settings will be lost during the migration. This is applicable only to the robot configuration. If any step has the "Wait real time for timer events" or "Max wait for time out" settings, they will be converted into a legacy waiting criterion.