We need to be able to stop users from editing parameters through Assistant

We just upgraded our test environment to 2020.10.4.

Trying out the new UiPath Assistant, I see it lets the user set their own parameters. This is awful. Users should not have this access by default, and I can find no way to turn it off.

The other problem is that even though Assistant shows the value as configured in the Process in Orchestrator, it doesn’t actually USE the parameter value that’s in Orchestrator - despite showing you the value.

This is terribly designed.

1 Like

Hi @postwick ,

Why do you want to block end-users to lack access to the parameters? What are you usually using the parameters for?
Thanks!

Parameters are for various things like paths to where the Process should save log files, who to email for errors or successes, email server settings etc.

We use arguments/parameters instead of Excel config files. Much simpler and more secure.

All along only Orchestrator admins could change Process parameters. Now suddenly they expose them to end users. This is absolutely horrible decision-making.

1 Like

Hello @postwick

Thank you for sharing this insight. To enhance my understanding, I’d like to pose a few questions:

  • Are end users the ones running the automations you mentioned earlier?
  • Do these end users undergo any training? Are they familiar with the specific input parameters they can manipulate and those they should avoid? I envision that this training process might be challenging and time-consuming. Could you elaborate on this aspect?
  • Do end users have access only to relevant automations in their Assistant or is there a risk of them interacting with automations they should not have access to?

Thank you! :rocket:

  • Are end users the ones running the automations you mentioned earlier?

Yes

  • Do these end users undergo any training? Are they familiar with the specific input parameters they can manipulate and those they should avoid? I envision that this training process might be challenging and time-consuming. Could you elaborate on this aspect?

We do not use parameters for attended automations, exactly because it has never worked well.

  • Do end users have access only to relevant automations in their Assistant or is there a risk of them interacting with automations they should not have access to?

The only have access to relevant automations.

My feedback on your survey post is about how parameters work in Assistant today (2023.4.4). This post about stopping users from editing the parameters also still applies - we should be able to control which parameters are editable by the user in Assistant vs only being editable in Orchestrator.

1 Like

Thank you @postwick :rocket:

Your concerns are valid and very important for us to address.

We will keep you informed of any developments or solutions that may arise in the future regarding the input arguments. We are already working on some improvements :heart:

1 Like

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