pub struct BookingCreate {Show 17 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 quantity: Option<i64>,
pub description: Option<Option<String>>,
pub on_behalf_of_pid: Option<Option<i64>>,
pub resource_id: i64,
pub show_in_cal: bool,
pub status_id: i64,
pub subtitle: Option<Option<String>>,
pub title: String,
pub extra: Map<String, Value>,
}Expand description
Create an independent resource booking. A resource requiring an appointment must instead be booked through the appointment APIs.
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.
quantity: Option<i64>Number of resource units reserved by each occurrence.
description: Option<Option<String>>Booking notes.
None leaves the field out, Some(None) sends null.
on_behalf_of_pid: Option<Option<i64>>Person for whom the booking is made.
None leaves the field out, Some(None) sends null.
resource_id: i64Resource to reserve, such as a room, vehicle or piece of equipment.
show_in_cal: boolWhether the booking is marked for display in the calendar. This does not create or link a calendar appointment.
status_id: i64Booking status: 1 = pending approval, 2 = approved, 3 = rejected. Rejected bookings are excluded from conflict checks.
Allowed values: 1, 2, 3.
subtitle: Option<Option<String>>Optional booking subtitle.
None leaves the field out, Some(None) sends null.
title: StringBooking title shown in resource planning.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.