Activate a Robot

After you finish building a robot, activate it. Afterward, you can test and run the robot.

Requirements for Activation

If version 1.0.0 of a robot is active, you can't make version 1.0.1 or version 1.1.0 active. However, you can make version 2.0.0 active. Or, you can deactivate version 1.0.0 and then activate 1.0.1 or 1.1.0.

The same rule persists as you increase version numbers. If version 2.0.0 is active, you can't make version 2.0.1 or version 2.1.0 active. However, you can make version 3.0.0 active. Or, you can deactivate version 2.0.0 and then activate 2.0.1 or 2.1.0.

Prerequisites

Before you activate a robot, you must complete the following steps:

Activate a Robot

  1. Open a project.
    1. In the navigation pane, select Projects.
    2. Select the project name.
  2. In the left toolbar, select Robot Robot.
  3. Consider updating the open browser action so that the robot runs in a headless browser.

    Be aware that a robot typically has improved performance when it runs in a headless browser.

  4. In the Robots box, ensure that the robot's state is Configured.

    A robot has a Configured badge in the Robots box

    If the robot isn't in a Configured state, you haven't met all the prerequisites for activation. See Specify Where a Robot Runs and Fix a Robot's Errors.

  5. In the Robots box, point to the Configured robot, select ..., and select Activate.

    The Activate robot panel appears.

  6. Choose the appropriate tracing level for the robot.

    See Tracing Levels for Robots and Allow Screenshot. To understand how the different options for tracing levels impact each other, see Options for Tracing Levels.

  7. Select Activate.

    A Confirmation pop-up appears, and the state changes to Activation in progress.

    A robot has an Activation in progress badge in the Robots box

  8. Navigate to another area of the application, and then return to the project to check the robot's state.

    Within a minute or two, the robot's state changes to Active.

    A robot has an Active badge in the Robots box

    Robot in Active status

Next, you can test the robot on its environment. See Test a Robot on Its Environment.

Tracing Levels for Robots

Choose the right tracing level for your robot: either production, audit, or debug.

The following table identifies the type of information that is included in the activity stream for each tracing level.

Tracing level Example Includes a summary of the activity Includes all activity messages with unmasked contents (XPaths) Includes the input and output of activities "Allow screenshot" is selected by default

Production

Sample activity stream entry for production-level tracing

 Yes No No No

Audit

Sample activity stream entry for audit-level tracing

 Yes Yes Yes No

Debug

Sample activity stream entry for debug-level tracing with Allow screenshot selected

 Yes Yes Yes Yes

Allow Screenshot

When you choose a robot's tracing level, specify whether to include screenshots in the activity stream using the Allow screenshot checkbox.

Tip: A robot that captures screenshots sometimes runs a little slower and captures more data than a robot that doesn't capture screenshots. Therefore, many people select Allow screenshot for Debug tracing and deselect it for Production tracing.

Setting Do screenshots appear in the activity stream for screenshot actions?
Screenshot action
 Do screenshots appear in the activity stream when "Before this action" or "After this action" is selected?
Before this action and After this action are selected

Allow screenshot is selected

Allow screenshot is selected

Yes

See Add a Screenshot Action.

Yes

See Capture Screenshots in Robots.

Allow screenshot is not selected

Allow screenshot is not selected

Yes

See Add a Screenshot Action.

No

The Allow screenshot setting overrides the Before this action and After this action settings.

See Capture Screenshots in Robots.

Options for Tracing Levels

You have many options for setting tracing levels. Understand how each option affects a robot.

Option for specifying a tracing level Does this option affect a robot? More information

Project deployment

When activating a project deployment

Yes

This setting overwrites the robot-level setting. Therefore, if you activate a robot and then activate a project deployment that contains the robot, the robot uses the tracing level that you set for the project deployment.

See Activate or Deactivate a Project in Using Integrations in Oracle Integration 3.

Integration activation

When activating an integration

 No

This setting affects only an integration and doesn't affect a robot's tracing level, even if the integration calls a robot.

See Activate an Integration in Using Integrations in Oracle Integration 3.

Integration update

After activating an integration

 No

This setting affects only an integration and doesn't affect a robot's tracing level, even if the integration calls a robot.

See Manage Tracing Levels on Integrations in Using Integrations in Oracle Integration 3.

Robot activation

When activating a robot

Yes

This setting determines the tracing level for a robot, unless you override it when you activate a project deployment.

See Activate a Robot.

Robot update

After activating a robot

Yes

This setting determines the tracing level for a robot, unless you override it when you activate a project deployment.

See Activate a Robot.