A web table definition defines the columns in a table that a robot must interact with.

Learn more: Web Table Definitions

Consider a robot that gets invoice numbers from a table that lists all invoices that meet specific criteria. You identify the table using a web table definition.

When you add a web table action to a robot and select a web table definition, Oracle Integration creates a variable for saving the table information.

Variables

A variable holds data temporarily for a robot so that you can use the data somewhere else.

Learn more: Variables

Consider the get text action, which obtains text from a field. You can hold the value in a variable. Additionally, if the text value is an output for the robot, you can use the variable as an output property.

Input

An input defines the data that comes into a robot, typically when the robot starts running.

Learn more: Triggers

Consider a robot that needs to update a purchase order. An integration obtains the purchase order number and passes it to the robot as an input property. You dynamically define the input properties in a map action in an integration. You can also define these values when you test a robot outside an integration.

Output

An output defines the data that comes out of a robot. You can dynamically pass the output data elsewhere, such as to another robot, integration, or action in an integration.

Learn more: Triggers

Consider a robot that obtains the total value of a purchase order. The robot can pass the total value into an output, which an integration can use to take further action.

A page state is a container for one or more validation checks. A validation check occurs before or after an action in a robot.

Learn more: Page States

Consider an application that experiences latency issues during periods of high usage. Without validation checks, a robot that runs in the application could fail if the robot attempts to complete a task before the required fields and buttons are visible. Validation checks ensure that all fields and buttons are visible and enabled on a page before a robot attempts to complete its task. These checks increase the likelihood of a robot completing its tasks successfully.

Targets

A target identifies the HTML element that a robot interacts with. Every target has two components: a user-friendly name, and the hard-coded XML path language, or XPath.

Learn more: Targets

Targets help with maintenance. Consider a robot that interacts with the same HTML element multiple times. Oracle Integration creates a target for the element and can reuse the target for each interaction. Therefore, if the HTML for a page changes, all you need to do is update the target one time, and all of the robot's interactions with the element are updated.

A data type defines how data should be classified.

A data type is the basis of every variable, output property, and input property. You can use one of the default data types provided by Oracle or a custom data type that you create.

Learn more: Data Types

Consider a robot that must update a set of invoices. You can create a data type that defines the components of invoice data, such as invoice number, invoice amount, supplier name, and due amount. Next, you can create a input of the data type, and use the trigger to pass this information into the robot.

Robot connections

A robot connection lets you store sensitive data, such as sign-in credentials, outside a robot for easier maintenance.

Learn more: Robot Connections

In order for a robot to sign in to an application, you must provide a user name and password. However, an administrator needs easy access to this information so they can update the password according to your organization's security policies. Thanks to a robot connection, this sensitive information lives outside a robot, so you can update it easily outside the lifecycle of the robot.

Inputs and outputs contain one or more properties. Define the properties, including specifying their data types and whether they hold a single value or an array of values, when you create the trigger.

You don't define a value for an input or output because a trigger is a container for its properties. Additionally, you can't hard code values for the properties. Instead, you dynamically pass in values for each input and output property.

Create an input or output in a robot, either when you define the trigger of a robot, or at any time on the canvas.

Page states contain one or more validation checks for a robot action. A validation check uses a target to reference a specific UI control, such as waiting until a button is visible on a page.

Create an input or output in a robot, either when you define the trigger of a robot, or at any time on the canvas.

Oracle Integration creates targets for you when you select an element for the robot to interact with while building a robot, either using the recorder or the low-code tools.

Create a target when you add an action to a robot, or at any time on the canvas.

Your settings determine whether Oracle Integration reuses targets for previously selected UI controls. You can override these settings, if needed. Reusing a target offers benefits. For example, you can update a target one time, and all actions that use the target get the update.

A data type can contain one or more properties.

Oracle Integration provides several predefined data types, including string, boolean, and number.

You can define additional data types as needed, including defining their properties.

A robot connection contains one or more parameters. Define hard-coded values for the parameters when you create the robot connection. You cannot pass in values to a parameter.

Additionally, a robot connection and its parameters live outside a robot, so you can update the parameter values without updating a robot.

Create a robot connection in a project.

Use the value of a parameter when you define a robot action.