By default, each Appointment has two properties: ResourceId and ResourceIds. Usually, the ResourceId is used when you have only a single resource for the appointment. In case you have multiple resources for an appointment the ResourceIds collection is used. However, the current implementation of the EditAppointmentDialog uses a RadDropDownList for the resource selection. Thus, the user is not allowed to create an appointment and assign two resources to it. It can be achieved only programmatically. This is a common scenario when creating a meeting and you have at least two participants. A possible solution would be to replace the resources RadDropDownList with a RadCheckedDropDownList. Thus, the user will be able to select multiple resources.

Allow customizations of the height of RadSchedulers header in timeline view.

Add the ability to have a scrollbar in the cell where AllDay appointments are stored. The scrollbar should show after a certain amount of AllDay appointments have been added.

This feature is required for OpenEdge scenarios. 

A common case is that the resource_id field is stored as an integer field in your DataSource. But RadScheduler needs EventId type. You can have a look at the Appointment.ResourceId property which expects EventId value, not an integer. It is necessary to use a SchedulerMapping in this case and convert the integer value to EventId used by RadScheduler and convert the EventId to an integer used by your DataSource. This conversion is performed by the ConvertToDataSource and ConvertToScheduler callbacks. It is responsible for the proper conversion of the integer resource_id value coming from the DataSource to the RadScheduler's EventId. Additional information for the SchedulerMapping is available here: http://docs.telerik.com/devtools/winforms/scheduler/data-binding/scheduler-mapping

In C#, it is just necessary to specify the name of the callback which will handle the conversion but it seems to be a problem in ABL. It is required to have events.

Expose events that are fired when the user click the navigation elements in RadScheduler.

Add the NavigateBackwardsButton and NavigateForwardsButton's text to the localization provider.

DECLINE REASON:
The text in these buttons was visible due to an issue in the Aqua theme. The text of these buttons is not visible in any theme by design therefore this item will be declined as its implementation will be redundant.

Add possibility to manipulate appointments' height in the MonthView of RadScheduler.

Add possibility to customize the action of the overflow button in a month cell of RadScheduler.

When printing the timescale in the printed document should be the same as in the scheduler or with option for changing.

The following scenario should be possible:

1. Create daily occurring appointment from 10:00 AM to 11:00 AM
2. Edit the second occurrence to start at 12:00 PM to 01:00PM
3. Move it to the previous date.
3. Both the occurrence at 10:00 AM and the exception at 12:00PM should be visible

Expose some of the printing methods to allow derived classes to override them for greater customization support.

When the range factor of the ruler is less than one hour, it should be possible to enable displaying the partial times for each row (for example 10:15, 10:30, 10:45 ...)

Add an option for SchedulerMonthlyPrintStyle to show the text of the appointments, not only the dates.

By design, the month view in RadScheduler stacks the appointments for a certain day considering the start time of the appointments and their duration. Internally, it uses MonthViewEventsComparer which would be great to be replaceable somehow. 

The user should be able to continuously resize appointments to multiple days when dragging to the left or right.

When in multi day view if many days are being added, each day visual becomes so narrow that the application practically becomes useless. If there is horizontal scroll bar the view could be stretched and the user would be able to scroll between the days.

RadScheduler - Implement functionality that will allow clients to define which time intervals should be visible in TimeLine view.

In Outlook, when the appontment height should be smaller than the height needed to accommodate 1 line of text, the appointment status size is being changed instead.

Add half hour time scale in the timeline view

EnableExactTimeRendering property should get or set a value indicating whether the appointment start and end time should be rendered exactly.