ExportUserInfoToAdminSystems: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 4: | Line 4: | ||
Users can update user info in [[UMS Web]] or [[App]] | Users can update user info in [[UMS Web]] or [[App]] | ||
== Supported admin systems == | ==Supported admin systems== | ||
===[[ExportUserInfoToAdminSystems/Lectio|Lectio]]=== | ===[[ExportUserInfoToAdminSystems/Lectio|Lectio]]=== | ||
Line 13: | Line 13: | ||
===[[ExportUserInfoToAdminSystems/SIS|SIS]]=== | ===[[ExportUserInfoToAdminSystems/SIS|SIS]]=== | ||
== FAQ == | ==FAQ== | ||
=== | ===How do I troubleshoot write back errors ?=== | ||
Restart service and look in UMS db, table ExportUserInfoToAdminSystems and logfile in usermanagement folder; ExportUserInfoToAdminSystems.log | Restart service and look in UMS db, table ExportUserInfoToAdminSystems and logfile in usermanagement folder; ExportUserInfoToAdminSystems.log | ||
===Why is data not written back to SIS?=== | |||
Institution number must configurered in the data source on the template, read more here: [[GetStudents/SIS]] | |||
<br /> |
Revision as of 11:15, 5 June 2019
ExportUserInfoToAdminSystems.exe, this runs as as service and must be set up, read more here: Configurator/Services
About
Users can update user info in UMS Web or App
Supported admin systems
Lectio
ExportUserInfoToAdminSystemsLectio.exe - must run as scheduled task, the normal service does not work for this,
EASY-C
LUDUS
SIS
FAQ
How do I troubleshoot write back errors ?
Restart service and look in UMS db, table ExportUserInfoToAdminSystems and logfile in usermanagement folder; ExportUserInfoToAdminSystems.log
Why is data not written back to SIS?
Institution number must configurered in the data source on the template, read more here: GetStudents/SIS