Support / Command & automation
Automations
Turning a command into something that runs on its own.
Any command you've previewed can be saved to run without you.
Three kinds of trigger
| Trigger | Example |
|---|---|
| On a schedule | Nightly export at 02:00. Weekly backup. Month-end cost roll-up on the last working day. |
| On an event | When an ECO releases, push the changed lines out and notify affected suppliers. |
| On a condition | When a released part first has no supplier price, open a worklist for the buyer who owns that commodity. |
Setting one up
- Run the command manually and check the preview is what you expect.
- Choose Save as automation.
- Give it a name somebody else will understand in six months.
- Choose the trigger.
- Decide who is notified when it runs, and who is notified when it fails.
What you should know
- Automations run with the permissions of whoever saved them, not whoever benefits from them.
- Every run is written to the audit log with the same detail as a manual one.
- A run that fails notifies the owner rather than failing quietly.
- Automations can be paused without being deleted.
Run it manually a few times first
A command that behaves perfectly on today's data can surprise you on next month's. Watch it work before you stop watching it.
Still stuck?
Email [email protected] and a person will pick it up. Include the part number and what you were doing — it saves a round trip.