How to Use the Asset in a Production Robot

Help Orchestrator
1

Hi,

I’m trying to run a package on the PROD tenant, which was taken from the UAT tenant (and UAT was originally obtained from the Dev tenant).

In my workflow, I’m using 12 assets for credentials and API endpoints. The asset values differ across Dev, UAT, and PROD environments. Since I have an Automation Developer License, I was able to set up Studio and create the same asset names with different values in Orchestrator for Dev and UAT.

However, in PROD, I only have a Production Runtime License, not a Developer License. This means I can only install UiPath Assistant, not Studio.

Here’s what I did in PROD:

  • Created a Folder in Orchestrator.
  • Uploaded the package (which was taken from UAT).
  • Attempted to run the automation, but it failed due to missing assets.

I tried creating the assets inside the folder, but my workflow get assets referencing the Orchestrator path as my workspace (xxx@xxx.com's workspace), which doesn’t match the folder-based asset structure in PROD.

My Questions:

  1. How can I use assets in the PROD environment without a Developer License?
  2. Should I be using UiPath Studio in the PROD environment, or is there an alternative?
  3. Is there a way to configure asset paths in my workflow to work correctly in PROD?

Any guidance would be greatly appreciated. Thanks in advance!

2

Hey @manjula_rajendran the Assets you are creating in your workspace .so it will only accessible for that user so . so if you want to use you asset make sure to create a Folder in the tenant .and assign that machine and assign the robot also that folder.so when you run your process it will access that folder and get the asset.
NOTE: My workspace is only for personal use for prod you have to create a folder and give access rights on it.

cheers

3

I’ve created the “PROD” folder and assigned robot account and machine. I cannot assign the role “Robot” as it is not listing in my Roles.

The image shows a user interface where an "unattended" username is assigned the "Administrator" role among other selectable roles. (Captioned by AI)
The image shows a user interface where an "unattended" username is assigned the "Administrator" role among other selectable roles. (Captioned by AI)762×426 21.5 KB

4

Hey @manjula_rajendran generally it shown after the admin role but enable that Administrator role and then try to run it.

5

I’ve already assigned and it is working fine for simple automations where there is no assets. I’ve only problem for assets.

The image shows the "Settings" page in UiPath Orchestrator with options to manage access, view machines, and assign roles under the "PROD" tenant. (Captioned by AI)
The image shows the "Settings" page in UiPath Orchestrator with options to manage access, view machines, and assign roles under the "PROD" tenant. (Captioned by AI)1322×383 58.5 KB

As you can see, i’ve My workspace in that i’ve created assets and linked to PROD folder still it don’t work. getting error “Status code: 400 (Bad Request). Orchestrator response:
Folder does not exist or the user does not have access to the folder. Error code: 1100” This error may be because i’m using this tenant for Robot Account only not for user.

6

Hey @manjula_rajendran as you can see the the error message
Folder does not exist or the user does not have access to the folder.
means only the user means can access the My workspace folder you trying to run it in PROD so you create a robot and also setup a machine right so that robot is basically not associate with the my workspace folder.so when you process is run and bot is trying to access My workspace folder it not access to that folder.means you have to create the asset in a folder where bot is access when run in unattended mode. for example if you create that asset in prod folder and assign that robot in that folder then it can access.and could you show me the process where you are trying to read the asset .using get asset activity

7

Hi @manjula_rajendran,

In cases like this, where folders that you are using for dev, uat, prod are different, its a good idea to provide orchestrator folder name in the Get assets activity.

In case, when this is left empty, bot would automatically pick assets form the folder where process is running, but if in your dev env, you had provided a value in there for orchestrator folder, and then when you run that process in prod, it won’t run as it is trying to refer that same folder.

image
image373×187 4.16 KB

You can also refer below thread for same:

Regards
Sonali

1 Like
8

I found the solution from this link

I just need to leave blank in the orchestrator path.

A configuration window for getting credentials in an orchestrator, showing fields for folder path and credential asset name. (Captioned by AI)
A configuration window for getting credentials in an orchestrator, showing fields for folder path and credential asset name. (Captioned by AI)496×278 3.81 KB

9

For clarification: leaving the folder blank means it will get assets, queues etc. from the folder the automation is running in. Meaning moving your automation also requires movig (or linking) your assets to the new folder.

It also comes with the benefit that you can run the same automation over different folders each sing the same asset names, but different values without the need to use messy input parameters.

10

Just put all the assets in Shared, not a folder

11

For the best practice you should use use the shared folder or you have to create a specific folder where you can create your assets queues your process..and then you will use that asset .because in the near future if you create another asset in my workspace so how bot will know that it will choose that particular Asset.
cheers

12

I don’t see the Shared folder and while creating also i don’t see any option to select Shared folder.

As my process is not using the queue I’m continuing with the option of adding the assets to folder and leaving orchestrator path blank.

1 Like
13

Hey @manjula_rajendran

image
image200×287 19.1 KB

might be your admin did not give you the access of Shared folder thats why you can’t see that folder. so you can ask with the admin where you guys want to store that assets.
but if your process is in PROD folder so you have to store that assets also in PROD Folder .
cheers

1 Like
14

if your query is been resolved then close this by mark as solution

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.