This document describes how a simple scheduling application operates. This topic introduces the basics for providing appointments and resources data for the Scheduler.
How Does the Scheduling Application Operate?
The Scheduler Control displays the appointments data to end-users and responds to their input. All its data is provided via the built-in Scheduler Storage object. The Scheduler Control knows nothing about the data layer, while the Scheduler Storage knows nothing about end-user interaction.
Client-server interaction is performed via the callback mechanism (default), although the common postback and update panel operation modes are also available.
The navigation between the scheduled appointments can be accomplished via the stand-alone controls of the Suite, or the controls hosted within the main Scheduler control. The Go To Date dialog window serves the same purpose.
Appointment editing can be accomplished via invoking the separate appointment editing form, or in-place. The template mechanism enables customization of the form's appearance.
Processing the Data Layer
The Scheduler Storage object is intended to work on the data layer to provide appointments and resources data to the scheduling application. In fact, the Scheduler Storage contains two separate data stores - one for appointments (Appointments) and one for resources (Assigning Appointments to Resources). When providing data to these stores, it's necessary to specify mappings between data fields in the datasource, and their interpretation in the storage. Also, these stores provide the ability to optimize data loading, specify options specific to different data, add custom fields, etc.