Some clarification on Hide Dataset Actions and Workflow Outputs.
Hide Dataset Actions- This action hides one individual dataset after a job has been
Workflow Outputs- The intent of these is to give workflows some notion of
'official' outputs. Clicking the asterisk, or snowflake, on a particular output
dataset in the workflow editor flags the dataset as a workflow output- something you'd
like to see as an end result of running a workflow. Ultimately, we'd like for this
ability to formalize workflow outputs to lead to using workflows as one would use a tool,
potentially embedding them within other workflows.
For example, toggling the "snowflake" does seem to alter
the right hand side (add/remove the "Hide Dataset"), but
only after you save, close, and reload the workflow.
Is this a bug? If so, the simplest way to solve this (from a
UI perspective) might be to remove the "Hide Dataset"
action from the right hand side.
Workflow outputs utilize Hide Dataset Actions to do the work of hiding datasets as jobs
complete. That's why you see them added to your workflow whenever you save. Upon
saving, if any workflow outputs are tagged, all non-tagged output steps have a hide
dataset action added. Additionally, workflow outputs override individually set
hide-dataset actions, and will remove them as appropriate.
On a related point, if I extract a workflow from my history,
all the steps have their "snowflakes" greyed out - even the
final step in the history. Yet despite this, when I run the
new workflow all the output is kept (nothing is hidden).
After a little experimenting, my guess is that you have a
special case: if all the outputs have greyed out snowflakes,
rather than running the tools and hidding all the output, you
You are correct in your guess that if no workflow outputs are flagged, we do assume
you'd rather see everything than nothing. This is why an extracted history with
nothing flagged as an output, just like if you had an old workflow from before outputs
were available, will show everything.
I definitely understand some of the confusion here, and I agree that given the
functionality available using just the new workflow outputs we should probably just remove
manual control over Hide Dataset Actions, and represent this solely through the workflow
output asterisks. I'll also soon be adding options for marking all / none as outputs
to make working with large workflows easier.