pub struct AppointmentTemplate {Show 27 fields
pub address: Option<AppointmentTemplateAddressCreate>,
pub all_day: Option<bool>,
pub bookings: Option<Vec<AppointmentBooking>>,
pub calendar_id: i64,
pub days_archive_group_no: Option<i64>,
pub days_forward_no: Option<i64>,
pub description: Option<String>,
pub duration: Option<i64>,
pub events: Option<Vec<AppointmentEvent>>,
pub grouptype_id: Option<i64>,
pub is_internal: Option<bool>,
pub link: Option<String>,
pub on_behalf_of_pid: Option<i64>,
pub repeat_duration: Option<i64>,
pub repeat_frequency: Option<i64>,
pub repeat_id: i64,
pub repeat_option_id: Option<i64>,
pub start_time: Option<String>,
pub subtitle: Option<String>,
pub tags: Option<Vec<i64>>,
pub template_group_id: Option<i64>,
pub title: Option<String>,
pub category_id: Option<i64>,
pub id: i64,
pub image: Option<AppointmentTemplateImage>,
pub meta: MetaDataEntityId,
pub extra: Map<String, Value>,
}Expand description
Saved appointment defaults plus the template ID and metadata.
Fields§
§address: Option<AppointmentTemplateAddressCreate>Location entered with an appointment template.
all_day: Option<bool>Whether the template proposes an all-day appointment.
bookings: Option<Vec<AppointmentBooking>>Stored resource-booking defaults in the legacy template format.
calendar_id: i64Calendar for which the template provides defaults.
days_archive_group_no: Option<i64>Days after the appointment for archiving registration groups.
days_forward_no: Option<i64>Days ahead for creating registration groups.
description: Option<String>§duration: Option<i64>Difference between end and start in seconds. With allDay=true, 0 represents one all-day date because the appointment end date is inclusive.
events: Option<Vec<AppointmentEvent>>Stored service-planning event template selections. Applying them is part of appointment creation, not saving this template.
grouptype_id: Option<i64>Group type for registration groups created for appointment occurrences.
is_internal: Option<bool>§link: Option<String>§on_behalf_of_pid: Option<i64>§repeat_duration: Option<i64>Seconds from the chosen appointment start to the series end used when applying this template.
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_id: Option<i64>Monthly-by-weekday ordinal, using the template field name repeatOptionId. The resulting appointment uses repeatOption.
start_time: Option<String>Local start time used when applying the template, conventionally HH:mm.
subtitle: Option<String>Existing appointment-tag IDs saved in the template.
template_group_id: Option<i64>Group used as a template for registration groups.
title: Option<String>Title proposed for appointments created from this template.
category_id: Option<i64>Use calendarId instead.
Use calendarId instead.
id: i64Template ID; not an appointment ID.
image: Option<AppointmentTemplateImage>§meta: MetaDataEntityId§extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.