Ask for a job's deadline to be moved later, and move it if that is granted.
Unlike rescheduling, this moves the promise: the due date and the promised resolution time both shift by the interval between the date asked for and the one the job already had, so a job with two different deadlines keeps the distance between them and neither can be shortened by an extension. The promised response time is left alone — by the time more time is needed it has already been met or missed — and a breach that has already been recorded stays recorded.
Why the job needs longer is picked from your own list rather than typed: p_reason_id names a row of api.work_order_sla_extension_reasons, which is what makes “what keeps making us late” a question a report can answer. p_reason is the sentence beside it, and is required on any reason whose requires_notes is set — a delay waiting on a contractor is worth naming the contractor in, and your list is where that is decided.
Where an approval chain is published for extensions the job does not move until the chain settles, and the answer says the request is pending rather than that the dates changed. Where none is published the permission is the whole gate and the extension takes effect at once.
Whether more time may be asked for at all depends on where the job currently stands: a status is marked as one this is offered in, and no status is marked that way until somebody says so. A job sitting anywhere else is refused.
Refuses a date that is not later than the deadline the job already has, a job that is finished, a job that has no deadline at all, a reason that is not yours or no longer offered, and a reason that asks for a sentence given without one.
Headers
Preference
params=single-object Body
Ask for a job's deadline to be moved later, and move it if that is granted.
Unlike rescheduling, this moves the promise: the due date and the promised resolution time both shift by the interval between the date asked for and the one the job already had, so a job with two different deadlines keeps the distance between them and neither can be shortened by an extension. The promised response time is left alone — by the time more time is needed it has already been met or missed — and a breach that has already been recorded stays recorded.
Why the job needs longer is picked from your own list rather than typed: p_reason_id names a row of api.work_order_sla_extension_reasons, which is what makes "what keeps making us late" a question a report can answer. p_reason is the sentence beside it, and is required on any reason whose requires_notes is set — a delay waiting on a contractor is worth naming the contractor in, and your list is where that is decided.
Where an approval chain is published for extensions the job does not move until the chain settles, and the answer says the request is pending rather than that the dates changed. Where none is published the permission is the whole gate and the extension takes effect at once.
Whether more time may be asked for at all depends on where the job currently stands: a status is marked as one this is offered in, and no status is marked that way until somebody says so. A job sitting anywhere else is refused.
Refuses a date that is not later than the deadline the job already has, a job that is finished, a job that has no deadline at all, a reason that is not yours or no longer offered, and a reason that asks for a sentence given without one.
Response
OK