Raise a job with no request behind it — a breakdown somebody is standing in front of.
Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back.
A due date given here is the job’s SLA deadline: its response and resolution targets are that date rather than the priority’s, and it is not breached before it. Without one, the priority sets both. Pass due_at_is_preview when the date is only the priority’s own, shown to the person raising the job, so the priority’s targets apply.
It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant’s own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records.
Where the organisation has published an approval workflow on raising work orders, the job is still created and numbered, but it is returned with pending_approval_request_id set and nobody may assign, move or edit it until the request is decided. Whoever was named to do it is given the job when it is approved; a refused or withdrawn job is deleted.

