This is not yet field-hardened so please do not contact us looking to go into production this weekend. We won't let you make a decision that egregious.
There's also the issue of how we instantiate Travel Time (it goes in as an appointment with a Free-Busy Status of "Out of Facility"). See our previous post.
We've ignored Contacts for the moment.
Some screen shots.
So this on the Macintosh calendar:
Will become this on Microsoft Exchange:
And of course, meetings are really MEETINGS with guest responses. So on the Macintosh when Jimi invites Jerry to a meeting and Jerry accepts:
Travel Time, a feature not supported by Outlook or Exchange but loved in Apple calendaring we've implemented by inserting appointments with the appropriate durations in advance of calendar events.
So this on Macintosh
becomes this on Exchange:
The sharp-eyed among you will note that this does something different from our previous post -- it kept the name of the "seed" event in the travel time description. We experiment a lot with these things. Any preferences?
Keep an eye on this blog for one of our videos showing this in real-time. Probably after New Year's. We've got a lot of migrations going on in December.
To give you an idea what the configuration for this looks like:
You're going to need to map resources to SMTP addresses (not a big surprise I hope). You'll also notice above we set up the capability to read from a different Postgres database which makes it easier to copy your Apple iCalendar database to a more powerful Windows environment for insertion.