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 9:30 AM - 11:30 AM | Data-Driven Economy 6:30 AM - 8:30 AM Content Marketing World 12:30 PM - 2:30 PM | B2B Marketing Forum 4:30 AM - 6:30 AM Business Innovation Factory 7:30 AM - 9:30 AM Journalism Interactive 1:30 PM - 3:30 PM | Blogcademy 4:30 AM - 6:00 AM Sustainable Brands 7:30 AM - 10:00 AM | | Burning Man 9:30 AM - 11:30 AM | Data-Driven Economy 6:30 AM - 8:30 AM Techweek 9:30 AM - 11:30 AM | B2B Marketing Forum 4:30 AM - 6:30 AM Business Innovation Factory 7:30 AM - 9:30 AM Grow Conference 10:30 AM - 12:30 PM | Fashion Confidential 3:30 AM - 4:15 AM Blogcademy 4:30 AM - 6:00 AM Sustainable Brands 7:30 AM - 10:00 AM | | Burning Man 9:30 AM - 11:30 AM | Techweek 9:30 AM - 11:30 AM Content Marketing World 12:30 PM - 2:30 PM | B2B Marketing Forum 4:30 AM - 6:30 AM Grow Conference 10:30 AM - 12:30 PM Journalism Interactive 1:30 PM - 3:30 PM | Fashion Confidential 3:30 AM - 4:15 AM Blogcademy 4:30 AM - 6:00 AM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
|
Description
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.