Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Note that this functionality is currently in beta.

If the customer is unwilling to accept the permissions we ask for in the regular setup, this page describes an alternative way of setting up resource booking with MS365. The downside compared to the regular setup is that this requires some work on the customer side. It basically means that the customer sets up the calendar subscription and passes the events on to us.

Description 

The MazeMap resource booking has a cache in order to be able to display occupancy in a timely manner. For the cache to work, it needs to know about calendar events so that it can refresh the cache for that calendar.

Instead of MazeMap subscribing to the calendar (see the page describing regular setup for details), the customer can subscribe to calendar events and set the notification endpoint to us.

The customer needs to run something; a script, a program, an Azure function, or something that makes the call to set up the subscription. It can be as easy as a command line curl, or a python script. The script could probably be run as an Azure function if that is something the customer is familiar with.

Note that making changes to the resources that changes the resource ID in Microsoft, or adding new resources or deleting old, requires setting up the subscriptions again.

If the customer wants the solution to support active changes in Map Editor and booking cache updating itself, then the customer can run an Azure function which we can call that sets up the subscriptions we need. How the subscription is set up is still controlled by the customer, but we can help develop the function.

  • No labels