...
Each activity has a predefined set of Input/Output parameters. Depending on the requirements and business scenarios, variables and arguments may be required.
All parameters that have an Expression editor in Activity Properties panel can be used for value storage and passing, through variables and arguments.
Example: Collection From String activity
Defined IN arguments, with default value to be filled in by the user when running the workflow:
Defined variables to store the output of the Collection From String activity:
Parameters with different editors, like Folder editors or ComboBox cannot be bound to variables nor arguments. Each Input parameter from each activity has an editor. The default editor is the Expression Editor which allows string values to be inserted. In the example below, the activity used is Length (check the Misc->Display Name property) from String Operations library . This activity has one input parameter, with an Expression editors that accept string values. The value "Flowster" was inserted directly in the Expression editor without the use of variables/IN arguments meaning that the value is now embedded in the task after check-in. This represents the basic value insertion for activity parameters.
If the value for the "InputString" parameter should not be embedded in the task and the value would be given on execution time, for example when executing the task from the User Portal, then an IN argument is defined for the "InputString" parameter.
Activity Properties
In general terms of activities properties, there are three main concepts:"Tracking Outputs", „Stop On Error" and „Enabled".
The concept of „Stop on error" and „Enabled"mechanisms are defined for Runtime purposes.
...