Welcome > Workflow > Business processes > Design a basic process > Add an activity > Activity types > Kofax activities > RPA activity > Configure an RPA activity

Configure an RPA activity

  1. Add an activity to the map.

    By default, the Configuration tab is open in the properties panel of the activity.

  2. Change the default Name of the activity to something meaningful.
  3. On the Type list, select Kofax > RPA.
  4. Configure the following properties.

    Server

    The RPA server to use.

    A list of projects available from the selected RPA server appears on the Project list .

    Project

    The project to use.

    A list of robots from the selected project appears on the Robot list.

    Robot

    The Robot to use. A robot is an automated workflow designed to accomplish a task involving a data source, such as a website, or an Excel document, or a database

    The parameters from the selected robot appears in the Configure RPA activity dialog box.

  5. To map values to the parameters, click Configure for Parameters.

    The Configure RPA activity dialog box displays the RPA details for the server, project and robot and also the parameters from the selected Robot.

  6. To map input and return values to the parameters, do the following:
    1. Select a dynamic value (process variable, server variable or click provide an inline value for input value.
    2. Select a dynamic value (process variable or server variable) or provide an inline value for return parameter.
    3. Click OK to return to the activity configuration.
  7. Save the process map.

    • When you export or import the process, the RPA activity configuration and the reference to the RPA server used in the activity are included in the XML.

    • When you import the process on another system, and a RPA server with the same name already exists, that server is used when executing the activity.

    • When you import the process on another system, and the server does not exist, the server name is displayed as "Unknown" and execution fails because the RPA server is not defined.