Orchestrator parameters do not work with UiPath Assistant

[loginerror (Maciej Kuźmicz)]

Hey @postwick

I cannot speak to all the issues brought up above, but I just tested the scenario of passing some values from Orchestrator configuration of the process to the Assistant.

This is on the latest Cloud orchestrator and Studio/Assistant 2022.12:

Although not perfect just yet (it could use some more features), it does pass the parameters as it should now.

[postwick (Paul Ostwick)]

It always worked if the user edits the value.

Did you test that the values make it into the job if the user does not edit them?

[loginerror (Maciej Kuźmicz)]

Thanks for the further context, you are right. I gave it a few more tests.

Hardcoded values from the workflow will not populate the Assistant, even if Orchestrator has them set as “inherit” in the process settings. So that’s a bummer.

Then, if you do force the values from Orchestrator, those do get to the Assistant and they are used in the process execution.
It is possible to update the value in the Assistant from Orchestrator.

But, the moment the user edits a value manually, you can no longer reset it arbitrarily from Orchestrator until the user clicks on the Clear button in Assistant:

[Catalina_Ianus]

Hello everyone,

In wrapping up this discussion, our efforts resulted in implementing and delivering this enhancement in version 23.4.
These are the release notes: You can see from Assistant which arguments have default values defined at design time. If a variable has a default value and is not modified, the automation will run with that default value. You can also update the respective fields with your preferred values.

We appreciate your feedback, @postwick We will continue improving the experience of configuring the input arguments even more.