Create a change order. `originalRevisionItem.id` is required and `disposition.id`, when sent, must resolve to a change order disposition. The change order's sequential number is assigned server-side, `requestedUtc` defaults to the moment of creation, and a change order created Completed is stamped with `completedUtc`. The change order is created with no impacted records and no tasks. Creates are not idempotent: a retried request creates a second change order.

When the change was requested (UTC). Defaults to the moment of creation when not supplied

When the change order is due (UTC)

When the change order was approved (UTC)

When the change order was completed (UTC). Stamped server-side when status is Completed and none is supplied

Where a change order stands.

What the change is

Whether completing a task on this change order tells the owners of the next step. Null on a create takes the company default; null on an update keeps what the change order carries

The id of the change order

The change order's sequential number, unique within the tenant and assigned server-side

When the change was requested (UTC). Defaults to the moment of creation when not supplied

When the change order is due (UTC), or null when it carries no date

When the change order was approved (UTC), or null when it has not been

When the change order was completed (UTC). Stamped server-side when status moves to Completed without one supplied

Where a change order stands.

What the change is

Whether completing a task on this change order tells the owners of the next step

When the change order was created (UTC). Read-only

When the change order was last modified (UTC); supports incremental sync. Read-only