...
In general terms of parameters in WF4, there are two main concepts: Variables and Arguments. Variables are used to store data within a task and Arguments are used to pass data in/out of a task. The concept of „binding" parameters has been replaced with the usage of variables and arguments.
Variables are to be used in a task whenever the need to store data is limited to the current task and the output/input of the task is not used anywhere else (for example another task).
Arguments are to be used whenever the input parameters of an activity are given by the user using a web-based application, (for example when executing a task in User Portal) or if the output of an activity is to be returned and used outside of flowster Design Studio Flowster Designer application. (for example User Portal).
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 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.
...
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 Design PoolActivity Library.
The concept of Stop On Error and Enabled mechanisms are defined for Execution purposes.
...