Command ID. This can be any string, and it's up to the api integrator to ensure uniqueness.
Arbitrary metadata set by the api integrator. Keys must start with 'ext-'
The command type
Command format version / API version
Is this slot committed, or only planned?
S4C's dispatch system (FLS) plans a slot at "Bestätigt" — real, but still
movable — and commits it at "Fixiert". Only a committed slot should move
the job to appointment_confirmed and fire the confirmation side effects.
Omitted means committed. Every sender before this field existed meant "confirmed", and the backfill scripts still do, so absent must keep the original behaviour. The FLS-status → boolean mapping stays in the Dynamics flow: GID should not learn FLS picklist codes.
Generated using TypeDoc
Set (or update) the appointment for a specific job. Triggered by S4C via the
/v3/commands/s4c/appointmentendpoint and consumed in jobs-service, which calls gid-apiadmin/jobs/set-statuswith the suppliedappointment_date— moving the job toappointment_confirmed, or, whenappointmentConfirmedis false, writing the date while leaving the status where it is.Exactly one of
jobApiId,invoicingEid,gidOrderNumber, oryourOrderIDmust be provided to identify the target job.