Workflow & automation — quiz
6 questions covering this module. Organising, parsing, outputs and running repeatably.
How do you test a workflow without running one branch?
- Delete the tools
- Disable the container holding them
- Add a Filter
- Comment them out
Answer: Disable the container holding them — Disabling skips everything inside on the next run.
A good tool annotation says:
- The tool name
- Why the tool is there
- The record count
- The author
Answer: Why the tool is there — What it is, is already visible on the canvas.
A field holds "widget, bolt, nut" and you need one row each. Use:
- RegEx Match
- Text to Columns, split to rows
- Cross Tab
- Append Fields
Answer: Text to Columns, split to rows — Splitting to rows is the option people overlook.
Why specify the input format in the DateTime tool?
- Speed
- Ambiguous formats are misparsed silently
- It is required
- To handle nulls
Answer: Ambiguous formats are misparsed silently — 03/04/2024 could be March or April.
To produce one CSV per region in a single run:
- One workflow per region
- Take File/Table Name From Field on the Output tool
- A Union tool
- A container per region
Answer: Take File/Table Name From Field on the Output tool — The field value becomes the file name.
Which makes a workflow safe to rerun?
- Append outputs
- Relative paths and overwrite or delete-and-append outputs
- More containers
- Disabling Browse tools
Answer: Relative paths and overwrite or delete-and-append outputs — Append plus absolute paths is the usual handover failure.