If I may suggest a feature - it would be great if I could name a
dataset inside the workflow. Instead of naming it "Input dataset" I
could give it a descriptive name, so even if the order of the input
datasets changes, users will know which dataset goes into which input.
Okay, input dataset labels are (finally ;) implemented in 15bf910890d5
which is r1647 in central and 1907 in the security development branch.
In the editor form, you can provide a name for any input dataset, and
it will be displayed as the row label in the run form.
The support for this is pretty generic, and this changeset may help
anyone wanting to try adding more parameters to a workflow module
(like constraining input dataset type).