Example of Editor Template in ASP.NET Core Scheduler Control

In this demo, the event window is customized based on the doctor's required appointment related fields which can be achieved by making use of the editorTemplate API. Here, the custom design is built with the required fields through the script template and its type should be text/x-template.

In this demo, the editor window header is customized based on the appointment subject field which can be achieved by the editorHeaderTemplate.

Each field defined through it should contain the e-field class, so as to allow the processing of those fields in the default event object from internal source. The ID of this customized script template section is assigned to the editorTemplate option, so that this customized fields will be replaced onto the default editor window.

As we are using our Syncfusion sub-components within this editor in this demo, therefore the custom defined form elements needs to be configured as required Syncfusion components such as DropDownList and DateTimePicker which needs to be done within the popupOpen event. This particular step can be skipped, if the user needs to simply use the normal form design with applicable fields.

Within the eventRendered event that triggers before every appointment getting rendered on the Scheduler user interface, the colors for the appointments are set based on its status which is retrieved from the appointment data.

The additional restriction has been added to the Scheduler cells such that if a cell already contains an appointment - then it should be prevented to book with multiple appointments on the same time for which the isSlotAvailable method is used. This method returns true, if the underlying cell is available for adding new events by checking whether it already has any events in it.