Inside the Workspace Editor: The Workspace Tree
Have you ever used the Workspace tree?
The Workspace tree is a hierarchical tool inside the Workspace editor that lets you see the nested structure of your workflow and search for operations by text generally, or specifically by label, global name, UUID or operation type.
Where is the workspace tree anyway?
If you cannot see the Workspace tree, you may need to select it from the View->Docks… menu
Looking for a particular operation
By default, the Workspace tree will display one row per operation; each branch represents a nested workflow with the operations inside it represented as its children. The top figure shows a workflow where the root workflow has two nested workflows, the “Write chart image” branch has been expanded.
To search for a particular operation, enter part of its label inside the line editor and press Enter. The tree will expand to ensure any rows with matching items are visible while any non-matching operations are hidden.
Showing (or hiding) inputs and outputs
You can expand this tree to show inputs and outputs using the filter menu, to the right of the line editor. For example, you can use the Show Inputs and Show Outputs checkboxes to toggle between showing/hiding inputs and outputs. Similarly, the Show Operations checkbox toggles between showing or hiding operations that are not nested workflows. The tree will always display nested workflows if they or any of their visible children are matches.
Global names, UUIDs, types and external file paths
In the same way, you can also expand the workspace tree to show more information columns. Try setting the Show global names or Show UUID checkboxes. Similarly, you can display operation types and external file paths. As you can see in the figure below, you can sort, swap, expand or contract columns to get the display you find most helpful.
Restricting what shows up
Generally, the search function will find items that match the line editor text in their global name, UUID, type or file path as well as their labels. However, you can restrict this if you are looking for something specific by changing the match filter type. Look at the figure below to see how you can change the match filter to hide operations if their types don’t contain “chart”.
As always, we we would be really glad to hear from you if you have any feedback.