Page tree
Skip to end of metadata
Go to start of metadata

MyTimetable 4.0 has been superseded by our continuous release process and is no longer supported. For supported MyTimetable versions we refer to the 2019.x releases. MyTimetable 4.0 is tracked using the git branch rb-4.0.

MyTimetable 4.0 is the big 'notification release'. MyTimetable is now able to detect changes in timetables and communicate these changes to the users. At the moment we are still fine-tuning some of the details of this functionality, so this version is not available to all customers yet.

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

  • Change detection — MyTimetable now 'indexes' all timetables and detects changes in the timetables. The notifications and incremental sync features depend on this change detection process. The indexing requires a PostgreSQL database and is currently only available to customers using our managed hosting platform.
  • Notifications — Users can choose to receive notifications of changes to their timetable. The notifications are sent using email, SMS or the university's mobile app. The notifications require additional components and are currently only available to customers using our managed hosting platform.
  • Incremental sync for external calendars — If a change it detected, the user's push synchronisations will be updated immediately. This only applies for customers where change detection is enabled.
  • GP-Untis support — MyTimetable now supports GP-Untis timetables, easily published from the timetabling application.
  • OSIRIS support — MyTimetable now supports personal student and staff timetables coming from OSIRIS Link.
  • Simac Presto support — MyTimetable can now show the student's attendance from Simac Presto, and allows staff members to register attendance in Simac Presto directly from MyTimetable.
  • iCalendar timetable statistics — The administrative interface shows the number of subscriptions to iCalendar-based timetables.
  • Publication rules: section condition — A publication rule condition was added to match on the sections attached to an event.
  • Admin: stale user cleanup — It is now possible to cleanup stale users from the administrative interface.
  • Admin: inactive subscriptions cleanup — It is not possible to cleanup stale subscriptions from the administrative interface.
  • API: support roles for API users — It is now possible to assign security roles to API users. For now, this functionality is not yet available in the interface, but only through the database.
  • As usual, many small bug fixes and improvements were added to this version.

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:

  • New Syllabus Plus backend — The new backend offers better performance and is ready to support change detection and notifications.

  • New TermTime backend — The backend to TermTime was reimplemented for more features and better performance.
  • ActiveMQ removal — ActiveMQ is no longer necessary for the communication between the MyTimetable web interface and the push synchronisation components.
  • Push synchronisation consumer and producer services merged — Only one additional component is now necessary to offer the push synchronisation functionality.
  • API converted to Spring MVC — The API was rewritten to use Spring MVC instead of Apache CFX. Due to this, some specifics in the API input and output may have changed. Nevertheless, correct API requests should behave exactly as before.
  • Many dependencies were upgraded.

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