Visible Hour eliminates long scrolls on refresh by letting you determine the start and end time of the visible hour region. Event rendering adjusts according to your settings. Even better, all WebScheduler’s feature, such as client paging, time interval, etc., still work flawlessly. Any overlapping events are rendered according to the current visible hour setting. The real event's time span is still visible from the interactive call out. All events are still displayed.
WebScheduler supports multiple time interval views to satisfy every user. All related events, actions, and UI elements smartly adjust to fit into the time settings. Cycle from 10-minutes to 60-minutes time interval to for a granular view of events, or dial back for the big picture. Time interval is view dependent. This means you can easily set different time interval for each view. Users also have the privilege of changing the interval in runtime through the built-in contextual menu. The combination of time interval feature and multiple cell selection lets users quickly create a new event based on the selected cells duration.
Disabled time is a unique feature that lets you block event creation during certain time periods without any complicated code. When the disabled time is specified, a user will not be able to add a new, or edit an existing event, within the disabled time period. There are three disabled time options in WebScheduler: global disabled time, resource disabled time, and partial disabled time.
The tight integration between WebScheduler and the rest of WebUI Studio’s ASP.NET components ensures that users will always have a consistent, familiar user interface. For developers, this also maximizes the value of existing investments in Intersoft's WebUI technology, and increases productivity by reducing learning curves.
The built-in disabled time validation engine prevents adding events within a disabled time area. However, if either the start or end dates occur outside a disabled time area, they are saved. Enjoy complete freedom to manually code the validation logic. This process must be done in OnValidateDisabledTime, as a client-side event. The return must be a Boolean value. A custom validation will cause WebScheduler to validate all events based on the custom logic.