Exchange to Dime.Scheduler

This article is concerned with the message flow from Exchange to Dime.Scheduler.

How it works

This part of the synchronization is rather a technically complicated story but the end result is simple enough: any manipulation of any event of any resource that is tracked by the Dime.Scheduler Exchange may potentially end up updating the schedule in the planning board in Dime.Scheduler.

Note that this description allows for more room for interpretation. There is room for configuration and customization to give ultimate control to the planner and prevent resources from fiddling with the planning. In theory, resources could change appointments that are managed in Dime.Scheduler, but as you can imagine, not every planner will want this type of collaboration. Also, not every resource will want to share his entire calendar with other people.

Configuration

There is an entire section dedicated to the configuration of the 'Exchange to Dime.Scheduler' message flow:

Appointments will be sent to Dime.Scheduler for the resources that meet the configured criteria (by either the administrator or the resources themselves):

• Enabled
• Show as status (multiple choices)
  • Free
  • Tentative
  • Office
  • Out of office
• Sensitivity (multiple choices)
  • Normal
  • Personal
  • Private
  • Confidential

Configuration

The connector listens for events in Exchange and pushes them to Dime.Scheduler, and to do that, you need to provide some parameters. Same as the Dime.Scheduler to Exchange message flow, we need some details about the Azure App Registration:

• The client id of the Microsoft Entra ID application
• The client secret of the Microsoft Entra ID application
• The tenant id

All these parameters can be configured in the Exchange config section in Dime.Scheduler. Instructions to set up the Microsoft Entra ID application can be found here.