pub struct AppointmentBase {Show 27 fields
pub additionals: Vec<AppointmentAdditionals>,
pub additions: Option<Vec<AppointmentAdditionals>>,
pub address: Option<Address>,
pub all_day: bool,
pub calendar: AppointmentBaseCalendar,
pub caption: Option<String>,
pub description: Option<String>,
pub end_date: DateOrDateTime,
pub exceptions: Vec<AppointmentExeptions>,
pub id: i64,
pub image: Option<Image>,
pub information: Option<String>,
pub is_internal: bool,
pub link: Option<String>,
pub meta: MetaDataEntityId,
pub note: Option<String>,
pub on_behalf_of_pid: Option<i64>,
pub repeat_frequency: Option<i64>,
pub repeat_id: i64,
pub repeat_option: Option<i64>,
pub repeat_until: Option<NaiveDate>,
pub signup: Option<AppointmentSignup>,
pub start_date: DateOrDateTime,
pub subtitle: Option<String>,
pub title: String,
pub version: i64,
pub extra: Map<String, Value>,
}Expand description
Stored calendar appointment defining a single occurrence or a series. id identifies the whole stored appointment; pair it with a local occurrence start date to address a particular occurrence. startDate/endDate are the base occurrence, not necessarily the occurrence currently being displayed. Service-planning events, registration groups, bookings and meeting requests are separate linked resources.
Fields§
§additionals: Vec<AppointmentAdditionals>§additions: Option<Vec<AppointmentAdditionals>>Use ‘additionals’ instead
Use ‘additionals’ instead
address: Option<Address>§all_day: boolTrue when the appointment is all-day. The serialized endDate is inclusive.
calendar: AppointmentBaseCalendarCalendar containing the appointment.
caption: Option<String>Use ‘title’ instead
Use ‘title’ instead
description: Option<String>§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: Vec<AppointmentExeptions>§id: i64ID of the stored appointment or series.
image: Option<Image>§information: Option<String>Use ‘description’ instead
Use ‘description’ instead
is_internal: bool§link: Option<String>§meta: MetaDataEntityId§note: Option<String>Use ‘subtitle’ instead
Use ‘subtitle’ instead
on_behalf_of_pid: Option<i64>Person on whose behalf the appointment was entered, or null.
repeat_frequency: 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.
repeat_id: i64Recurrence 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<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.
repeat_until: 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.
signup: Option<AppointmentSignup>Registration-group configuration, or null if the appointment has none.
start_date: DateOrDateTimeStart of the base occurrence. For all-day appointments, send YYYY-MM-DD.
subtitle: Option<String>§title: String§version: i64Revision counter increased by updates; not an input precondition or a per-occurrence ID.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.