iSAMS: Synchronising a Future Timetable

iSAMS has a number of different timetable types and we synchronise those which are marked as "published". Where a timetable isn't in force yet, you will probably find that it is marked as a "development" timetable. This article shows you what to do to make these timetables synchronise into your Room Booking System. 

Check the timetable is set up correctly

  1. The timetable should be in development. You can check this in iSAMS by going to Configuration > Manage Timetables and looking for an icon in the development timetable section:
  2. Check with your colleagues that the timetable is ready to be added. Development timetables can still be changed, and any such changes will be reflected in the Room Booking System when the timetable is synchronised (usually overnight). You can use a timetable which is still being built and changed, but you should be aware that new timetabled classes could delete existing manual bookings if they clash.
  3. Ensure that the timetable has been allocated to weeks. This is usually done via the Configuration > Manage Periods and Days > Allocate Weeks section of iSAMS.
  4. If the new timetable structure differs from the old (e.g. you moved from a week with 6 periods to one with 8 periods), please send us an email with a screenshot of the new timetable layout for comparison with the old one. We will then work with you to find the best way to make the change as seamless as possible.

Pulling through the new timetable

When you're ready for the new timetable to be synchronised, you'll need to add the " Timetable Manager - Development Timetable Schedules" method to the API key you use for the Room Booking System. Save the changed key, then allow 1 hour for the change to be processed on the iSAMS API. Once the next automatic synchronisation (usually at 1am) has taken place the new timetable should appear on your system.

NOTE: Once the timetable has moved over to be the " published" timetable, we recommend turning the " Development Timetable Schedules" method off for the Room Booking System API key. This will ensure that you don't unexpectedly pull through a timetable which is actually still in development.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us