Event unique id
Event type
Event format version / API version
Installation appointment time end
Installation appointment time start
The order billing address
Documentation for order completion and/or other order related events.
Not that, one documentation type can be have several files present.
The partner-side internal order id (mapped from job.partner_eid__c).
The order external id, if set by the API integrator
The time installer finished working on a order.
The order invoicing external id, if set by the API integrator
The opportunity (deal) the job belongs to. The opportunity groups the jobs
of an order and carries the order-level arrangement with the brand, so it
is the level at which "what kind of business is this" is decided — a
Mehrplatz opportunity is a multi-site project, whatever the single job
happens to look like.
Optional because a payload built before the relation was loaded has neither, and because not every job need have an opportunity. Prefer the id for anything that must stay stable; the name is free text that S4C read.
The order ID
The order number used for communication (email, protocols, etc.)
Products included in the order.
The ID of the project this order belongs to
The name of the project this order belongs to
Total scheduled service time for this order in minutes.
Services included in the order.
The order installation address
The time installer started working on an order.
The substatuses of the Job. See JobSubstatus for why each entry is an object rather than a string.
Generated using TypeDoc
This event is sent on a change in order status and or relevant fields, meaning it will be sent even if there is no status change but a field related to the current status has changed.