GetTimetable/Ludus: Difference between revisions
Jump to navigation
Jump to search
Created page with "==Requirements for writing absence to LUDUS== You will need to open this webservices in LUDUS (marked in red) if UMS is going to write absence back to LUDUS. File:GetTimetab..." |
|||
Line 16: | Line 16: | ||
This will only write information back to LUDUS if the activity starts with '''UMS'''. | This will only write information back to LUDUS if the activity starts with '''UMS'''. | ||
=== Ludus absence codes -> UMS Absence codes === | ===Ludus absence codes -> UMS Absence codes=== | ||
Specify how the Ludus absence codes translates to the absence codes in UMS. | Specify how the Ludus absence codes translates to the absence codes in UMS. | ||
This will also enable UMS to write the absence | This will also enable UMS to write the absence reason from the student back to Ludus. | ||
==FAQ== | ==FAQ== |
Revision as of 12:52, 7 December 2020
Requirements for writing absence to LUDUS
You will need to open this webservices in LUDUS (marked in red) if UMS is going to write absence back to LUDUS.
Setup
Format and content
Description
Name of the setting.
Absence settings
Export settings
Only write back test data to LUDUS
This will only write information back to LUDUS if the activity starts with UMS.
Ludus absence codes -> UMS Absence codes
Specify how the Ludus absence codes translates to the absence codes in UMS.
This will also enable UMS to write the absence reason from the student back to Ludus.