How do I Pass Parameters to Processes run using Attended or Studio Robots

Hello Community!

  • I have a Process that is capable of taking Input parameters via Main.xaml
  • I execute this process via my UiPath Assistant manually
  • However, I have the following issue - Let me explain the steps, and you can correct me if I’m off someplace

Step 1: I login to Orchestrator Cloud CE and select my process >> View Process

Step 2: I update the Input parameters and Save the changes

Step 3: Next, I refresh the UiPath Agent on my laptop and Run the process

Process executes successfully- but here’s the problem! :warning:

The output logs show that my Process has executed using default design-time parameters and not the ones that I configured in Step 2!

How then do I pass input arguments to attended processes? :thinking:


1 Like

The values that you set on Orchestrator only can be used when start job on Orchestrator or call API.
In Step 3, you run the process from UiPath Agent, so Agent cannot retreive your values

1 Like

this orchestratr version can`t supported Attenend and studio robots,

only use the Unattended robot.

To input arguments to attended processes, you have to use command line to start the process, not Uipath Agent
Please refer below link ( --input <Input_Parameters>)

1 Like

It’s better if Uipath update Uipath Agent to allow user setting parameters like Orchestrator, right?

1 Like

Yes it would be nice. Most folks who run attended Robots in an Enterprise are not developers. Asking them to tinker with any kind of command lines would be difficult if not impossible. I work in Finance related IT, and asking business users to run such attended automation will not be a great selling point.


I added this request to User Voice
Please Vote to raise it to UiPath


I figured that out after I converted my Studio Robot to a UA robot. But I don’t follow how I can ask my business users to run attended automations that are based on certain manual and highly sensitive inputs. Saving files to their local laptops or shared drives is not an option. :pensive:

Here’s the use case:
Users will open applications that are accessible by Multi-Factor authentication .

Then they will access screens that are visible only to them.

They copy one or more values and then provide them to the robot. Robot executes certain calls on an application we have access to and completes the workflow.

You see the issues. The authentication by itself doesn’t make this process fully automated.
And there’s no way we will have direct access to their finance applications.

In case of Attended, you can prompt a pop-up for user input his values.

Yes, that is an option. But I would also kindly ask you to consider the following factors as well:

Just because a solution is technically feasible, doesn’t mean that it can be implemented everywhere. These depend on the industry, the backgrounds of the people who own the business and development practices laid out across IT teams.

Example: A few weeks ago, the proposal to disable Multi-factor authentication for a certain internal web application that we wanted to automate was shot down . Our security team didn’t even want to consider it as an ask.

I can go in and put in pop-up boxes much against the developmental guidelines that we follow. But that will never be acceptable for use by a group of business users who largely operate the business through a system of cloud-based applications.

And most importantly, people who hold the purse strings to sign off on purchases of software such as UiPath.


I would maybe think about taking another approach by prompting users for information as suggested earlier.

  • On the first run, prompt the user for required information whether that is via prompt or Form Activities
  • Save any persistent information to a local configuration for that user, use the Windows Credential Manager where it makes sense and encrypt other sensitive data if you need to store it.
  • Any additional runs assuming the information is still good, wouldn’t prompt the user for the input again.

Re: MFA, I think it will depend on your implementation and how complex of a workflow along with considerations from your security team is. As an example we use Saleforce most via API but where we did do some automation against the UI, we have the accounts setup with MFA using a OTP which is generated by a workflow. This could be done as part of the sequence or could abstract it further and have another service handle the trust relationship of the RPA to provide the token.

Another thought could be to have a attended process which would trigger another process whether that be attended (background) or unattended.

If you think there is still a use case for being able to set input arguments on an attended process through the UiPath Assistance, I’d encourage your to submit an idea in the User Voice part of the forum for UiPath to review and consider.

This is the most significant! Solutions are most often shot down because of security concerns. Getting service accounts to automated front-ends without MFA is extremely time consuming.

Yep, we control access to certain front-ends like SF that we can either do Front-end automation or API automation. But there are other HR,Finance and Sales Commission apps to which we don’t have access to. And the variables require human intervention for the decision making process.

Example: A certain type of contract that has to be treated a certain way based on its type, history, billing etc.

This is where the whole thing suffers. The MFA tokens are generated on peoples official mobile devices and they have to put them in as a password+token combination.

Yep, one other contributor has already done it and I’ve voted for it.