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 3 Next »

MyTimetable 3.1 is currently in the state 'in development'. These release notes are work in progress, and planned features may change at any time. MyTimetable 3.1 is tracked using the git branch master.

MyTimetable 3.1 contains some features that have been moved from 3.0, and is currently still work in progress.

All work involved in upgrading to the latest MyTimetable version (configuration, building, testing) is free of charge for our customers with a Software Assurance or All-In support agreement.

Functional changes

  • PLANNED Incremental sync for external calendars — At the moment we only offer a daily 'full sync' of a timetable. MyTimetable 3.1 build will also offer incremental synchronisation, where changes in the timetable will be synchronised almost instantly.
  • Support for Semestry TermTime was added — MyTimetable now features support for Semestry TermTime. Not all features have been implemented yet, but we will work with Semestry's customers on adding as many features as necessary for a great user experience.
  • Web Room Booking support in S+ provider — The Syllabus Plus provider now offers the possibility to show a user's web room bookings in the interface as a separate timetable (based on the username included in the web room booking).
  • API: deduplicate acitivities by default — Previously activities returned from API requests would not be deduplicated (i.e., each activity always belonged to one subscription/timetable key). This has now been fixed. We do not anticipate any issues for existing API users as the data format has not been changed.

Non-functional, technical and back-end changes

The following changes have been made to the MyTimetable backend and underlying software, and have no direct impact on MyTimetable functionality:

  • PLANNED New Syllabus Plus backend — The new backend will offer better performance and will be ready to support change detection and notifications. ERDB 3.1.x support will probably be dropped, since almost all of our customers have already moved to ERDB 3.2+ which has a new schema.

  • Many dataprovider specific configuration properties have been renamed. This allows us to publish timetables from different software products in the same MyTimetable instance.
  • SAML IdP metadata can now be read from a file instead of an URL.
  • The following dependencies were upgraded:

    • Spring (4.2.4)

    • Spring Integration (4.2.4)
    • Spring Security (3.2.9)

Removed and deprecated features

The following features from earlier MyTimetable versions have been deprecated, removed, or partially removed and are not supported anymore:

  • None as of yet.
  • No labels