Commands and automation
Running bulk operations from one line, and scheduling them.
The command bar runs operations across many records at once — the things that would otherwise be an afternoon of clicking.
The shape of a command
A verb, a record type, and a filter:
find part where lifecycle = 'released' and mass is nullexport part where project = 'HALO6' --format xlsxcompare bom 8383838 9399393 --level all
It always previews first
- You type the command.
- It resolves to a set and shows the count and matching rows.
- You read what it proposes to do.
- Nothing happens until you confirm.
Chaining
A pipe passes the matched set to the next verb: find part where category is null | set category = 'mechanical'
Useful flags
| Flag | Effect |
|---|---|
--dry-run | Stop at the preview permanently; never execute |
--atomic | If any row fails, roll the whole batch back |
--format | For exports: xlsx, csv or pdf |
Automations
Any command you've previewed can be saved to run on a schedule, on an event such as an ECO releasing, or when a condition first becomes true. Every run is audited exactly like a manual one.
It runs as you, with your permissions, through the same gates as the interface. Rows you can't see aren't matched; locked parts are refused and named; approvals still apply.
Email [email protected] and a person will pick it up. Include the part number and what you were doing — it saves a round trip.