...
Each activity has a predefined set of Input/Output parameters. Depending on the requirements and business scenarios, variables and arguments may be required.
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 the String Operations library . This activity has one input parameter, with an Expression editors that accept string values. The value "FlowsterFlowsterStudio" 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 Portal, then an IN argument is defined for the "InputString" parameter. The arguments are defined in the Task Designer panel, Parameters section, Arguments tab. Each argument defined in this section should have a name, direction( IN for input values , OUT for output values, IN/OUT for arguments that are used for both input and output purposes). The argument type must match the desired input parameter's type from the activity (for example, for Length activity, the InputString parameter has a string type, so the defined argument InputString should have the same type).
Activity Properties
In general terms of activities properties, there are three main concepts: Enabled, Stop On Error and Track Outputs. These three properties are defined for each activity in Flowster Studio Activity Library.
The concept of Stop On Error and Enabled mechanisms are defined for Execution purposes.
...