Create Asset activity

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

Configure the Create Asset activity

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

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v7.0 Software Update 2 or higher.

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
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?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the UiPath RPA tab.
On the UiPath RPA tab, drag the Create Asset activity onto your process.

General Configuration

Specifies the basic settings for the Create Asset activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
Display Name	Description: Specifies the activity name that shows in your process. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts 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	Description: Specifies an optional text description for your activity. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No

Field Name

Definition

Display Name

Description:

Specifies the activity name that shows in your process.

Allowed Values:

One line of text (a string).

Accepted:

Letters
Numbers
Spaces

Default Value:

None

Accepts Variables:

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

Description:: Specifies an optional text description for your activity.
Allowed Values:: More than one line of text.
Default Value:: None
Accepts Variables:: No

Create Asset Configuration

Specifies the information to create an asset in UiPath.

Fields

Field Name	Definition
UiPath	Description: Specifies the access token that connects to your UiPath service. Allowed Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for UiPath Function of this Screen: Configure an access token to connect to UiPath.
Folder	Description: 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. Allowed Values: A UiPath folder name from the list. Default Value: None Limitations: This field is available in these releases: AgilePoint NX OnDemand (public cloud) AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v8.0 or higher
Single Value / Per Robot	Description: Specifies whether all robots in UiPath can access the asset. Allowed Values: Single Value - All robots can access the asset. Per Robot - The specified robot can access the asset. Default Value: Single Value Accepts Variables: No
Asset Name	Description: Specifies the name of the asset to create in UiPath. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: Yes
Type	Description: Specifies the type of the asset to create. Allowed 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	Description: 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: On the Create Asset Configuration screen, select Per Robot. Allowed Values: A UiPath robot from the list. Default Value: None Accepts Variables: Yes
Value	Description: Specifies the value for the asset. To Open this Field: On the Create Asset Configuration screen, in the Type field, select one of these types: Text Boolean Integer Allowed 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 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	Description: Specifies the user name for any account to store in the asset. To Open this Field: On the Create Asset Configuration screen, in the Type field, select Credentials. Allowed Values: A valid user name. Default Value: None Accepts Variables: Yes
Password	Description: Specifies the password to store in the asset. To Open this Field: On the Create Asset Configuration screen, in the Type field, select Credentials. Allowed Values: An alphanumeric string that represents a password. Default Value: None Accepts Variables: Yes
Add	Function: Adds a row for a robot. To Open this Field: On the Create Asset Configuration screen, select Per Robot.
Delete	Function: Deletes the row. To Open this Field: On the Create Asset Configuration screen, select Per Robot.
Store Response in this Variable	Description: Specifies the process data variable that stores your asset ID from UiPath. Allowed Values: A process data variable that accepts an alphanumeric string with no spaces or special characters. Default Value: None Accepts 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?