pub struct EventTemplate {Show 14 fields
pub admin_ids: Option<Vec<Value>>,
pub calendar_id: Option<i64>,
pub description: Option<String>,
pub duration_in_seconds: i64,
pub event_name: Option<String>,
pub facts: Value,
pub hour: Option<i64>,
pub id: i64,
pub minute: Option<i64>,
pub note: Option<String>,
pub services: Vec<EventTemplateService>,
pub sort_key: i64,
pub template_name: String,
pub extra: Map<String, Value>,
}Expand description
This is separate from a calendar appointment template. When creating an event for an appointment with eventTemplateId, the current event-creation service copies description, adminIds, service slot counts and facts. The appointment and supplied startDate determine the new event’s appointment and time; the remaining scheduling fields are template metadata for clients.
Fields§
§admin_ids: Option<Vec<Value>>Database storage can return numeric IDs as strings. null means no stored administrator list.
calendar_id: Option<i64>Default calendar ID; null when no default is stored.
description: Option<String>Empty text is converted to null when the event is created from this template.
duration_in_seconds: i64Default duration in seconds, not minutes.
event_name: Option<String>Proposed event name; null when no default is stored.
facts: ValueDefault recorded values keyed by fact definition ID from /facts.
hour: Option<i64>Default local start hour; null when no default is stored.
id: i64ID to use as eventTemplateId when creating an event for a calendar appointment.
minute: Option<i64>Default local start minute; null when no default is stored.
note: Option<String>deprecated in the ChurchTools API
Deprecated alias for description.
services: Vec<EventTemplateService>Service roles and their requested slot counts; an empty list is allowed.
sort_key: i64Template display order. This endpoint sorts by sortKey ascending.
template_name: StringName of the reusable template, distinct from the proposed event name.
extra: Map<String, Value>Fields not described by the spec, e.g. instance-specific DB fields.