Parameter not populating in Orchestrator despite having it as arguments in Studio

So i have a sequence which i have extracted as a workflow.
I am invoking this workflow from main.xaml file.

The workflow has 3 variables,which i have managed to invoke and in turn got converted to arguments.I even imported these arguments.Later published them.

However when i try to run a job in orchestrator,it showing parameters with the below message : “Input parameters are not defined for this version.”

My question is why is it that despite importing arguments,they have not populated in my Orchestrator.

I have searched for this answer over entire forum.But didnt find.
I appreciate your efforts to reply.Thank you in advance.

1 Like

Hi @Vidya_Srinivasan

Which versions of Studio and Orchestrator is it?

Studio : 2019.7.0
Orchestrator : 2019.6.0-CE.4

Attaching the code below :
Main.xaml (4.2 KB) Notepad_char_count_workflow.xaml (11.7 KB)

I believe it is because your Main.xaml doesn’t have arguments corresponding to the arguments from the invoked workflow.

Basically, only the arguments from the Main.xaml will be visible in Orchestrator.


So my main does have “Import argument” option.
Then my next question is : Why is it that despite clicking on import argument,the arguments are not populating in variable pane of main.xaml.

All is as expected. Invoke Workflow File activity has this button to easily allow you to assign variables or arguments to the ones from the invoked workflow.

You will need to have arguments for your Sequence in Main.xaml file and then you will be able to assign those as values in the Import Arguments window :slight_smile:

So i manually created arguments in the variable pane(If that is what you meant).
I was able to get the argument in orchestrator.

Please let me know if this is the correct procedure to pass arguments.

Also Can you elaborate on the use of this below window.I didnt understand

Basically, each workflow has it’s arguments. These need to be passed around when you invoke one workflow from the another one.

This passing of arguments happens in the Invoked Workflow’s arguments window.

Basically, the Name in that window is the argument (from the arguments pane) of the file that is being invoked. Clicking Import Arguments will automatically populate this window for you.
The Value in that window are the arguments on the level the workflow is being invoked. In this case, you should assign each argument you have just created to each argument that was already there after automatic import :slight_smile:

Thank u for taking time to reply.
Did u mean something like this : image

So i first need to create variables manually in argument pane ( As they didnt come automatically)Marked 1 in diagram

And then i need to assign those variables to the window marked 2(Which is invoked workflow’s argument window)

In that case,my next question is :
What is the use of this assignment as just creating new variables (1 in diagram) is passing parameters to Orchestrator.

Whats the need to assign these variables to invoked workflow’s argument window?

I am new to UI Path Studio.Hence these basic doubts.

On doing as below :

I get the orchestrator page as below :

However if i dont assign these manually created variable to “Invoked workflow arguments” window,this is how the orchestrator comes :

The process works as expected when i assign those variables to Invoke workflow argument window.

If i dont assign those,it doesnt work as expected.Is this the difference.

You have to basically pass your argument down to the invoked workflow.

See here for the simplest setup :slight_smile:

If you publish this, this will happen:

  1. in_username argument will be exposed in Orchestrator
  2. in_username will be passed as a value to the invoked workflow
  3. in the invoked workflow, it should look like this:

You basically have to:

  1. work with arguments
  2. look at it ‘from the top’

The top-most level is the Orchestrator (in your case). You then take this argument and assign it as a value to the inner argument of the invoked workflow.

I hope it makes things clear :slight_smile: I really hope someone has figured out an easier way to explain it (maybe graphically). I remember it took me some time to get it initially :smiley: But it is rather straight-forward in the end.

1 Like

Thank u so much ! This is very well explained by you.

I get it now :slight_smile:

1 Like

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