Closed a-pika closed 8 years ago
This is because the output binding belongs to the task, not the variable. In the output bindings dialog in the example, we are looking at the binding that outputs to net variable 'var'.
Nevertheless, there is a warning dialog when an output binding is about to overwrite an existing one, with 'yes, no, cancel' options.
outputBinding.yawl.gz
Steps: in the attached specification (‘outputBinding.yawl’) open ‘Data variables’ for task ‘a’ -> create another task variable with scope ‘Output’ (e.g. ‘var2’) and bind it with net variable ‘var’
Result: Output binding for task variable ‘var’ is modified (without warning):