Assistant arguments display is bad design

[postwick (Paul Ostwick)]

I realize you had to fix that the arguments didn’t pass properly, and I’m hoping that’s fixed, but this “Use default value”…

…is terrible. The user needs to see what the value is to know whether to update it. And the value should still be there when the edit icon is clicked, to allow editing the value instead of just typing into an empty box.

[Catalina_Ianus]

Hello, @postwick

Thank you for you feedback! I created a ProductBoard insight and will take in consideration as soon as it is possible.

I have some questions:

• Do all processes use input arguments to collect data from users?
• Are there any cases in which you would want to restrict users from updating the default values? Can you please provide some examples?
• Do input arguments have default simple values or are there any default complex expressions? Are users updating the default expressions from Assistant?

Thank you once again

[postwick (Paul Ostwick)]

[quote=“Catalina_Ianus, post:4, topic:708815”]

• Do all processes use input arguments to collect data from users?

Not all processes, no.

• Are there any cases in which you would want to restrict users from updating the default values? Can you please provide some examples?

There can be times where we wouldn’t want them to be able to update certain parameters - like log file paths, filenames, etc.

• Do input arguments have default simple values or are there any default complex expressions?

So far we’ve only used simple values, because that’s all UiPath allows AFAIK.

• Are users updating the default expressions from Assistant?

I’m not sure what you mean by default expression. You can’t enter expressions into the parameters, only explicit values.