Event schedule warnings.
An Event Warning is always attached to a specific event session; either the main session for the Event or an actual EventSession.
You must have the scheduling ConventionPrivilege to access this.
See "Object Properties" in Introduction for basic shared properties.
Complete details in EventWarningProperties.
See "Related Objects" in Introduction for how to use them.
The Convention this event warning belongs to.
The Event this event warning belongs to.
The EventSession this event warning belongs to.
Event Warnings have no child relationships.
Event Warnings have no descriptor includes.
The services used to fetch and manipulate event warnings.
The Event Warning API does not support cross-convention searching.
The Event Warning API does not support a discrete endpoint for event warning creation. Event Warnings are created automatically whenever there is a conflict in the schedule of an Event or EventSession.
GET /api/eventwarning/xxx
Returns:
{
"id" : "xxx",
"event_id" : "xxx",
"type" : "host_double_booked",
...
}
The Event Warning API does not support a discrete endpoint for general-purpose editing. Event Warnings are resolved automatically when a conflict in the schedule of an Event or EventSession is resolved.
Deletes the specified warning. Only resolved warnings may be deleted. See also "Delete Resolved Event Warnings" in Event.
DELETE /api/eventwarning/xxx
Returns:
{
"success" : 1
}
This will set the event warning as seen. A warning marked as seen (or hidden) will not appear by default on the Events scheduling index page. Some types of warnings, such as "host double booked", can't be hidden.
POST /api/eventwarning/xxx/hide
Returns same as a normal read.
This will un-set the event warning as seen.
POST /api/eventwarning/xxx/unhide
Returns same as a normal read.