Difference in synchronization behavior
 | Planon will determine whether a Reservation can be created! |
The synchronization behavior is implemented by the C4C-App and thus depends on the C4C-App that is installed and whether that C4C-App supports one or both types of synchronization behavior.
The C4C-App for Microsoft Graph API supports both synchronization behaviors.
In-the-lead
For the synchronization behavior In-the-lead the C4C-App expects that the Calendar Processing property of the Room Resource in Exchange is set to AutoUpdate and that it accepts new requests tentatively. This means that the requests will remain pending in the Inbox of a Room Resource till they are handled.
The C4C-App also has a subscription on incoming requests, hence the C4C-App will be notified when someone creates/updates/cancels an Event that invited the Room Resource.
Upon a notification the C4C-App will start a synchronization process to synchronize the Event in Exchange with a Reservation in Planon. When a Reservation could be synchronized, then the C4C-App will instruct the Room Resource to accept the Event. In case a Reservation could not be synchronized, then the C4C-App will instruct the Room Resource to decline.
Follows
For the synchronization behavior Follows the C4C-App expects that the Calendar Processing property of the Room Resource in Exchange is set to AutoAccept. This means that the requests are handled immediately by the Room Resource, thus changing the Calendar of a Room Resource.
The C4C-App also has a subscription on changes to the Calendar of a Room Resource, hence the C4C-App will be notified when someone creates/updates/cancels an Event that invited the Room Resource.
Upon a notification the C4C-App will start a synchronization process to synchronize the Event in Exchange with a Reservation in Planon. When a Reservation could be synchronized, then the C4C-App does not have to do anything. In case a Reservation could not be synchronized, then the C4C-App will instruct the Room Resource to decline (this might confuse an end user: first one gets an accept from the Room Resource and later a decline will follow because of a check with Planon).
| | For an animated video explaining the difference between In-the-lead and Follows, please see our video channel |