GetTimetable/TimeEdit: Difference between revisions
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
===[[GetTimetable/Export_settings|Export settings]]=== | ===[[GetTimetable/Export_settings|Export settings]]=== | ||
=== Object Types === | |||
This setting defines the object type that UMS will extract from TimeEdit | |||
You can enter more object types for each UMS object | |||
In the example below. UMS will extract classroom and location as a room in UMS. | |||
[[File:GetTimetable TimeEdit ObjectTypes Room.jpg|none|thumb|447x447px]] | |||
==[[TimeEditFields#Required_TimeEdit_fields_when_extracting_timetable_blocks|TimeEdit field information]]== | ==[[TimeEditFields#Required_TimeEdit_fields_when_extracting_timetable_blocks|TimeEdit field information]]== | ||
Revision as of 10:58, 1 December 2020
Requiements
UMS Modules
This feature only works if UMS has uploaded the data with our TimeEdit module.
Setting
Format and content
Description
Name of the setting.
Absence settings
Export settings
Object Types
This setting defines the object type that UMS will extract from TimeEdit
You can enter more object types for each UMS object
In the example below. UMS will extract classroom and location as a room in UMS.
TimeEdit field information
FAQ
What to do when TimeEdit replaces an existing timetable system such as SIS ?
When the school is ready to drop the old system, all old timetable data must be removed from UMS, else the enduser will see duplicated timetable blocks due days back / days ahead settings in both old and new system.