At design time, in Studio, the way you configure your project to accept In or Out arguments, with or without default values,
enables you to use them in other third-party apps or Orchestrator. You can only make use of input and output arguments in
Orchestrator and other third-party apps if you had added the corresponding arguments in your Studio project beforehand. If
no arguments have been added in Studio, the following message is displayed: "Input arguments are not defined for this version.".
The In, Out, or In/Out arguments of a project become input and output arguments when published to Orchestrator. Please note
that for In/Out arguments two different arguments are created and displayed in Orchestrator, an input and an output one, with
the same name.
Note:
A value provided for an input arguments at process level in Orchestrator is kept when you update the package, as long as
the new package version does not concern arguments' definition.
The storage limit for input/output arguments is 1 MB.
If you provide values for input arguments in Orchestrator, please note that they have to be provided in a JSON format. A few
examples of how you can do this:
String
- the value has to be provided without quotation marks, such as
string
;
Int32
- provide the value as you would any integer,
11
;
Boolean
- two radio buttons are displayed to help you select true or false;
Double
- provide the value as a floating point value, such as
3.5
;
DateTime
- provide the value as a valid JSON, such as
"2012-04-23T18:25:43.511Z"
;
Array
- provide values as valid JSON, such as
[1, 1, 2, 3, 5, 8]
or
["firstString", "secondString"]
.
Note:
Any type of In argument can be used, yet please keep in mind that only primitives are validated by Orchestrator.
Note:
For API calls, a maximum of 10,000 characters is accepted for the entire length of the JSON representation of input arguments,
including argument names, all the escaped characters, spaces, brackets, and argument values.
Note:
Workflows that were created and published to Orchestrator prior to v2018.3 must be re-uploaded with a v2018.3 (or later)
Robot so that the In and Out arguments of the
Main.xaml
file can be displayed.
