Create Asset activity

An activity that creates an asset for one or more robots in UiPath.


Create Asset activity

Configure the Create Asset activity

To configure the Create Asset activity, do the procedure in this topic.

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In the Process Builder, in the Activity Library, open the UiPath RPA tab.

    Open UiPath
  3. On the UiPath RPA tab, drag the Create Asset activity onto your process.

    Drag Create Asset

General Configuration

Specifies the basic settings for the Create Asset activity.

Figure: General Configuration screen

General Configuration screen

Fields

Field Name Definition

Display Name

Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
No
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Create Asset Configuration

Specifies the information to create an asset in UiPath.

Figure: Create Asset Configuration screen

Create Asset Configuration screen

Fields

Field Name Definition

UiPath

Function:
Specifies the access token that connects to your UiPath service.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None

Create Add Token icon

Opens this Screen:
Access Token for UiPath
Function of this Screen:
Configure an access token to connect to UiPath.

Folder

Function:
Specifies the name of the folder in which to create an asset.

When you select the access token from the UiPath field, this field shows the folders associated with the access token from UiPath.

Accepted Values:
A UiPath folder name from the list.
Default Value:
None
Limitations:

This field is available in these releases:

Single Value / Per Robot

Function:
Specifies whether all robots in UiPath can access the asset.
Accepted Values:
  • Single Value - All robots can access the asset.
  • Per Robot - The specified robot can access the asset.
Default Value:
Single Value
Accepts Process Data Variables:
No

Asset Name

Function:
Specifies the name of the asset to create in UiPath.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
Yes

Type

Function:
Specifies the type of the asset to create.
Accepted Values:
  • Text - An asset that stores a text strings with no quotation marks.
  • Bool - An asset that stores a true or false value.
  • Integer - An asset that stores integers.
  • Credential - An asset that stores usernames and passwords that the robot requires to execute specific processes.
Default Value:
Text

Robot

Function:
Specifies the name of the robot that can access the asset to execute the processes.

When you select the access token from the UiPath field, this field shows all the robots in UiPath associate with the access token.

To Open this Field:
  1. On the Create Asset Configuration screen, select Per Robot.
Accepted Values:
A UiPath robot from the list.
Default Value:
None
Accepts Process Data Variables:
Yes

Value

Function:
Specifies the value for the asset.
To Open this Field:
  1. On the Create Asset Configuration screen, in the Type field, select one of these types:
    • Text
    • Boolean
    • Integer
Accepted Values:
  • If you select Text in the Type field, this field accepts more than one line text.
  • If you select Boolean in the Type field, this field accepts True or False.
  • If you select Integer in the Type field, this field accepts an integer.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Username

Function:
Specifies the user name for any account to store in the asset.
To Open this Field:
  1. On the Create Asset Configuration screen, in the Type field, select Credentials.
Accepted Values:
A valid user name.
Default Value:
None
Accepts Process Data Variables:
Yes

Password

Function:
Specifies the password to store in the asset.
To Open this Field:
  1. On the Create Asset Configuration screen, in the Type field, select Credentials.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Accepts Process Data Variables:
Yes

Add Add icon

Function:
Adds a row for a robot.
To Open this Field:
  1. On the Create Asset Configuration screen, select Per Robot.

Delete Delete icon

Function:
Deletes the row.
To Open this Field:
  1. On the Create Asset Configuration screen, select Per Robot.

Store Response in this Variable

Function:
Specifies the process data variable that stores your asset ID from UiPath.
Accepted Values:
A process data variable that accepts an alphanumeric string with no spaces or special characters.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?