GetTimetable/LUDUS: Difference between revisions
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. none|thumb|758x758px ==Setup== none|thumb|783x783px ===Format and content=== ===Description=== Name of the setting. ===Absence settings=== ===GetTimetable/Exp..." Tag: Recreated |
|||
| Line 6: | Line 6: | ||
===[[GetTimetable/Format and content|Format and content]]=== | ===[[GetTimetable/Format and content|Format and content]]=== | ||
===[[GetTimetable/Subscription - Notification settings|Subscription - Notification settings]]=== | |||
===Description=== | ===Description=== | ||
Latest revision as of 12:51, 5 November 2026
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
Description
Name of the setting.
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 reasons from students nack to Ludus.