Shell task
The Shell task allows you to run shell scripts and commands.
| Command | Shell command to execute. |
| Argument 1 | Arguments that are passed to the shell command. |
| Argument 2 | Arguments that are passed to the shell command. |
| Argument 3 | Arguments that are passed to the shell command. |
| Argument 4 | Arguments that are passed to the shell command. |
| Argument 5 | Arguments that are passed to the shell command. |
| Wait | Wait, if necessary, until the shell process has terminated. |
| Output Variables | Variable to store shell command output. |
| Error Code Variable | Variable to store shell command error code. |
| Redirect Error | Indicates whether the standard error is combined with the standard output. |
| Clean Env | Indicates whether the shell process inherits the current environment. |
| Directory | Default directory of shell process. |
| Exclusive | When it receives a special job from a specific process example, it makes jobs run in order. |
| Execution listeners | Listeners for an activity, process, sequence flow, start and end event. |
| Multi-instance type | Determines if multiple instances of this activity are created. |
| Cardinality (Multi-instance) | An expression or numeric value determines how many instances are created. |
| Collection (Multi-instance) | The number of instances is determined by the elements of a collection. For each element in the collection, a new instance is created. |
| Element Variable (Multi-instance ) | The variable under which each element is available to the newly created instance. |
| Completion Condition (Multi-instance) | An expression that, if it evaluated to true , stops the creation of new instances. |
| Is for compensation | A flag that identifies whether this activity is intended for the purposes of compensation. |
Execution listeners examples
You can use the Execution listeners as shown in the examples.
Start
End
Take
Multi-instance type examples
You can use the Multi-instance type as shown in the examples.
Default, only one instance is created:
None
Activities are created in parallel. This is a good practice for User tasks activity:
Parallel
Activities are created sequentially. This is a good practice for Service tasks activity:
Sequential
Cardinality (Multi-instance) examples
You can use the Cardinality (Multi-instance) as shown in the examples.
${number}
2
Collection (Multi-instance) example
You can use the Collection (Multi-instance) as shown in the example.
2
Element variable (Multi-instance) example
You can use the Element variable (Multi-instance) as shown in the example.
elementvar
Completion Condition (Multi-instance) example
You can use the Completion Condition (Multi-instance) as shown in the example.
true
${variable==True}