pub struct AppointmentSplitUpdate {Show 25 fields
pub additionals: Option<Vec<AppointmentAdditionalCreate>>,
pub end_date: DateOrDateTime,
pub exceptions: Option<Vec<AppointmentExceptionCreate>>,
pub repeat_frequency: Option<Option<i64>>,
pub repeat_id: Option<i64>,
pub repeat_option: Option<Option<i64>>,
pub repeat_until: Option<Option<NaiveDate>>,
pub start_date: DateOrDateTime,
pub address: Option<AppointmentAddressCreate>,
pub bookings: Option<Vec<AppointmentBookingCreate>>,
pub description: Option<Option<String>>,
pub events: Option<Vec<AppointmentEventCreate>>,
pub inform_owner: Option<bool>,
pub is_internal: bool,
pub link: Option<Option<String>>,
pub meetingrequests: Option<Vec<MeetingRequestCreate>>,
pub on_behalf_of_pid: Option<Option<i64>>,
pub signup: Option<AppointmentSignupCreate>,
pub subtitle: Option<Option<String>>,
pub tags: Option<Vec<Value>>,
pub title: String,
pub bookings_to_delete: Option<Vec<i64>>,
pub split_date: NaiveDate,
pub split_until_end: bool,
pub extra: Map<String, Value>,
}Expand description
New appointment data plus the scope removed from the original series. The response identifies the newly created appointment; the original retains the unaffected dates.
Fields§
§additionals: Option<Vec<AppointmentAdditionalCreate>>§end_date: DateOrDateTimeEnd of the base occurrence. For timed appointments it must be later than startDate. For all-day appointments this date is inclusive and may equal startDate for a one-day appointment.
exceptions: Option<Vec<AppointmentExceptionCreate>>§repeat_frequency: Option<Option<i64>>Interval between repetitions; use a positive integer for automatic patterns, for example 2 with repeatId=7 for every two weeks. Irrelevant for once/manual patterns.
None leaves the field out, Some(None) sends null.
repeat_id: Option<i64>Recurrence pattern: 0 = once, 1 = daily, 7 = weekly, 31 = monthly by date, 32 = monthly by weekday, 365 = yearly, 999 = manually selected dates. Automatic patterns use repeatFrequency and repeatUntil; manual dates use additionals.
Allowed values: 0, 1, 31, 32, 365, 7, 999.
repeat_option: Option<Option<i64>>For repeatId=32, ordinal of the weekday within the month: 1–5 for first through fifth, 6 for last. The weekday comes from startDate.
None leaves the field out, Some(None) sends null.
repeat_until: Option<Option<NaiveDate>>Inclusive last date of an automatic series. Supply this with automatic recurrence; omission does not represent an unlimited series in these write endpoints.
None leaves the field out, Some(None) sends null.
start_date: DateOrDateTimeStart of the base occurrence. For all-day appointments, send YYYY-MM-DD.
address: Option<AppointmentAddressCreate>Location entered with an appointment.
bookings: Option<Vec<AppointmentBookingCreate>>Resource reservations matched by resourceId.
description: Option<Option<String>>Description of the appointment.
None leaves the field out, Some(None) sends null.
events: Option<Vec<AppointmentEventCreate>>Only new service-planning events to create. Existing linked events are updated separately when the appointment changes; events no longer matching the series may be deleted.
inform_owner: Option<bool>Send an information email to the person on whose behalf the appointment is managed, or its original creator. The workflow skips inactive recipients, the acting user and changes without notable differences.
is_internal: boolSet false for a regular appointment. Use true only when the appointment is intended to be visible exclusively to signed-in users.
link: Option<Option<String>>None leaves the field out, Some(None) sends null.
meetingrequests: Option<Vec<MeetingRequestCreate>>Invitees for the appointment or series. The field name is lowercase.
on_behalf_of_pid: Option<Option<i64>>Person ID on whose behalf the appointment is created. This person is also used as inviter for meeting requests.
None leaves the field out, Some(None) sends null.
signup: Option<AppointmentSignupCreate>Configure groups used to collect registrations for individual appointment occurrences. These are separate ChurchTools groups, not meeting invitations or service-planning events.
subtitle: Option<Option<String>>None leaves the field out, Some(None) sends null.
Appointment tags to add, as IDs, names or objects containing id.
title: String§bookings_to_delete: Option<Vec<i64>>IDs of existing appointment bookings to delete. These are booking IDs, not resource IDs. In a split request, the selected scope is removed from these bookings and not recreated for the new appointment.
split_date: NaiveDateLocal date identifying the original occurrence or start of the split segment.
split_until_end: booltrue cuts the original series off on the day before splitDate; false adds an exception for splitDate only. Supply the complete recurrence of the new part in either case.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.