This demo illustrates the usage of single event that are shared by multiple resources.
More Details...
| |
12:00 AM | | 1:00 AM | | 2:00 AM | | 3:00 AM | | 4:00 AM | | 5:00 AM | | 6:00 AM | | 7:00 AM | | 8:00 AM | | 9:00 AM | | 10:00 AM | | 11:00 AM | | 12:00 PM | | 1:00 PM | | 2:00 PM | | 3:00 PM | | 4:00 PM | | 5:00 PM | | 6:00 PM | | 7:00 PM | | 8:00 PM | | 9:00 PM | | 10:00 PM | | 11:00 PM | |
| | Burning Man 3:00 PM - 5:00 PM | Data-Driven Economy 12:00 PM - 2:00 PM Content Marketing World 6:00 PM - 8:00 PM | B2B Marketing Forum 10:00 AM - 12:00 PM Business Innovation Factory 1:00 PM - 3:00 PM Journalism Interactive 7:00 PM - 9:00 PM | Blogcademy 10:00 AM - 11:30 AM Sustainable Brands 1:00 PM - 3:30 PM | | Burning Man 3:00 PM - 5:00 PM | Data-Driven Economy 12:00 PM - 2:00 PM Techweek 3:00 PM - 5:00 PM | B2B Marketing Forum 10:00 AM - 12:00 PM Business Innovation Factory 1:00 PM - 3:00 PM Grow Conference 4:00 PM - 6:00 PM | Fashion Confidential 9:00 AM - 9:45 AM Blogcademy 10:00 AM - 11:30 AM Sustainable Brands 1:00 PM - 3:30 PM | | Burning Man 3:00 PM - 5:00 PM | Techweek 3:00 PM - 5:00 PM Content Marketing World 6:00 PM - 8:00 PM | B2B Marketing Forum 10:00 AM - 12:00 PM Grow Conference 4:00 PM - 6:00 PM Journalism Interactive 7:00 PM - 9:00 PM | Fashion Confidential 9:00 AM - 9:45 AM Blogcademy 10:00 AM - 11:30 AM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
Description
In this demo, allowGroupEdit option is set to true within the group property to
enable the same event to be shared with multiple resources. With this property enabled, a single appointment
object will be maintained within the appointment collection, even if it is shared by more than one resource –
whereas the resource fields of such appointment object will hold the IDs of the multiple resources separated
by commas. Any actions such as create, edit or delete held on any one of the event, will be reflected on all
other related instances visible on the UI. The allowMultiple option when set as true within the
resource property, will allow the user to select multiple resources from the resource field of
editor window, while trying to create appointments.