UmsWiki - User contributions [en]

Attendance Registration Advanced

2019-12-04T09:44:03Z

Phk:

Attendance Registration Advanced is an add-on module that gives extra functionalities to [[Attendance Registration]]. With this module, you gain access to an advanced statistical interface that makes it even easier to monitor attendance.

Attendance Registration Advanced offers you these advantages:

*You have access to a web-based view of the students’ attendance records and a statistical interface, making it easy to keep overview of the students' attendance activities. Students can keep track of their own attendance, while teachers, student counsellors, and school management can see attendance for students and classes relevant to them. When you log on to UMS Web, you will see different data if you are a student, teacher, student counsellor, or manager. This means that you will only see information relevant to you.
*You also have access to a [[Guardian Portal]], allowing parents, guardians, employers, social workers, and internship mentors to follow a student's progress during schooling. The [[Guardian Portal]] gives you access to the student’s timetable, attendance records, and grades. If there are new occurrences, you will automatically be notified. The portal also allows you to monitor several students at the same time if you e.g. have more than one child attending the school.
*School employees can create attendance reports through the web interface. The reports can be created for one or several students, e.g. based on the teacher of a class or the contact teacher for a group of students.
*Students can subscribe to text messages that will be sent when they are registered as absent. The text messages shows that the school engages in the students and invites the students back to the classroom (requires [[SMS Send]]).
*It is possible to print attendance sheets that teachers can use for e.g. field trips or in classes where it is not possible to register attendance through a computer (requires [[Merge Letters]]).

==Prerequisites==

===Supported administrative systems===

*EASY - (W031) (requires subscription to do so through STiL)

===Module requirements===

*[[UMS]]

*[[UMS Academic Web]]

*[[Attendance Registration]]

===Testing after setup===
To start testing after setup, you must log in as a teacher. See if you have access to attendance statistics on the front page of UMS portal. Please note that the module only will appear when the registered data is more than one day old.

To ensure that the system writes back to EASY, you can review the log files: Absence_ExportToAdminSystems.log. There are also logs in SQL table job_logs.

===What to have ready===
In order for the system to write back attendance data to EASY, it is necessary to:

*Have a running [[UMS]] installation and our module [[Attendance Registration]].

*Contact UNI-C to gain access to W031. Have your institution number from UNI-C ready. You will be provided with a PIN code and access to W031. You can read more about W031 [http://admsys.stil.dk/EASY-A/Webservices#W031%20Registrer%20skemabaseret%20frav%C3%A6r here].

*The IP address on the UMS server must be open in EASY.

==Installation==

===User access===
Access to the attendance statistics interface is controlled with a standard AD group membership. The AD group membership will function whether the AD group is Global, Universal or mail-enabled groups.

In order to edit settings for Attendance statistics, you can access the menu in the UMS Configurator by clicking on 'Web Setup' and selecting 'Absence'. See example below.[[File:Absenceadvancedwebsetup.png|none|thumb|630x630px|Web setup]]

The following settings are needed for Attendance Registration Advanced:

*Headmaster access:
**Members of the chosen group has access to the schools overall statistics.
**If left blank, nobody has this access/role.

*Counsellor access:
**Members of the chosen group is treated as “student-counselors” which gives access to special note-types.
**If left blank, nobody has this access/role.

*Standard access:
**Members of the chosen group is treated as “standard-teachers” with access to all relevant absence-statistics for activities, students and so on.
**If left blank, nobody has this access/role.

*Show new/old check boxes:
**These check boxes are available so that you can choose whether to see either the old or new version of Attendance Registration Advanced. This option will be removed in later versions (when older version is end of life)

Please note that changing these settings will require an IIS-reset on the frontend.

==Technical settings==

===Export to admin-system===
The Write back webservice need to be setup so that the registered absence registrations can written back to the admin-system (EASY C).

For setting up the write back absence you need to have a PIN code for the write back webservice (W31) from STIL. The data is entered under the data source for the timetableblocks, which is found under “Modules/Timetable/Data sources”
[[File:Absenceadvanceddatasources.png|none|thumb|584x584px]]

Edit the required data source, i.e. EASYC.
[[File:Absenceadvanceddatasources2.png|none|thumb|602x602px|Data sources]]

Enter the institution number and write back pincode:
[[File:Absenceadvancededitdatasource.png|none|thumb|655x655px|Edit data source]]

After the write back settings are entered, it is also necessary to ensure that the service that sends the data is started/running. Services are controlled through the menu 'Settings\Services'. Please see below.

*'Absence export to admin systems': Enter a computer name for the server that you want the service to run on. Restart the service on the selected computer, and check the log file for connection status of the service (<install path>\UserManagement\Absence_ExportToAdminSystems.log).
*'Geocode': Enter a computer name for the server that you want the service to run on. Restart the service on the selected computer, and check the log file for connection status of the service (<install path>\UserManagement\Geocode.log).

[[File:Absenceadvancedservicessetup2.png|none|thumb|626x626px|Server settings]]

===Geocode service===
The Geocode service is responsible for collecting geo data for students' addresses (for use in the Absence Stat Interface). For the service to work a Google token is needed.

The token has to be entered under 'Settings/Geocode'.

If no token is entered, you need to sign up for one at Google. Simply click the 'How to get token' link, and follow the directions.[[File:Absenceadvancedgeocode.png|none|thumb|653x653px|Google authenication token for Geocode]]

Enter the acquired token and make sure that the Geocode is allowed to run on a server under 'Settings/service'. Please see the picture 'Server settings' above.
==FAQ==
SSN usage:

If you want to see and use SSN in the search, and wants the information shown in Attendance Registration Advanced - there's an option to enable it on all searches made by UMS.
[[File:SearchSettingsSSN.png|thumb|This shows the search settings options
Found inside Website Settings -> Search Settings -> Select setting -> Check Show SSN for selected types.
|none|870x870px]]'''Absence registrations export to admin-system Error'''

28-10-2019 07:48:09 - Inlogic0805 - SLI_ID = 2132443 - Skemabegivenhed = 7138184413 - Status = G - Minutter = -1 - Institutions nummer = 8821xxx

28-10-2019 07:48:09 - (UpdateEasyW031) Update Error Username = Inlogic0805 - TimeStamp = 13-03-2019 08:39:48 - ErrorCode = 6 - ErrorText = elev. 2109xxxxx, dato 15.02.2019, lektion: 4 eksisterende fravær kan ikke overskrives.

28-10-2019 07:48:09 - Inlogic0805 - SLI_ID = 2132443 - Schedule event =7138184413 - Status = G - Minutes = -1 - Institution number = 8821xxx

28-10-2019 07:48:09 AM - (UpdateEasyW031) Update Error Username = Inlogic0805 - TimeStamp = 13-03-2019 08:39:48 - ErrorCode = 6 - ErrorText = student. 2109xxxxx, date 15.02.2019, lesson: 4 existing absences cannot be overwritten.

'''''The error occurs because Easy does not allow correction of existing absenteeism due to the time for correction of absenteeism being exceeded in Easy'''''
 

===How does the statistics handle student pauses?===
The statistics will calculate absence percentages using the following: 
a = Minutes absence 
p = Minutes pauses 
o = Offered lessons in minutes 
 
absence percent = (a-p)/(o-p)

Attendance Registration

2019-12-04T09:40:24Z

Phk:

Attendance Registration is a tool for the educational sector that makes it easy to register attendance. Through a simple and intuitive interface, the teacher can register who is present, who is late, and who is absent. Registering attendance can be done in a matter of seconds, simply by clicking the button with the student’s name and picture. The interface uses colour codes, which makes it easy to see what the individual students are registered as. You decide which attendance options you want to use - i.e. options for being late, for legal absence, and illegal absence - as well as which colours are used for the different options. When attendance is registered, UMS automatically writes back to the administrative system - if supported. The interface also supports the possibility to see if the student has sent a text message to the school or if the staff has written notes regarding the student’s attendance.

There are references to other UMS modules, e.g. SMS, in this guide. In case the mentioned modules are not present in your environment, you can ignore these settings.

In order to edit templates, it is also required to have a basic knowledge about the UMS configurator.

==Prerequisites==

===Supported administrative systems===

*Easy-C

*Lectio

*SIS

*Other systems where it is possible to retrieve a timetable for students and teachers

===Module requirements===

*[[UMS]]

*[[UMS Academic Web]]

===Testing after setup===
To start testing after setup, you must log in as a teacher. See if you have access to attendance registration on the front page of UMS portal.

Click on attendance registration and check that you can search for timetables for students, teachers, and classes.

Check that you can register individual students as absent.

===What is necessary to get started===
To get started, it is necessary to have a running [[UMS]] installation.

==Installation==
Install [[UMS]] and [[UMS Academic Web]]

==Technical settings==

===Settings for UMS Attendance Basic===
All settings for UMS Attendance Basic is set in the configurator. In the main menu under 'Settings/Services', it is necessary to set the 'Absence service' to run on a server. The service is responsible for sending text messages to students that are registered as absent. Please make sure the service has started and is running. See example of the set up below.
[[File:AbsenceServiceSetup.png|none|thumb|636x636px]]

===Global settings===
Global settings are settings that are valid for the entire school. For settings that can be altered per education, class, or similar, see 'Individual settings'.

The Global settings are:

*Attendance colours
*Design text messages sent to the students
*Granting access to teachers/employees and edit access to registration forward-looking
*Edit attendance types (late, approved, not approved)

====Attendance colours====
Settings are found under 'Modules\Absence\colors' in the main menu. Simply select the colours you want to use for each type of attendance. See example below.
[[File:Absencecolor.png|none|thumb|573x573px]]

====Designing text messages sent to the students====
It is possible to preset text messages that will be sent to students if they are registered as absent. The settings are found under 'Modules\Absence\SMS' in the main menu. The text messages can be set for each type of attendance both in Danish and English. It is also possible to create multiple text messages for each type of attendance. If you create multiple messages, the system will randomise these messages. Meaning, the system will send different messages to a student each time attendance is registered. See example below.
[[File:Absencesms.png|none|thumb|598x598px]]

When you edit a message, there are several variables that can be used to ensuaking the messages more personalised. See example below.
[[File:Absencesmsvariables.png|none|thumb|670x670px]]

====Granting access to teachers/employees and edit access to registration forward-looking====
Granting access to functions in the registration interface is done under 'Setup web access/Absence'. Attendance basic allows 'register access' and 'Future registration access'. Enter a group (nested groups are allowed) with the teacher/employees that are allowed to use the specific function. See example below.

The checkboxes have the following meaning:

*'Count too late on statistics' – Not used for Attendance basic
*'Show empty days' – Should the day ruler show or omit days with no planned timetable?
*'Show weekends' – Should the day ruler show or omit weekends?
*'Show legal' – Is legal attendance used on the school/is it shown in the protocol?
*'Show illegal' – Is illegal attendance used on the school/is it shown in the protocol?
*'Show too late' – Is too late attendance used on the school/is it shown in the protocol?

[[File:Absencewebsetup.png|none|thumb|828x828px]]

=====Edit attendance types=====
To edit letters and text used in the attendance module, choose the button 'Select' (see the window above).

Double-click on the row containing the settings you want to edit. See below.
[[File:Absenceselect.png|none|thumb|874x874px]]

===Individual settings===
Individual settings can be altered per education, class, or similar. For settings valid for the entire school, see 'Global settings'. If an individual setting for a specific group is needed, it is necessary to create the group with the students in question beforehand. These settings can be altered under Configurator\Templates\Edit\Absence\Manage\Add a new or edit an existing setting.
[[File:Template Absence Setting.jpg|none|thumb|784x784px]]
 

====SMS and App settings for notify absence====

*'SMS Sick Keyword' - The keyword set in this box will define which keyword the student sends in a text message to notify absence. E.g. the keyword 'Sick' means the student has to send a message containing 'sick' or 'sick %reason or message to the teacher%'. Both cases will be accepted by UMS. All text after the keyword will not be stored in UMS.
*'SMS absence Keyword' - The keyword set in this box will define which keyword the student sends in a text message to notify absence. E.g. the keyword 'Sick' means the student has to send a message containing 'sick' or 'sick %reason or message to the teacher%'. Both cases will be accepted by UMS. All text after the keyword will be stored in UMS.

*'Default incoming SMS status' - These are settings for which type of attendance the system should set as default when receiving a message from a student notifying absence. The teacher will see this status in the attendance registration interface. E.g. when the default type of attendance is 'Legal absence', students will be marked as 'Legal absence' when notifying absent
*'Ignore messages for today start/end' - In the set time span, it is not possible for a student to send a text message to notify absence. This means that if the message is received before the given start time, e.g. 10 a.m., the system will check the students schedule for timetable blocks that day and mark the blocks with the default attendance status, e.g. 'Legal absence'. The system will then send a reply confirming the student is marked absent. If the message is received between the start and end time, e.g. 10 a.m. and 3 p.m., the system will send the student a reply, saying it is not allowed to notify absence at this time. If the message is received after the given end time, e.g. 3.pm., the system will check the schedule for timetable blocks the following day and mark those with the default attendance status, e.g. 'Legal absence' If this feature is set to 00:00 - 00:00 students cannot register as absent. If you want an "Always register for the current day"-functionality, set it to 23:59 - 00:00
*'Require reason' - The school can require the students to give a reason when notifying absence. Check this box if students have to write a reason in order to register as absent

====Misc settings====

*'Use cards' - This enables students to register via their student ID's via Bianco. Check this box if the student is allowed to register via card
*'Show watermark at %' - If the school has a limitation for how high attendance percentage is allowed for a student, this can be set as visible. Check this box if it should be visible if the students are above the accepted limit
*'Days back' - This setting decides how many days backwards a teacher is allowed to register and edit attendance. Set the number of days that are allowed in the drop-down menu 'Days back'. Please note that this setting cannot exceed the number of days backwards in the global timetable block data job!
*'Too late' - This shows the number of minutes a late show should count. 'Too late' sets the number of minutes late attendance should count. If a student is late for class it will be registered as e.g. 10 minutes absence. Set the number of minutes that should count in this box
*'Show percent on studentstat' - Check this box, if students are allowed to see their attendance percent under 'My attendance'
*'Send SMS' - When a student is registered as absent, the system can reply with a text message. Check this box to enable the system to send a reply
*'Default calculation view' - Choose between "Display calculation in lessons" or "Display calculations in minutes"
*'Lesson length' - Number of minutes one lesson counts for
*'Time interval for calculation' - Select the time interval for the calculation of my absence
*'Show Course' - Check this box to show course view for students' 'My absence' in both web and app
*'Show Activity' - Check this box to show activity view for students' 'My absence' in both web and app
*'Show Grades' - Check this box to show grades in statistics

====Student reason settings====

*'Allow students to register absence reason' - This setting allows students to create an absence reason when they are registered as absent
*'Use Cutoff Day' - This setting changes the 'Register absence' feature from being reliant on a specific amount of days back, to instead be fixed to a specific amount of days into a month.
*'Cutoff day of month' - At this day of the month the absence gets "locked" for the previous month.
*'Days back' - This sets how many days backwards students are allowed to add an absence reason on a course. E.g. the student can register an absence reason 7 days backwards
*'Show admin notes in app' - Changes whether the student can see administration-written notes on absence entries.

==FAQ==

====What to do when a teacher can't register absence X days back ?====
A specific day in the absence registration system has a green checkmark if the teacher is allowed to register according to "Days back" absence settings on the template in UMS Configurator.

Only members of the AD group configured in Websetup are allowed to register more days back than teachers.

 

====What to do when abscence can't be registrated due to double registration ?====
This error is due to double absence registration. Absence should be deleted in the administrativ program.

(UpdateEasyW031) Update Error Username = benj4896 - TimeStamp = 26-09-2018 10:14:55 - ErrorCode = 6 - ErrorText = elev. 2510015153, dato 26.09.2018, lektion: 2 eksisterende fravær kan ikke overskrives

====How can a teacher know that if a student has a pause?====
If a student has a pause, a small pause icon will be shown for that student.
Hovering with the mouse over the icon will show the pause interval. 
The system will automatically handle how much absence a student should have, if they don't show up, but they have a pause.

Attendance Registration - QR

2019-12-04T09:37:06Z

Phk:

Attendance Registration QR is a system developed for schools, that functions along with the UMS App. The system allows students to register their own attendance by scanning a continuously-changing QR code. The students can scan the QR code when they arrive, and use the app to check out again when they leave again. The QR system makes it is easy to monitor the students’ attendance, as all registrations automatically will be available in UMS.

Through the user-friendly interface, the teacher can see if everyone have registered correctly and make corrections if necessary. This system does not integrate with any third parties. If you need integration to any system, please contact us for price and availability.

 

==Prerequisites==

===Module requirements===
[[UMS Web]]

[[App|UMS App]]
 

===Testing after setup===
Students can check in by scanning the UMS-generated QR code, and check out, using the UMS App
 

===Is any physical items required===
A student (or school personnel that can log in as a test-student) must have an Android or iOS smartphone, with their schools UMS app installed
 

==Installation==

===Configurations===
Settings can be found under 'Web Setup -> Absence -> ''Scroll to bottom'' -> Check in/out settings'

[[File:Attendance QR Setup.png|frameless]] 

==Settings==
[[File:QR settings.png|frameless]]
 

*Refresh timer: How many seconds a QR code should stay, before it refreshes
*Timer deadzone: How many seconds, after a QR code expires, it should still remain usable behind the scenes.

 

==Student Pauses==
QR Registration handles students having pauses, down to the minute without the students having to do anything.
If a student is too late, but some of that time was during a pause, they will only get absence for the minutes they where actually absencet.
If a student has a pause in the middle of the class, and they check out and then check in again before the pause ends, the QR system will not give them any absence for that.

==FAQ==
 

*''Why have a deadzone?''

The deadzone was made to facilitate the scenario where there's 1 second left of the QR code, the user scans the QR code, but before the server receives the request, the code has expired and the user gets an error saying 'Expired/invalid QR code'.

SMS From CSV

2019-08-08T11:42:28Z

Phk: Added Configurator settings.

=== Access ===
From the Configurator - > Website Settings you can select which AD Group should be able to access the SMS From CSV feature.
[[File:SMS Csv Settings.png|left|thumb|Options to show/hide SMS CSV ]]

To see SMS From CSV you must be a global admin or part of the selected AD group.

If you select "show SMS on front page" the option will be shown on the frontpage as well as in the control panel.

=== Sending SMS ===
Your csv file should be structured with two columns that are separated with a semicolon ;

*mobile number
*message

The first row defines the column header name (e.g. mobile and message). All the following rows are will be send with the first column being the receivers mobile number and the second column the message that will be send.

For linebreaks use <nowiki> </nowiki>

Example of csv:
mobile;message
42408883;Min første besked
41787710;Min anden besked
41787710;Min anden besked<nowiki> </nowiki>new line

File:SMS Csv Settings.png

2019-08-08T11:40:15Z

Phk:

Options to show and hide CSV SMS in the configurator

App

2019-04-04T05:59:51Z

Phk: "refactoring" language, and small english fixes.

[[File:UMS School App.png|frame]]
UMS School App is available for iPhone, Android and Windows Phone. It will be designed with the school’s own logo, color and style. The app gives the basic functionality to see:

*News
*Timetable
*Homework
*Grades
*User information

Additional licenses gives the ability to create, edit and see more information from various modules. For an overview of module requirement see "[http://wiki.inlogic.dk/index.php?title=App&section=6&wteswitched=1#Additional_functionality Additional functionality"]

==Support==
We provide regular support for the following and newer versions:

*Android version 7.0. We support the same versions as Google provide security updates for. Find an overview [[wikipedia:Android_version_history|here]].

*iOS version 10

*Windows 10 Mobile (version 10)

Please note that it is possible to run older versions. If support for older versions is needed, we offer support at our hourly rate.

==Prerequisites==
===Supported administrative systems===

*Userinfo: Easy-A, SIS and Lectio (Only mobile number).
*Grades: Easy-A, Lectio and SIS
*Homework: Easy-A and SIS.
*Timetable: Easy-A and SIS
*Attendance registration: Timetable data is retrieved from Easy-A, SIS, LUDUS, Tabulex and Lectio. Howerver, absence is only registered to Easy-A

===Module requirements===

*UMS Web (contains and run all the webservice that is required for the app to receive information and communicate with the server)

===Additional functionality===
You get more functionality in the app by having the following modules, these are all optional:

*Attendance Registration: Gives “Your attendance”, which shows student statistics, the student are able to add absence reason and see their absence status in the timetable
*Attendance Registration for UMS School App: gives employee “attendance registration” and student the ability to "report absence"
*Homework: gives the employee the ability to create homework
*Link Collection: gives links/bookmarks the school can setup
*User info: gives “Your information” the ability to edit the information. This also adds the functionality for the user to upload a new profile image (a selfie) to be used in the student id card
*Student & Employee Id: Gives the students a “student id card” and the employees an “employee id card”. To update their student id card profile image you’ll need the “User info” module
*Parking: Parkzone & APCOA Integration. Gives the option to create and edit parking permits from Parkzone and APCOA
*User information (add/edit)

Note: All Attendance functionality requires Attendance Registration.

===Testing after setup===

The app will be tested internally at inLogic before release. The test requires access to a user with relevant data. You can either create a fictional student who is associated to a real course, or alternatively use a real student's account, if the person agrees that the account is being used for a system test of the school's APP.

===What to have ready===

*'''Important''': The UMS site needs to use HTTPS and be public available. It needs a valid SSL certificate.
*Materials that can be used for designing the app. For example: Logo, brochure, design guide line, etc.

*Optional: It is possible for the school to have its own account where the app is located. An account in the App Store cost $99 per year, while an account for Google Play costs a onetime fee of $25. The school self-manage these accounts.

===Physical hardware requirements===

Having a smartphone is a necessity, either an Android, iOS or a Windows 10 Mobile.

===Should third party be contacted===

If the school is using a dedicated hosting service, they have to be informed on how you wish the news feed should be setup.

==Installation and setup==
inLogic will publish and update the app.

If you want your own AppStore and Google Play store pages, you will need your own Apple Developer Account for the iOS version, this is a requirements from Apples Guidelines. [[App Store Connect|Please follow the guide App Store Connect]].

Android and Windows Phone can be published through inLogics account or your schools own account (if you have acquired one). If you have your own account inLogic needs to be informed as well. To publish the app, inLogic needs the following information:

*[[UMS Web]] url address- This is the address that you use wen you access UMS Web. (If you are running any kind of gateway (TMG, UAG etc.) you will need to create rules for the services on UMS Web, contact us for more information)
**''<nowiki>https://*****.dk/</nowiki>''

===My School App===
My School App is the inLogic app that is hosted by inLogic, this lets your school get started using the app faster and cheaper, and also there is less maintenance for you.

======What does this mean?======
Pros:

*Lower start-up price.
*No need to set up an Apple Developer account.
*Upon contacting InLogic Support your app can be live within a few hours.
*You can change logo, images & colors after the app is deployed

Cons:

*The app will not be called your schools name on you phone and in AppStore/Google Play, but is instead called 'My school app', and its app icon cannot be customized.
*When students & teachers starts up the app for the first time, they will need to select their specific school before proceeding to login.

 

=====Setting up My school app=====
<blockquote>Configurator -> Web setup -> App -> Setting</blockquote>Here you need to configure a Primary and Secondary color, as well as a Logo. The Login background and Menu background images are optional.

The first time you set this up, you will need to contact InLogic support, and provide the following:

*A 64x64 pixels version of your logo (this logo is used in the the login dropdown, it will make it easier for users to find your school)
*UMS Web url (See [[App#Installation and setup|Installation and Setup]])

==Styling==
To style the app following is needed:

*Primary color
*Secondary color
*Logo (.png, vector file: .psd, .ai etc.)
*Icon for app logo (.png, vector file: .psd, .ai etc.)

The primary color will mostly be used as the default background color. The secondary color is the highlight color, and will be used when something is active or being activated like a button.

Optional:

*Background image for login (size 1080x1920)
*Background image for top bar of menu (size 1080x480)

===Examples of styling===

*Primary and secondary colors

[[File:App - Timetable view.png|none|thumb|Example of primary and secondary colors used in the app.
The primary color is used in the Header navigation bar, and the secondary color as border on the selected Calendar date
]]

*The schools logo - Max. 1024x576

[[File:Branding-af-app-inLogic-logo.png|none|thumb|Example of the inLogic logo used in the Demo app]]

*App logo - 1024x1024. If not supplied, inLogic will generate an App logo based on the schools logo (does not apply to My School App)

[[File:Simulator Screen Shot - iPhone SE - 2018-05-15 at 12.57.23.png|none|thumb|Example of app logo in use]]

*Login background image - 1080x1920. If not supplied, a white background will be shown, with your logo on top

'''''NOTE: The app will place your logo on top of the background image. This means when you supply a background image, it needs to be without logo on it.'''''[[File:App - Login screen.png|none|thumb|Example of a background image used on the Demo app login screen.
The school logo will be displayed on top of the background image, as seen here
]]

*Menu top bar image - 1080x480. If not supplied, a white background will be shown

[[File:App - Sidebar menu.png|none|thumb|Example of an image used on the Demo app menu view]]

==Technical settings==

The following sections show how to configure the app. This information only applies to services that are directly connected to the app, i.e. how to set up schedule tasks in the app. The only exception is 'UMS RSS Feeds', which is a specific service for app. If a fully detailed setup guide is needed, please go to that specific module.

Some of the configurations are not set up specifically for app, i.e. ParkZone. If you cannot find the setup guide you are looking for, you can find it by searching or on the front page. Please note that some changes made in the configurator not only will affect the app but also UMS Web.

'''Important''' As many settings only loads once the website is initializing, most changes require an IIS reset on the server. The app retrieves settings from UMS once a day, which means that changes will be visible the next time you log in or the next day.

===Menu Settings===

You are able to set the order and which menu buttons should be shown per template for the users

#Open UMS Configurator
#Templates -> Edit -> select a template -> App
#Under Menu order select Manage -> Add
#Write a Description
#Drap and drop the menu you want

[[File:MeunOrderSettings.png|none|thumb|789x789px]]
Here three menubuttons will be visible to the users on that specific template.

===History===
Before version 2.0.917, you used to choose the modules displayed in the app via the Configurator -> Web Setup.

We have moved the menu order into the Configurator -> Template Editor -> App -> Menu order.
[[File:Menu settings history.png|none|thumb|1600x1600px]]
This change was made to allow a different menu items and orders on Templates.

===News===

----

This describes how to setup news for the app.

*App News created from UMS Web
*Add a RSS feed
*Add Facebook feed

It is possible to use all three setups together. Combine as you like and set difference feed for difference templates.

====Setup for App News from UMS Web====

You need to create or use an existing AD group. This group will have access to create and modify news in
App News on UMS Web.

#Open UMS Configurator
#Menu -> Web Setup -> Edit -> App
#Add the AD group for News Access group

[[File:App newsaccessgroup.png|none|thumb|767x767px]]

====Setup for RSS feed====
Add server name for the service for RSS feed in Menu -> Modules -> Settings -> RSS Feeds

[[File:App rssfeedservice.png|thumb|none|594x594px]]
To setup Rss feed you will need the url for the rss. (E.g. http://inlogic.dk/feed)

Menu -> Templates -> Edit -> select template -> Rss Feeds

Manage -> Add… -> Fill in description, feed url and access token
[[File:App rssfeedurl.png|none|thumb|920x920px]]
'''Note:''' You only need an access token if the feed is from Facebook

The RSS feed runs as a service called “UMS RSS Feeds”. Default running every 5 min.
[[File:App services.png|none|thumb|561x561px]]
Restart the service to test it and check the output in /UserManagement/RSSFeeds.Log
[[File:App rssfeedlog.png|none|thumb|944x944px]]

====Setup for Facebook news====

If you want to use a Facebook page news feed, you need two things:

*Facebook Page Url Feed
*Access Token

=====Facebook Page Url Feed=====

To create the feed url

#Get your facebook page url
#*E.g. https://www.facebook.com/inlogic.dk
#Copy the name. E.g. “inlogic.dk”
#*Note: this can also be a number “142642699097242”
#Replace “inlogic.dk” with your name in this url
#*<nowiki>https://graph.facebook.com/v3.0/inlogic.dk/</nowiki>

Your facebook page url feed should look something like this:

*<nowiki>https://graph.facebook.com/v3.0/schoolname/</nowiki>

This is your feed URL.

=====Create a facebook access token=====
The personal Facebook account that you use to register as a developer does not need to be associated in any way with the page or group whose posts you want to display. You cannot log in to the Developer site using a Facebook Page or Business account. You must use the username and password from your personal Facebook profile. Facebook doesn’t allow businesses to register as developers, only individuals.

Please follow [https://developers.facebook.com/docs/apps/register Facebook guide] to enable yourself as developer on facebook.

When you have a facebook developer account and created an app go to [https://developers.facebook.com/tools/explorer Facebook Graph Explorer]

#Select application
#Select “Get Token” and “Get App Token”
#Copy the Access Token

[[File:App facebookgettoken.png|none|thumb|968x968px]]
Now you have the access token you need to paste into the configurator.
[[File:App rssfeedurl.png|none|thumb|920x920px]]
Reload the service UMS Rss Feed in Services and look in the RSS Feed log to validate.

===Grades===

----

You can set the default view for grades, that filters the grades accordingly. The options are Course, Day and period.

Configurator -> Web Setup -> Edit -> App -> Default grade view
[[File:App gradesview.png|none|thumb|801x801px]]
To specific the period you can set how your terms are set with start and end day for each period.

Configurator -> Modules -> Grades -> Select the Datasource -> Edit -> Terms
[[File:App gradesterms.png|none|thumb|706x706px]]
Depending on which administration system you’re exporting grades from the columns can vary. You can set which grades column should be used and in which order.

Configurator -> Web Setup -> Edit -> App -> Select grade columns
[[File:App gradescolumns.png|none|thumb|709x709px]]
The grades view in the App will change accordingly to which columns chosen, a max of 4 columns will be shown in the App. The columns will be shown for each grade in order from 1 to 4.

If no grade columns settings is made the default columns will be selected in the following order:

*EducationDescription
*CourseDescription
*EvaluationFormDescription
*GradeValue

===Your information===

----

You can select which fields in user information that should be editable.

Configurator -> Web Setup -> Edit -> Userinfo
[[File:App userinfo.png|none|thumb|800x800px]]
You need to set permission before the users are able to upload their own student photo (a selfie).

Configurator -> Web Setup -> Edit -> UMS Photo -> Enable Selfie in App
[[File:App userinfoselfie.png|none|thumb|802x802px]]
This will enable selfie function.

===Student ID And Employee ID===

----<blockquote>''This content has been moved to [[Student / Employee ID]]''</blockquote>

===My Absence===
----The students are able to write an absence reason on an already registered subject. This can be enabled in the template editor.

Select the template -> Absence -> Manage -> Create a new settings or select an existing one -> Add/Edit

Check "Allow students to register absence reason"

[[File:Absence settings.png|none|thumb|570x570px]]

'''Allow students to register absence reason''' will allow the students to set an absence reason when a teacher has set the student as absent. The student can set an absence reason in "My absence".

'''Days back''' is the number of days back the students are allowed to set an absence reason.

'''Show Course''' will show the course view (this will effect both web and app).

'''Show Activity''' will show the activity view (this will effect both web and app).

===Push Notification===
----<blockquote>'''''Temporarily disabled'''''</blockquote>UMS can send push notifications when there are news, grades, or changes in your timetable. It is possible to receive a daily notification with your timetable for the day.

In addition the app can receive [[SMS Alert]] messages.

To set up push notifications go to Web Setup -> App -> Manage -> Add
[[File:AppPushNotificationSettings.png|none|thumb|526x526px]]

Set the description

FCM Server Api Key:

#Receive the key string from inLogic and paste it

Windows Phone:

#Receive the Package SID and Client secret from inLogic and paste the strings

====School account====
In case the school has it's own account do the following to retrieve the information

FCM Server Api Key:

#Open https://play.google.com/apps/publish
#Google Play Console -> Settings -> API Access -> Create linked project and open it -> Credentials
#Create API Key
#Select the API Key and make key restriction for Android
#Type in your package name and SHA-1 certificate fingerprint
#Copy the API key and paste it inside FCM Server API Key

Windows Phone:

#Open https://developer.microsoft.com/en-us/dashboard/apps/overview
#Select your app
#Services -> Push notification -> WNS/MPNS
#Select "Live Services site"
#Copy and paste the Package SID into the configurator
#Generate an Application Secret if none exist
#Copy and paste the Application Secret into the configurator (This is the Client Secret)

===Links===
----[[UMS Links]] can be used by both UMS Web and UMS App. Check the [[UMS Links|guide]].

===Homework===
----See [[UMS Homework]]

===Parking===
----See [[Parking]]

===Notify absence===
----See [[Attendance Registration#SMS and App settings for notify absence|App settings for notify absence in attendance registration]]

===Sms Alert===
----See [[SMS Alert]]

===Privacy Policy===
----To add your own privary policy in the app go to Web Setup -> App

Insert into "Privacy Policy Url:"

If left empty it will default to inLogic's privacy policy "https://www.inlogic.dk/om-inlogic/privacy-policy/"
[[File:App privacypolicyurl.png|none|thumb|792x792px]]

To add it to the App Store login

#https://appstoreconnect.apple.com/
#My Apps
#Select the app
#Select the top menu App Store
#Select App Information in the left menu
#Add your privacy policy url to "Privacy Policy URL"

[[File:App appstore privacypolicy.png|none|thumb|955x955px]] 
===Force language setting===
----Should you wish to, you have the option to force the language of the app to use a specific language, rather than the phones default language.

This is changed via the 'Forced language' feature in the Configurator.
[[File:Forced language.png|none|frame]]
The list of languages will expand over time, as UMS adds support for new languages.
 

==FAQ==

===Untrusted Certificate Error on Android===
'''''We do not recommend using Comodo certificates since they have been known to cause these issues.'''''

Can't login on some Android devices? This could be due to an untrusted Comodo SSL Certificate. We were able to reproduced it on Android version 4.1, 4.4.2, 5.0.1 and 8.1.0, but it may be present on any number of versions.

You can test your SSL certificate on https://sslanalyzer.comodoca.com/

Do the following on the server

#Delete the Comodo RSA Certification Authority issued by Comodo RSA Certification Authority with an expiration date of January 18, 2038.
#Enable automatic root certificate updates on the server

Please checkout the Comodo support site: https://support.comodo.com/index.php?/Knowledgebase/Article/View/1019/38/untrusted-certificate-error-on-android

For future conservation:<blockquote>Certificate is not installed correctly; the certificate needs to be chained back to the Addtrust root certificate in order to be trusted on the Android.</blockquote><blockquote>The issue is that the Windows server is not presenting the complete certificate chain; clients which do not have the complete certificate chain will result in this error as encountered on the Android phone. In order to resolve this, on the server which this certificate is installed on, please open the MMC (Microsoft Management Console), and add the certificate snap-in for the computer account on the local computer.</blockquote><blockquote>In the Intermediate Certification Authorities folder, verify if the Comodo RSA Domain Validation Secure Server CA and Comodo RSA Certification Authority(issued to Comodo RSA Certification Authority, issued by AddTrustExternal CA Root) are installed in this certificate store.</blockquote><blockquote>In the Trusted Root Certification Authorities folder verify if the AddTrustExternal CA Root is installed. Also, if you see the Comodo RSA Certification Authority (issued to and issued by Comodo RSA Certification Authority with an expiration date of January 18, 2038) is present, if it is please delete this certificate.</blockquote><blockquote>If any of these certificates are missing the intermediate and root certificates were provided to you in the .zip file when the certificate was issued, or are available via this support article - <nowiki>https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/979/108/domain-validation-sha-2</nowiki> .</blockquote><blockquote>If you had to delete the Comodo RSA Certification Authority from the Trusted Root Authorities folder, you will also need to disable automatic root certificate updates on the server - https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/769/17/turn-off-automatic-root-certificates-updates-server-2008</blockquote><blockquote>If you have performed these steps and the certificate chain has not updated on the server, to force IIS to update the certificate chain you will need to either change the certificate binding in IIS to another certificate, and then switch the certificate bindings to the correct certificate. Alternately, you will need to restart the server.</blockquote>Conservation for https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/769/17/turn-off-automatic-root-certificates-updates-server-2008<blockquote>To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.</blockquote><blockquote>To turn off Automatic Root Certificates Update:</blockquote><blockquote>1. Click Start, and then click Run.</blockquote><blockquote>2. Type gpedit.msc, and then click OK.</blockquote><blockquote>3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.</blockquote><blockquote>4. Double-click Administrative Templates, double-click System, double-click Internet Communication Management, and then click Internet Communication settings.</blockquote><blockquote>5. Double-click Turn off Automatic Root Certificates Update, click Enabled, and then click OK.</blockquote><blockquote>6. Close the Local Group Policy Editor.</blockquote><blockquote>Note: You can use Group Policy to set policy settings that apply across a given site, domain, or organizational unit in Active Directory Domain Services.</blockquote>

===Issues with the app===
If you're facing issues with the app, please perform the following steps before contacting support:

*Check the AppStore/GooglePlay for app updates and install any present
*Shut down the app completely, and start it back up
*Restart the phone
*Uninstall the app, and redownload it from AppStore/GooglePlay

GetTimetable/TimeEdit

2019-01-29T06:55:20Z

Phk: /* Server connection */

==Requiements==

===UMS Modules===
[[SLI]]

[[TimeEdit]]

This feature only works if UMS has uploaded the data.

==Setting==
[[File:GetTimetable TimeEdit.jpg|none|thumb|783x783px]]

===[[GetTimetable/Format and content|Format and content]]===

===Description===
Name of the setting.

===Server connection===
All connection information is provided by TimeEdit support. (Please contact them for this information.)

All information is specific to a customer.

====URL (Endpoint)====
This URL specifies the endpoint that UMS connects to.

====Certificate path====
Then XML file you receive from TimeEdit.

====Username====
Username to access the Webservice URL.

====Password====
Password to access the Webservice URL.

This must match the one under the data source for templates.
===[[GetStudents/Export Settings|Export settings]]===

==Extra TimeEdit fields==

===comment===
This will be copied to UMS as a comment field on the timetable blocks.

==='''AbsenceRegistration'''===
UMS supports Absence information from TimeEdit.

This is achieved by creating a True/False column on the timetable blocks called "'''AbsenceRegistration'''"

When set to True UMS will see the timetable block as [[Attendance Registration]] enabled.

TimeEdit

2019-01-28T13:31:00Z

Phk: /* Static text before database field */

==Settings==
 [[File:TimeEdit Settings.jpg|none|thumb|728x728px]]

===Description===
Enter a name for this setting.

===Upload courses===
Upload courses from UMS to TimeEdit. This is courses as defined by UMS

Activities/groups upload can not be disabled.

===TimeEdit Server connection===
All connection information is provided by TimeEdit support.

All information is specific to a customer.

====URL (Endpoint)====
This URL specifies the endpoint that UMS connects to.

====Certificate path====
Then XML file you receive from TimeEdit.

====Username====
Username to access the Webservice URL.

====Password====
Password to access the Webservice URL.

===Employee mail domain===
This will be appended to the username to complete a mail address that TimeEdit can use.

===Students mail domain===
This will be appended to the username to complete a mail address that TimeEdit can use.

==Exclude students from classes==
Username entered here will prevent them from being member of any activities.

Users will still be uploaded to TimeEdit.[[File:TimeEdit Settings Exclude Students.jpg|none|thumb|447x447px]]

==Metadata configuration==
This lets you define which fields in UMS are sent to corresponding fields in TimeEdit.

This needs to be setup for employees, activities and courses. Students are predefined by UMS.

Some fields are predefined for the metadata settings.

All fields are from the table called '''Students'''.[[File:TimeEdit Settings Metadata.jpg|none|thumb|902x902px]]

===Key name===
The name of the field in TimeEdit.

===Static text before database field===
The text you write in this field will be suffixed to the UMS database field value.

===UMS database field===
The database field in the UMS table Students.

===Static text after database field===
The text you write in this field will be postfixed to the UMS database field value.

===Required===
UMS will not send the record to TimeEdit If this field is empty when it generates the data to send. This will also be logged in to TimeEdit.Log file.

==TimeEdit field information==
'''Predefined fields''' are done by UMS and can not be changed and are needed to enter into Configurator.

'''Required fields''' has to be setup in the Configurator program. They have to be setup with the as described below. The UMS field can be changed but it is not recommended.

===Students===
TimeEdit's extid for this object type is "student.<SLI_ID>". SLI ID is from the internal UMS table called SLI and column ID.
{| class="wikitable"
|+Predefined fields
!UMS
!TimeEdit
!Description
|-
|ForNavne
|person.first_name
|First name
|-
|Efternavn
|person.last_name
|Last name
|-
|StudieNr
|student.init
|
|-
|StudieNr
|student.username
|
|-
|
|general.email
|UMS will fill this field with <Username@Students mail domain>
This can be overwritten by manual configuration.
|}
===Employees===
TimeEdit's extid for this object type is "teacher.<SLI_ID>". SLI ID is from the internal UMS table called SLI and column ID.
{| class="wikitable"
|+Predefined fields
!UMS
!TimeEdit
!Description
|-
|ForNavne
|person.first_name
|First name
|-
|Efternavn
|person.last_name
|Last name
|-
|
|general.email
|UMS will fill this field with <Username@Employee mail domain>
This can be overwritten by manual configuration.
|}
{| class="wikitable"
|+Required fields
!UMS
!TimeEdit
!Description
|-
|
|person.init
|Username for TimeEdit
|}
{| class="wikitable"
|+Best practice fields
!UMS
!TimeEdit
!Description
|-
|MobilePhone
|general.phone
|
|-
|WorkMail
|general.email
|
|}
===Activity===
TimeEdit's extid for this object type is "studentclass.<Aktivitet>"
{| class="wikitable"
|+Predefined fields
!UMS
!TimeEdit
!Description
|-
|Aktivitet
|studentclass.code
|
|-
|Aktivitet
|studentclass.name
|
|}
{| class="wikitable"
|+Required fields
!UMS
!TimeEdit
!Description
|-
|ActivityDescription
|studentclass.longdescript
|Long description
|-
|Kort_Betegnelse
|studentclass.shortname
|Short description
|}

===Courses===
TimeEdit's extid for this object type is "course.<Aktivitet>_<Skolefag>"
{| class="wikitable"
|+Predefined fields
!UMS
!TimeEdit
!Description
|-
|Aktivitet_Skolefag
|course.code
|
|-
|Aktivitet_Skolefag
|course.name
|
|}
{| class="wikitable"
|+Required fields
!UMS
!TimeEdit
!Description
|-
|SkoleFag_Kort_Betegnelse
|course.shortname
|Short description
|-
|SkoleFag_betegnelse
|course.LongDescript
|Long description
|}

Configurator/Destination

2019-01-25T08:55:21Z

Phk:

This controls Active Directory settings for the template.

Control where the users and groups will be created in Active Directory and a security/distribution group for the template.
[[File:Template Destination.jpg|none|thumb|791x791px]]

==OU (Organizational Unit) Settings==

===Destination OU ===
Specify where this templates users will be created in Active Directory.

===OU for users===
Specify a sub folder or choose "'''Put users in destination OU'''"

===OU for security groups===
Specify a sub folder for security groups or choose "'''Put groups in destination OU'''"

You can not specify an Active Directory path. The OU will always be created under the destination OU.

It is not recommended to put groups in the same OU as the users.

===OU for distribution groups===
Specify a sub folder for distribution groups or choose "'''Put groups in destination OU'''"

You can not specify an Active Directory path. The OU will always be created under the destination OU.

It is not recommended to put groups in the same OU as the users.

===Nice to know===
You can put both the security groups and the distribution groups in the same sub folder ('''This is recommended''').

==Group settings==

===Security group for template===
This group will be created in the "'''OU for security groups'''" if it does not exist.

UMS will remove users that does not belong in the group when it runs. It will add users that are missing as well.

====Disregard keepalive====
Enabling this causes UMS to ignore users that are active because they are in the keepalive period. They will not be added to the group.

===Distribution group for template===
The group will only be created if there is an Exchange setting attached to the template. UMS will not use this group/field for anything without an Exchange setting on the template.

This group will be created in the "'''OU for distribution groups'''" if it does not exist.

UMS will remove users that does not belong in the group when it runs. It will add users that are missing as well.

====Disregard keepalive====
Enabling this causes UMS to ignore users that are active because they are in the keepalive period. They will not be added to the group.

===Nice to know===
UMS will create a mail-enabled security group if "Security group for template" and "Distribution group for template" match.

Configurator/Extra groups

2019-01-25T08:07:05Z

Phk: /* Implicit group memberships */

This tells UMS to maintain groups that are not coming from the administrative system.
[[File:Template Extra groups.jpg|none|thumb|791x791px]]

===Implicit group memberships===
inLogic recommends using this feature in UMS.

This will add the security group of the template to the group entered here.This group will not show up on the users '''Member Of''' tab but instead it will show on the security groups '''Member Of''' tab.

This means the user will be a member of both groups since it is member of a group that is a member of another group.

===Explicit group memberships===
This will add the user directly to the group in '''Active Directory''' and this group will then show on the users '''Member Of''' tab.

UMS will not remove users from this group it will only add missing users that is known to UMS. This is normally a manual group which means UMS can not remove users that are in the group and UMS doesn't know.

If you want groups that are explicit and fully maintained automatically then use [[Custom SQL Commands#Add users to groups]]

Configurator/Destination

2019-01-25T08:05:00Z

Phk:

This controls Active Directory settings for the template.

Control where the users and groups will be created in Active Directory and a security/distribution group for the template.
[[File:Template Destination.jpg|none|thumb|791x791px]]

==OU Settings==

===Destination OU===
Specify where this templates users will be created in Active Directory.

===OU for users===
Specify a sub folder or choose "'''Put users in destination OU'''"

===OU for security groups===
Specify a sub folder for security groups or choose "'''Put groups in destination OU'''"

You can not specify an Active Directory path. The OU will always be created under the destination OU.

It is not recommended to put groups in the same OU as the users.

===OU for distribution groups===
Specify a sub folder for distribution groups or choose "'''Put groups in destination OU'''"

You can not specify an Active Directory path. The OU will always be created under the destination OU.

It is not recommended to put groups in the same OU as the users.

===Nice to know===
You can put both the security groups and the distribution groups in the same sub folder ('''This is recommended''').

==Group settings==

===Security group for template===
This group will be created in the "'''OU for security groups'''" if it does not exist.

UMS will remove users that does not belong in the group when it runs. It will add users that are missing as well.

====Disregard keepalive====
Enabling this causes UMS to ignore users that are active because they are in the keepalive period. They will not be added to the group.

===Distribution group for template===
The group will only be created if there is an Exchange setting attached to the template. UMS will not use this group/field for anything without an Exchange setting on the template.

This group will be created in the "'''OU for distribution groups'''" if it does not exist.

UMS will remove users that does not belong in the group when it runs. It will add users that are missing as well.

====Disregard keepalive====
Enabling this causes UMS to ignore users that are active because they are in the keepalive period. They will not be added to the group.

===Nice to know===
UMS will create a mail-enabled security group if "Security group for template" and "Distribution group for template" match.

Configurator/Activities

2019-01-25T07:38:41Z

Phk:

This settings determines if activities coming from the administrative system will be active in UMS.

If there are no settings configured, activites can not be used in UMS product.

UMS will synchronize users in an activity; by removing users that do not belong (anymore) and adding users that should be there.

Synchronization information usually comes from the administrative system and is stored in the UMS Database.

==Template Setting==
[[File:Template Activities.jpg|none|thumb|791x791px]]

===Setting===
The activity setting attached to this template.

===Web search setting===
Enter an Active Directory group here.

If you are a member of this group then you can search the users and groups/activities from this template.

Leaving this blank means that there are no restrictions on who can see users and groups/activities from this template.

===Include all===
UMS will see all activities as active. (Recommended)

====Filter====
UMS will only see activities matching the filter as active.

==Activity setting==
[[File:Template Activities Settings.jpg|none|thumb|546x546px]]

===Description===
Enter a name for this setting.

===Settings===

====Mail enable====
Mail enable groups on this template. Look for Exchange documentation for further info.

(Only works if an Exchange setting is attached to the template)

 

====Only senders inside my Organization====
Everyone can send to this groups mail address if this checkbox is cleared. Look for Exchange documentation for further info.

(Only works if an Exchange setting is attached to the template)

 

====Do not empty groups====
UMS will not remove users from this group (even if they do not belong according to the administrative data).

====Create - day(s) before start====
The group will be seen as active in UMS, X number of days before it starts.

====Keep active - day(s) after end====
The group will still be active after it ends. This only works if UMS still gets the information from the administrative system, so it only works with certain administrative systems.

====Exchange delivery management====
This controls who can send to the group.

It only works if "'''Only senders inside my Organization'''" is checked.

This is only set on the group when it's mail enabled in Active Directory.

(Only works if an Exchange setting is attached to the template)

====Only accept message from group members====
Check this to activate the feature.

====New group====
Enter an Active Directory group that should be mail enabled.

====Selected groups====
Shows all the current group that will be set on new groups.

===Extra groups===
[[File:Template Activities Settings Extra groups.jpg|none|thumb|666x666px]]All users on templates using this activity setting will be added to the UMS group entered here. Just as [[Custom_SQL_Commands#Add_users_to_groups]] would.

It's recommended to use [[Custom SQL Commands]] instead of this feature.

===Add extra AD groups to UMS groups===
[[File:Template Activities Settings Extra AD groups.jpg|none|thumb|466x466px]]
Enter Active Directory groups here.

====Add to activities====
This will add the Active Directory group to all UMS groups coming from the administrative system.

====Add to template groups====
This will add the Active Directory group to [[Configurator/Destination#Security_group_for_template]] of all templates using this setting.

Custom SQL Commands

2019-01-25T07:21:41Z

Phk:

Custom SQL Commands is a feature for executing customized SQL at specific times in various background jobs. The time depends on the job you attach the SQL command to.

This feature is found at: Configurator -> Settings -> Custom SQL Commands
[[File:Custom SQL commands.jpg|none|thumb|556x556px]]

==Program==
The list of UMS programs that supports Custom SQL commands. The list is only filed with programs that you have a license for.

===Show commands after addon file has been run===
Some of the programs have a custom file that it can run instead of the one supplied by UMS.

If you do not have a custom file then ignore this chekbox

===Show commands after <Program name> has run===
This allows you to run custom SQL commands after the specific program has finished running. This could be a program like '''SLI'''.

If this is not checked the custom SQL commands will run before the program starts.

==Jobs==
The following is a list of all programs you can attach Custom SQL commands to. Note that you will only see the programs you have licenses for. (GetStudents requires no license)

==[[GetStudents]]==
Always use the table '''ImportFromDB''' instead of the Students table when doing these SQL commands.
[[File:Custom SQL commands GetStudents.jpg|none|thumb|725x725px]]

====Description====
Enter a name.

====Priority====
This control in which order commands should run. (1 is first)

====SQL command====
Enter the SQL command UMS will run.

You can create a Store Procedure and run that instead use the command "'''Exec''' '''<Stored Procedure Name>'''"

===Add users to groups===
This option allows you to create new groups in UMS. These groups will be handled like any other group coming from the administrative system.
[[File:Custom SQL commands GetStudents Add users to groups.jpg|none|thumb|725x725px]]

====SQL Command====
Only write the part that comes after the SQL Where sentence and not the whole SQL sentence.

====GetStudents====
All fields under this setting are text fields.

The action should always be left with the text '''Add'''.

[[GetTimetable]]

[[Moodle]]

[[Moodle#Cohort|Moodle Cohort]]

[[Canvas]]

[[G Suite#Drive|Google Apps Drive Sync]]

[[G Suite#Site|Google Apps Sites Sync]]

[[Fronter Integration|Fronter]]

[[ELEARNINGFORCE SharePoint LMS|ELEARNINGFORCE]]

[[Export User Info to Admin systems]]

[[Office 365|Office 365 SharePoint Sync]]

[[OneNote Class Notebook]]

[[SLI]]

==FAQ==
If you ever want to use the UNILOGIN column, you'll need to run it after SLI - use the checkbox to change from before to after.

Welcome to UMS Wiki

2019-01-24T09:09:50Z

Phk:

[[File:UMS-Web-og-app-400.png|thumb|340x340px]]
Welcome to UMS Wiki. This wiki contains technical information about UMS. UMS is developed to help the school’s IT-department avoid trivial and hour-long administration tasks. UMS is short for User Management System and it is a system
developed especially for the educational sector. UMS is a standard solution, which makes it easy to update and maintain, however, because UMS is built using optional modules, it can be tailored to your school’s individual needs. That way you get a simple and effective solution containing everything you need – nothing more, nothing less.

Are you seeking general information please visit our [http://www.inlogic.dk/en/ inLogic website www.inlogic.dk]

==What is UMS?==
Watch our [https://www.youtube.com/watch?v=MI2Wh8ic2hk video] and find out more. UMS is developed to help the school’s IT-department avoid trivial and hour-long administration tasks. However, the school’s teachers and students will benefit from it too, via web and app. Want to know how? Find out in the text below.

'''UMS reduces the IT-department’s workload'''

With UMS, manual user creation is a thing of the past. UMS automatically creates and maintains users in Active Directory, Google Apps, Office 365 and learning management systems, based on data from the student administration system. UMS also gives the school’s students and staff access to a self-service portal, where they can reset their own password, thus saving time for the IT-department.

'''UMS gives teachers more time to teach'''

Many teachers find themselves with a multitude of administrative tasks they need do to, in addition to their other tasks. This could ultimately reduce the amount time they have to teach. To avoid that, UMS makes it possible to complete the administrative tasks quickly and easily via the UMS self-service portal, app and SMS modules, thus giving teachers more time to teach.

'''UMS makes it easier to be a student'''

With UMS, it is easy to be a student, because a long list of relevant school information is easily accessible. E.g., students can see their timetable, homework, grades and attendance records via web and SMS. They can even get notifications on their phone, if there are changes to their timetable or other important information. This makes it easy to stay up-to-date and it strengthens the students’ affiliation to the school.

==Possibilities with UMS==
'''Identity management.''' UMS automatically creates, maintains and deletes users in Active Directory, Office 365, Google Apps and many other systems, based on data from the student administration system.

'''Cloud integration.''' UMS easily integrates with Office 365, SharePoint, Google Apps, Sites and Drives. Timetable data automatically synchronizes to Outlook / Google Calendar. We have also developed a learning portal to Office 365 SharePoint.

'''LMS integration.''' UMS automatically creates class and group rooms in Canvas, Fronter, Moodle, SharePoint etc. Additionally, we integrate to a long list of other systems, e.g. library systems, print payment systems and cafeteria systems.

'''Self-service portal.''' UMS gives you a single login portal, where users can register attendance, reset passwords, block internet access, create guest users, send SMS, see attendance records and much more.

'''SMS and communication.''' The best way to reach your students is through their phones. With UMS, the students can automatically receive an SMS when there are changes to their timetable, they can reset their own password, receive their timetable and grades and much more via SMS.

'''App.''' With UMS, your school can get its own smartphone app, designed with the school’s colours and logo. The app gives students access to their timetable, homework, student ID, attendance records, news from the school etc.

==Support==
If you need support, we are here to help you. Contact us on our support phone: '''+45 42408815''' Monday to Friday from 08.30 am to 03.30 pm. Outside of our opening hours you can send us an e-mail at [mailto:support@inlogic.dk support@inlogic.dk]

Get remote support with [http://downloads.inlogic.dk/TeamViewerQS_da-idcbvgwhct.exe TeamViewer]. With TeamViewer you can get remote support to solve issues, while you are watching. All it requires is that you give us access to your computer.

Download [http://downloads.inlogic.dk/Setup.zip UMS]

Download [http://downloads.inlogic.dk/UMSFrontendSetup.zip UMS Academic Web]

Read our [http://www.inlogic.dk/ums-changelog/ changelog] for the lastest changes.

For other useful tools go to [http://www.inlogic.dk/en/support/download-ums/ inLogic's download site]

==Manuals==
[[InLogic SMS Gateway|InLogic SMS Gateway]]

[[Foxbox|Foxbox SMS Modem]]

[[UMS License Install]]

[[UMS update guide|UMS Update Guide]]

===App===
[[App]]

[[App Store Connect|Apple Developer Account]]

[[Attendance Registration]]

[[Custom Terms and Localization]]

[[App Login]]

[[Student / Employee ID]]

[[My Information]]

[[Parking]]

[[SMS Alert App]]

[[UMS Homework]]

[[UMS Links]]

[[Vouchers]]

===Attendance===
[[Absence Registration for Employees]]

[[Attendance Registration]]

[[Attendance Registration Advanced]]

[[Attendance Registration Card System]]

===Backend===
[[AD Attributes]]

[[Configurator]]

[[Exchange Reviewer]]

[[Exchange Timetable Blocks]]

[[File Server Move]]

[[GetStudents]]

[[Password agent]]

[[Password Expiration Alert]]

[[Powersave]]

[[SLI]]

[[STIL UNI Login]]

===Integrations===
[[Axpoint]]

[[BOSS]]

[[Custom SQL Commands]]

[[Reindex]]

[[Casepoint|Casepoint]]

[[DAM]]

[[edCom]]

[[Elbek & Vejrup Fagsystem]]

[[Integra]]

[[Intranote]]

[[Lectio Sync]]

[[Google Apps]]

[[Moodle]]

[[Papercut]]

[[Print Payment and Management]]

[[Pure]]

[[Safeticket]]

[[SLS]]

[[Study Quiz]]

[[TimeEdit]]

[[UCFMD]]

[[UMS Web Service]]

[[SSO/AD FS]]

[[Tabulex]]

===LMS===
[[Canvas]]

[[ELEARNINGFORCE SharePoint LMS]]

[[Fronter Integration]]

[[Itslearning]]

[[Moodle]]

[[Wizdom integration]]

===Office 365===
[[Office 365]]

[[OneNote Class Notebook]]

[[MSGraphPermissions|Microsoft Graph Permissions]]

[[Sharepoint Portal]]

[[Teams]]

[[Microsoft_SDS]]

===Self Service===
[[Exam Handling]]

[[Grades]]

[[IT Rules]]

[[Merge Letters]]

[[Multiple Users]]

[[Password Self Service]]

[[Password Change]]

[[SSO]]

[[UMS Homework]]

[[UMS Links]]

[[UMS Photo]]

[[UMS Web]]

[[Logo on UMS Web ]]

[[UMS Welcome]]

[[User Lock]]

[[Web Timetable]]

[[SLI Change Username]]

===SMS===
[[SMS Alert]]

[[SMS Subscriptions]]

[[SMS Timetable]]

[[SMS Welcome]]

[[SMS Log]]

SLI Change Username

2019-01-24T09:08:23Z

Phk:

In the UMS controlpanel you can find the function "Change SLI username".
 
[[File:Change SLI Username.jpg|none|thumb|368x368px]]

This global admin features lets you change the username of a student or employee without changing their SLI ID.
[[File:Change SLI Username - Popup.jpg|thumb|474x474px|none]]

This is for example useful if a user name is based on the users initials and they have a name change.

SLI Change Username

2019-01-24T09:08:00Z

Phk:

In the UMS controlpanel you can find the function "Change SLI username".
 
[[File:Change SLI Username.jpg|none|thumb|368x368px]]

This global admin features lets you change the username of a student or employee without changing their SLI ID.
[[File:Change SLI Username - Popup.jpg|left|thumb|474x474px]]

This is for example useful if a user name is based on the users initials and they have a name change.

SLI Change Username

2019-01-24T09:07:44Z

Phk:

In the UMS controlpanel you can find the function "Change SLI username".
 
[[File:Change SLI Username.jpg|none|thumb|368x368px]]

This global admin features lets you change the username of a student or employee without changing their SLI ID.
[[File:Change SLI Username - Popup.jpg|left|thumb|474x474px]]

This is for example useful if a user name is based on the users initials and they have a name change.

File:Change SLI Username - Popup.jpg

2019-01-24T09:07:14Z

Phk:

Change SLI Username - Popup

SLI Change Username

2019-01-24T09:03:31Z

Phk:

In the UMS controlpanel you can find the function "Change SLI username".
 
[[File:Change SLI Username.jpg|none|thumb|368x368px]]

File:Change SLI Username.jpg

2019-01-24T09:03:01Z

Phk:

Change SLI Username

SLI Change Username

2019-01-24T09:01:55Z

Phk: Created page with "In the UMS controlpanel you can find the function "Change SLI username"."

In the UMS controlpanel you can find the function "Change SLI username".

STIL UNI Login

2019-01-23T08:35:19Z

Phk:

UNI•Login er et digitalt ID for børn, unge og ansatte på institutioner, som giver adgang til nationale tjenester og en lang række pædagogiske services og online læremidler. UNI•Login kan bruges både til gratis webtjenester og til webtjenester, som institutionerne kan abonnere på. Institutionerne benytter ofte UNI•Login til adgangsstyring på lokalnet, intranet, trådløse net, skytjenester og andre webløsninger, hvor brugerne skal sikres nem adgang. UNI-Login leveres af STIL, Styrelsen for IT og Læring, der tidligere hed Uni-C.

==Prerequisites==

===Supported administrative systems===
Alle

===Module requirements===
[[UMS]]

===Should third party be contacted===
Kræver en adgang til WS17 ved STIL som skal bestilles.

http://www.stil.dk/It-og-administration/Brugere-og-adgangsstyring/Udbyder-UNILogin/UNI-Login-Eksport

==UNI-C Dataprovider==
Sender UNI-Login’s til STIL

Sættes op på den enkelte template under UNI-C noden
[[File:STIL Account setting.jpg|none|thumb|458x458px]]

===Account settings===
Her bestemmes hvor man vil sende brugerne fra den pågældende template hen.

===Institution number===
Det institutions nummer hvor data skal sendes hen.

===Upload UNI Logins to STIL===
Tells UMS that all templates using this setting will be uploaded to STIL. This will create/add users to the institution number.

===Create new UNI login when CPR changes===
When a CPR changes UMS will tell STIL that it has to create a new UNI login.
If this checkbox is not checked, then you must manually change the UNI Login at https://ba.emu.dk at the same time you change it in the administrative system.

===Write back webservice pincode===
Bruges til kommunikation med elevplan hvis fraværs beskeder skal sendes til dem

===Elevplan Institution number===
Det elevplans institutions nummer hvor data skal sendes hen.

===Elevplan keyord===
SMS keyword som UMS reagerer på når det sendes ind til UMS gateway. Når det står først i Sms’en vil den blive sendt videre til elevplan. Man vil modtage en SMS fra elevplan om at den er modtaget hvis ikke man får den indenfor 30 minutter, skal man gensende Sms’en.

===Company mail address for employees===
Det bruges når der laves en upload af data til STIL til unilogin generering (UNILogin Upload). Man kan bestemme den adresse man har ved uddannelses institutionen. Bruges f.eks. til SDBF systemet.

===Company mail address for students===
Det bruges når der laves en upload af data til STIL til unilogin generering (UNILogin Upload). Man kan bestemme den adresse man har ved uddannelses institutionen.

===Mail===
Lister felterne fra students tabellen hvis man lader den stå i <Not Used> vil den automatisk bruge brugernavnet som man har i AD.

===Mail Domain===
Her indtaster man f.eks. inlogic.dk

Hvis ikke man vælger at indtaste noget i feltet mail domain men kun sætter mail feltet vil mail feltet skulle indeholde hele mail adressen.

==UNI-Login Settings==
[[File:Stiluniloginsettings.png|none|thumb|569x569px]]

===Use UNI-Login===
Her sættes der op om denne template skal bruge UNI-Login

===Force update UNI-Login===
Hvis man ændrer UNI-Login skal det så slå igennem i UMS. Dette vil betyde at brugeren bliver nedlagt og en ny oprettet.

For at sende disse data til STIL skal man aktiverer en service i UMS

Dette punkt findes under settings -> services
[[File:Stilservicessetup.png|none|thumb|585x585px]]

Der skal indtastes et servernavn som denne service skal kører på

Når det er indtastet vil servicen hvert 5 minut se efter om der er kommet en ny students tabel og sende nye data til STIL.

Når man har indtastet navnet og gemt skal man starte servicen ”UMS UNILogin Upload” eller genstarte serveren.

==Upload af data==
For at kunne uploade data som sendes til STIL skal man have et Onlinetjeneste-abonnement. Informationer om dette kan findes her.

http://www.stil.dk/It-og-administration/Brugere-og-adgangsstyring/Udbyder-UNILogin/Onlinetjenester

For at bestille skal man sende en mail til [[Mailto:uniloginudbyder@STIL.dk| uniloginudbyder@STIL.dk]] med teksten og bestillingsformularen.

===Bestillingsformular===
Vi vil gerne have en konto som har adgang til WS10 upload og WS17 download af UNI-Logins. inLogic løsning.
Oplysninger
IP:
Institutions numre:
Dette findes under Modules -> UNI-Sync
[[File:STIL UNISync setup.jpg|none|thumb|368x368px]]

===Activate UNI-Sync===
Skal vi sende/hente data fra STIL

===Institution numbers===
Indtast hvilke institutions numre der skal hentes fra

===Data provider settings (Onlinetjeneste-abonnement)===
Indstillinger som skal bruges til WS10 (Sende data) og WS17 (hente data)

http://www.stil.dk/~/media/STIL/Filer/PDF13_14/140521%20UNI%20Login%20Import%20WS10%20v31.pdf

http://www.stil.dk/~/media/STIL/Filer/Publikationer/Tekniske%20vejledninger/UNI-ogin%20Eksport%20WS17%20v1.3.pdf

===Username===
Username need to access webservice.

==='''Password'''===
Password need to access webservice.

===Password synchronization (UNI-Sync abonnement)===
For at kunne password synkroniserer med STIL skal man have et UNI-Sync abonnement. Informationer findes her

http://www.stil.dk/It-og-administration/Brugere-og-adgangsstyring/Institutioner-og-kommuner/UNISync

(Det er kun nødvendigt at sætte kryds ved punkt A3 =” Automatisk via en webservice (kræver kendskab til SOAP)”.)

===Username===
Username need to access webservice.

==='''Password'''===
Password need to access webservice.

==Opsætning på brugeradministrationen==
For at kunne hente fra STIL og sende data til STIL skal man give lov til det. Det sætter man op i <nowiki>https://ba.emu.dk</nowiki>

En vejledning for opsætningen af WS17 kan findes her.

<nowiki>http://www.stil.dk/~/media/STIL/Filer/PDF15/150714%2017ws%20afsend%20og%20godkend%20Dataforspoergsel%20til%20skoler.pdf</nowiki>

UMS vil hente alle WS10

===Pakke===
Man skal som minimum have adgang til en fuld eller mellem pakke. Specifikationerne for de enkelte pakker kan ses nedenunder.

Dataaftale for UNI-Login Eksport

(UNI-Login webservice ws17)

Udbydere med ws17 dataadgang kan trække nedenstående information afhængigt af den valgte pakke.
{| class="wikitable"
| colspan="8" | - Den fulde pakke: Alle data i skemaet - markeret F

- Mellem pakken: Data i skemaet, som er markeret M

- Den lille pakke: Data i skemaet, som er markeret L

Data om ansatte, elever, værger og andre kontaktpersoner
|-
| colspan="3" | - CPR-nummer
| colspan="2" |F
| colspan="2" |M
|
|-
| colspan="3" | - Fornavn(e)
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Efternavn
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Privatadresse (Se adresseinformation)
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Hjemmetelefon (Se telefonnummer-information)
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Arbejdstelefon (Se telefonnummer-information)
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Mobiltelefon (Se telefonnummer-information)
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - E-mail
| colspan="2" |F
| colspan="2" |M
|
|-
| colspan="3" | - Fødselsdag
| colspan="2" |F
| colspan="2" |M
|
|-
| colspan="3" | - Køn
| colspan="2" |F
| colspan="2" |M
|
|-
| colspan="3" | - PhotoId
| colspan="2" |F
| colspan="2" |M
|
|-
| colspan="3" |
| colspan="2" |
| colspan="2" |
|
|-
| colspan="3" |Adresseinformation:
| colspan="2" |
| colspan="2" |
|
|-
| colspan="3" | - Om adressen er beskyttet
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Adressens vejnavn, nr. og etage
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Postnummer
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - By
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Landekode
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Land
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Kommunekode
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Kommunenavn
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" |
| colspan="2" |
| colspan="2" |
|
|-
| colspan="3" |Telefonnummer-information:
| colspan="2" |
| colspan="2" |
|
|-
| colspan="3" | - Om telefonnummeret er beskyttet
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Telefonnummer
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" |
| colspan="2" |
| colspan="2" |
|
|-
| colspan="3" |Supplerende data om elever
| colspan="2" |
| colspan="2" |
|
|-
| colspan="3" | - Studietype (elev eller stud)
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Studienummer
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Elevens niveau (for grundskoleelever)
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Elevens hovedgruppe (klasse)
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Yderligere grupper elever er tilknyttet
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - Kontaktlærer
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Kontaktperson(er)s relation (mor, far osv.)
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Om kontaktperson(er) har forældremyndighed
| colspan="2" |F
| colspan="2" |
|
|-
| colspan="3" | - Afdeling, bygning eller værelsesnummer på efterskoler
| colspan="2" |F
| colspan="2" |M
|L
|-
| colspan="3" | - ID i det lokale studieadministrative system
| colspan="2" |F
| colspan="2" |M
|L
|}
{| class="wikitable"
|Supplerende data om ansatte
|
|
|
|-
|<nowiki>- Ansættelsestype (lærer, tap, pæd eller gæst)</nowiki>
|F
|M
|L
|-
|<nowiki>- Initialer</nowiki>
|F
|M
|L
|-
|<nowiki>- Stilling</nowiki>
|F
|M
|L
|-
|<nowiki>- Afdeling, bygning eller værelsesnummer på efterskoler</nowiki>
|F
|M
|L
|-
|<nowiki>- Grupper medarbejderen er tilknyttet</nowiki>
|F
|M
|L
|-
|<nowiki>- ID i det lokale studieadministrative system</nowiki>
|F
|M
|
|-
|
|
|
|
|-
|Data om UNI-Login for ansatte og elever
|
|
|
|-
|<nowiki>- UNI-Login brugernavn (brugerID)</nowiki>
|F
|M
|L
|-
|<nowiki>- Initialpassword</nowiki>
|F
|M
|
|-
|<nowiki>- Om inititalpassword er gældende password</nowiki>
|F
|M
|
|-
|<nowiki>- Brugerens navn i UNI-Login</nowiki>
|F
|M
|
|-
|<nowiki>- SkoleKom-navn</nowiki>
|F
|M
|
|-
|<nowiki>- Brugerens selvvalgte email-adresse i UNI-Login</nowiki>
|F
|M
|
|-
|<nowiki>- Brugerens selvvalgte mobilnummer i UNI-Login</nowiki>
|F
|M
|
|-
|
|
|
|
|-
|Data om grupper på institutionen
|
|
|
|-
|<nowiki>- Gruppeid</nowiki>
|F
|M
|L
|-
|<nowiki>- Gruppenavn</nowiki>
|F
|M
|L
|-
|<nowiki>- Gruppetype</nowiki>
|F
|M
|L
|-
|<nowiki>- Niveau</nowiki>
|F
|M
|L
|-
|<nowiki>- Spor</nowiki>
|F
|M
|L
|-
|<nowiki>- Startdato</nowiki>
|F
|M
|L
|-
|<nowiki>- Slutdato</nowiki>
|F
|M
|L
|}

===Technical settings===

====17ws - forspørgsel til skoler====
Log ind på ba.emu.dk – tryk dataaftaler>tryk på webservice forespørgsler
[[File:Stil1.png|none|thumb|642x642px]]
[[File:Stil2.png|none|thumb|642x642px]]

Indtast en skoles institutionsnummer> tryk vis > Tryk opret
[[File:Stil3.png|none|thumb|642x642px]]
Set fra skolens side > klik på dataaftaler > godkend, dvs. tryk gem
[[File:Stil4.png|none|thumb|642x642px]]

==FAQ==

===Hvordan checker jeg om min IP er åbnet hos STIL?===
Man kan teste adgangen via denne url:

<nowiki>https://ws04.infotjeneste.uni-c.dk/infotjenesteunilogin-ws/ws?WSDL</nowiki>

Den skulle gerne returnere et xml. Dokument – hvis i får en Access denied, så er der ikke åbnet for jeres IP.

===Hvilke CPR numre sendes til STIL (Gammel ordning)===
Alle rigtige CPR numre

Alle Fiktive CPR numre begyndende med 6,7,8 eller 9 og som overholder modulus 11

===Hvilke CPR numre bliver ikke sendt til STIL (Gammel ordning)===
Alle CPR numre som ikke overholder modulus 11

Alle CPR numre som indeholder bogstaver

===Hvilke CPR numre sendes til STIL (Ny ordning)===
Numerisk værdi der overholder modulus 11

Hvis cpr numre indeholder bogstaver opretter UMS Uni-login på baggrund af SLI id.

===Hvis man skifter CPR nummer beholder man så sit UNI Login===
Ja

===Må der kører andre importer end den fra inLogic===
Nej, det vil ødelægge automatikken med at beholde sit unilogin hvis man skifter CPR.

===Kan man få generet UNI-Login’s med det samme===
Ikke helt, men næsten.

Det kræver 2 kørsler af GetStudents med en upload af data imellem (UNILogin Upload servicen skal have kørt). Inden man kører anden kørsel af GetStudents skal STIL have haft nok tid til at lægge data fra deres back end miljø ud til de webservice’s hvor man henter data. En tommel finger regel kunne være 20-30 minutter.

===Hvordan nulstiller jeg common secret (udregnes ved første synkronisering)===
Åbner den tabel der hedder PasswordSyncGeneralSettings og sletter indholdet af kollonen UniCCommonSecret

===Skal Easy-C jobs slåes fra (C001 og C002)===
Ja de må ikke køre sammen med vores

===Skal LUDUS jobs slåes fra===
Ja kun upload man kan stadig download til ludus

===Error fra stil på uni-sync/password sync===
11/5/2018 11:05:01 AM - (ChangeUNI_CPassword) Change password for user - XXX0016 Error = 'ClientIP=87.54.38.xxx', 'AdpCommkeyStatus=2', 'checkCryptParam: md5sumNotEqual', 'BadAuth', 'ul-front-db-prod1', 'ul-wls-db-prod6', '2 ms'

Error rettes ved at nulstille UniCCommonSecret i SQL database. (update PasswordSyncGeneralSettingsset UniCCommonSecret = <nowiki>''</nowiki>)

Efter nulstilling af UniCCommonSecret, skal passwordsync jobbet køre igen.

===InstitutionPerson ikke indlæst! Ikke forventet CPR til localPersonID - skal omidentificeres: LocalPersonId====
Read this [[STIL UNI Login#Create new UNI login when CPR changes]]

Parking

2018-05-25T07:53:33Z

Phk:

The Parking function makes it easy to avoid parking tickets at schools, which administer their parking spaces with the parking company. Through the app, students and employees can get a valid, digital parking permit simply by entering their vehicle’s registration number in the app or in UMS Web. When the registration number has been entered, it becomes visible to the parking company, who then knows that the user is allowed to park at the school. Available integration includes Parkzone, Apcoa and City Parkering.

== Prerequisites ==

=== Supported administrative systems ===
* Parkzone
* Apcoa
* City Parkering

=== Module requirements ===
Parking

=== Should third party be contacted ===
You'll need a client key (and possibly a password) from the parking company before UMS can communicate with their services.

== Installation ==
It is necessary to have a running UMS installation.

== Configuration settings ==
There are two ways of settings up parking: New Parking and Legacy Parking. In the future legacy will be moved to the new system. Currently new Parking settings are used for City Parkering and legacy parking settings are used for ParkZone and Apcoa.

=== New Parking Settings ===
In the configurator go to:

Modules -> Parking
[[File:ParkingSettingsConfigurator.png|thumb|Parking settings in the configurator|none]]

There are 3 main parts of the parking system that needs to be set up:

'''Parking servers'''
[[File:Parking Servers Settings.png|thumb|The list of parking servers.|none]]
It is possible to set up multiple parking server systems.

You can add, edit or remove a system.
[[File:Parking server settings.png|thumb|Parking server settings|none]]
First you choose your parking system (currently only City Parkering is available, but more will be added in future releases).

The description is used as a name or reference in the configurator, but is not visible to users.

You should have been provided a company key and a password by your parking provider, enter them in these parking server settings.

'''Parking places'''
[[File:Parking Places.png|thumb|Parking Places|none]]
You can have multiple parking places, and you can edit, add or delete them.
[[File:Parking place seetting edit.png|thumb|Each parking place is connected to a parking system. |none]]
This parking place description is shown to the user if they have access to multiple parking systems to choose from, so make sure that this is a good identifier.

When "Delete users" is enabled, users that are removed in UMS will also be deleted from the parking system.

When "Cleanup" is enabled, users that exists in the parking system but not UMS will also be deleted.

Mail Domain is used only when a parking is created for a user that does not have a private email address entered. If there is a private email address it will be used, otherwise the username concatenated with the Mail Domain will be send.

'''Parking settings'''
[[File:Parking Settings.png|thumb|You can have multiple parking settings.|none]]
[[File:Parking setting setup.png|thumb|A parking setting is a collection of allowed and not allowed parking places.|none]]
You can set up a parking setting per template, so that one set of users have access to some parking places but not others.

If you only have one parking place, and everyone has access to it, you can just create one parking setting.

You can connect a parking setting to a template:
# Go to edit your template.
# Find the parking menu, and select the parking setting you want for you template.
# [[File:Parking template.png|thumb|A parking setting is connected to a template.|none]]

=== Legacy Parking Settings ===

==== 1. ParkZone setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> Parkzone -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Test Plads'
* 'Client Key settings' - Insert the provided client key from ParkZone. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group' - Insert the provided parking location ID from ParkZone
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
[[File:Parking permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for ParkZone.]]
The picture below illustrates the settings when managing the client key.
[[File:Parkzone clientkeysettings.png|none|thumb|439x439px|Manage client key settings for ParkZone.]]

==== 2. APCOA setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> APCOA -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Setup'
* 'Client key settings' - Insert the provided client key from APCOA. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group ID' - Insert the provided parking location ID from APCOA
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
* 'Mail Domain' - User suffix
[[File:Apcoa permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for APCOA.]]

The picture below illustrates the settings when managing the client key.
[[File:Apcoa clientkeysettings.png|none|thumb|332x332px|Manage client key settings for APCOA.]]

== App ==

=== Parking spaces ===
This view is a list of all parking spaces the school has available (based on your template).

If you only have 1 present, this will automatically be selected, and this step will be skipped.
[[File:Parking Spaces App.png|center|thumb|First choose your Parking Space.]]

=== Parking registrations ===
When you have selected a parking space, you will see a list of your registered license plates, along with a timestamp of when this was registered.

Here you can edit and delete existing registrations, as well as create more, up to the allowed number of registrations the school has specified.
[[File:Parking registrations.png|center|thumb]]
[[File:You can add a license plate.png|center|thumb|You can add a license plate by clicking on the "plus sign" in the top right.]]

=== General info ===
The app does not (visually) act differently whether the school is running APCOA, Parkzone or CityParking.

== Web interface ==
To register a license plate with a parking system go to “Your info”.
[[File:Your info.png|center|thumb|Go to your info]]
If a parking system has been installed and you have access to it, you should see a parking menu.
[[File:Empty parking list.png|center|thumb|You can see your parking permits.]]
You can then create a new parking, by clicking on the "create new".
[[File:Enter License.png|center|thumb|Enter your registration number and choose a parking spot.]]
Enter your licenseplate number and select which parking location you want to use. If you only have access to one parking place, you don’t have to choose one.

Once you click ok, the parking should be registered with the parking system and you should be good to go.

You can always edit or delete your parking.
[[File:A created registration.png|center|thumb|A created registration]]

== FAQ ==

Parking

2018-05-25T07:06:40Z

Phk: Added web interface description.

The Parking function makes it easy to avoid parking tickets at schools, which administer their parking spaces with the parking company. Through the app, students and employees can get a valid, digital parking permit simply by entering their vehicle’s registration number in the app or in UMS Web. When the registration number has been entered, it becomes visible to the parking company, who then knows that the user is allowed to park at the school. Available integration includes Parkzone, Apcoa and City Parkering.

== Prerequisites ==

=== Supported administrative systems ===
* Parkzone
* Apcoa
* City Parkering

=== Module requirements ===
Parking

=== Should third party be contacted ===
You'll need a client key (and possibly a password) from the parking company before UMS can communicate with their services.

== Installation ==
It is necessary to have a running UMS installation.

== Configuration settings ==
There are two ways of settings up parking: New Parking and Legacy Parking. In the future legacy will be moved to the new system. Currently new Parking settings are used for City Parkering and legacy parking settings are used for ParkZone and Apcoa.

=== New Parking Settings ===
In the configurator go to:

Modules -> Parking
[[File:ParkingSettingsConfigurator.png|center|thumb|Parking settings in the configurator]]

There are 3 main parts of the parking system that needs to be set up:

'''Parking servers'''
[[File:Parking Servers Settings.png|center|thumb|The list of parking servers.]]
It is possible to set up multiple parking server systems.

You can add, edit or remove a system.
[[File:Parking server settings.png|center|thumb|Parking server settings]]
First you choose your parking system (currently only City Parkering is available, but more will be added in future releases).

The description is used as a name or reference in the configurator, but is not visible to users.

You should have been provided a company key and a password by your parking provider, enter them in these parking server settings.

'''Parking places'''
[[File:Parking Places.png|center|thumb|Parking Places]]
You can have multiple parking places, and you can edit, add or delete them.
[[File:Parking place seetting edit.png|center|thumb|Each parking place is connected to a parking system. ]]
This parking place description is shown to the user if they have access to multiple parking systems to choose from, so make sure that this is a good identifier.

When "Delete users" is enabled, users that are removed in UMS will also be deleted from the parking system.

When "Cleanup" is enabled, users that exists in the parking system but not UMS will also be deleted.

Mail Domain is used only when a parking is created for a user that does not have a private email address entered. If there is a private email address it will be used, otherwise the username concatenated with the Mail Domain will be send.

'''Parking settings'''
[[File:Parking Settings.png|center|thumb|You can have multiple parking settings.]]
[[File:Parking setting setup.png|center|thumb|A parking setting is a collection of allowed and not allowed parking places.]]
You can set up a parking setting per template, so that one set of users have access to some parking places but not others.

If you only have one parking place, and everyone has access to it, you can just create one parking setting.

You can connect a parking setting to a template:
# Go to edit your template.
# Find the parking menu, and select the parking setting you want for you template.
# [[File:Parking template.png|center|thumb|A parking setting is connected to a template.]]

=== Legacy Parking Settings ===

==== 1. ParkZone setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> Parkzone -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Test Plads'
* 'Client Key settings' - Insert the provided client key from ParkZone. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group' - Insert the provided parking location ID from ParkZone
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
[[File:Parking permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for ParkZone.]]
The picture below illustrates the settings when managing the client key.
[[File:Parkzone clientkeysettings.png|none|thumb|439x439px|Manage client key settings for ParkZone.]]

==== 2. APCOA setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> APCOA -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Setup'
* 'Client key settings' - Insert the provided client key from APCOA. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group ID' - Insert the provided parking location ID from APCOA
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
* 'Mail Domain' - User suffix
[[File:Apcoa permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for APCOA.]]

The picture below illustrates the settings when managing the client key.
[[File:Apcoa clientkeysettings.png|none|thumb|332x332px|Manage client key settings for APCOA.]]

== App ==

=== Parking spaces ===
This view is a list of all parking spaces the school has available (based on your template).

If you only have 1 present, this will automatically be selected, and this step will be skipped.
[[File:Parking Spaces App.png|center|thumb|First choose your Parking Space.]]

=== Parking registrations ===
When you have selected a parking space, you will see a list of your registered license plates, along with a timestamp of when this was registered.

Here you can edit and delete existing registrations, as well as create more, up to the allowed number of registrations the school has specified.
[[File:Parking registrations.png|center|thumb]]
[[File:You can add a license plate.png|center|thumb|You can add a license plate by clicking on the "plus sign" in the top right.]]

=== General info ===
The app does not (visually) act differently whether the school is running APCOA, Parkzone or CityParking.

== Web interface ==
To register a license plate with a parking system go to “Your info”.
[[File:Your info.png|center|thumb|Go to your info]]
If a parking system has been installed and you have access to it, you should see a parking menu.
[[File:Empty parking list.png|center|thumb|You can see your parking permits.]]
You can then create a new parking, by clicking on the "create new".
[[File:Enter License.png|center|thumb|Enter your registration number and choose a parking spot.]]
Enter your licenseplate number and select which parking location you want to use. If you only have access to one parking place, you don’t have to choose one.

Once you click ok, the parking should be registered with the parking system and you should be good to go.

You can always edit or delete your parking.
[[File:A created registration.png|center|thumb|A created registration]]

== FAQ ==

File:A created registration.png

2018-05-25T07:06:24Z

Phk:

A created registration

File:Enter License.png

2018-05-25T07:05:37Z

Phk:

Enter License

File:Empty parking list.png

2018-05-25T07:04:20Z

Phk:

Empty parking list

File:Your info.png

2018-05-25T07:03:37Z

Phk:

Your info

Parking

2018-05-25T07:01:09Z

Phk: Added app parking

The Parking function makes it easy to avoid parking tickets at schools, which administer their parking spaces with the parking company. Through the app, students and employees can get a valid, digital parking permit simply by entering their vehicle’s registration number in the app or in UMS Web. When the registration number has been entered, it becomes visible to the parking company, who then knows that the user is allowed to park at the school. Available integration includes Parkzone, Apcoa and City Parkering.

== Prerequisites ==

=== Supported administrative systems ===
* Parkzone
* Apcoa
* City Parkering

=== Module requirements ===
Parking

=== Should third party be contacted ===
You'll need a client key (and possibly a password) from the parking company before UMS can communicate with their services.

== Installation ==
It is necessary to have a running UMS installation.

== Configuration settings ==
There are two ways of settings up parking: New Parking and Legacy Parking. In the future legacy will be moved to the new system. Currently new Parking settings are used for City Parkering and legacy parking settings are used for ParkZone and Apcoa.

=== New Parking Settings ===
In the configurator go to:

Modules -> Parking
[[File:ParkingSettingsConfigurator.png|center|thumb|Parking settings in the configurator]]

There are 3 main parts of the parking system that needs to be set up:

'''Parking servers'''
[[File:Parking Servers Settings.png|center|thumb|The list of parking servers.]]
It is possible to set up multiple parking server systems.

You can add, edit or remove a system.
[[File:Parking server settings.png|center|thumb|Parking server settings]]
First you choose your parking system (currently only City Parkering is available, but more will be added in future releases).

The description is used as a name or reference in the configurator, but is not visible to users.

You should have been provided a company key and a password by your parking provider, enter them in these parking server settings.

'''Parking places'''
[[File:Parking Places.png|center|thumb|Parking Places]]
You can have multiple parking places, and you can edit, add or delete them.
[[File:Parking place seetting edit.png|center|thumb|Each parking place is connected to a parking system. ]]
This parking place description is shown to the user if they have access to multiple parking systems to choose from, so make sure that this is a good identifier.

When "Delete users" is enabled, users that are removed in UMS will also be deleted from the parking system.

When "Cleanup" is enabled, users that exists in the parking system but not UMS will also be deleted.

Mail Domain is used only when a parking is created for a user that does not have a private email address entered. If there is a private email address it will be used, otherwise the username concatenated with the Mail Domain will be send.

'''Parking settings'''
[[File:Parking Settings.png|center|thumb|You can have multiple parking settings.]]
[[File:Parking setting setup.png|center|thumb|A parking setting is a collection of allowed and not allowed parking places.]]
You can set up a parking setting per template, so that one set of users have access to some parking places but not others.

If you only have one parking place, and everyone has access to it, you can just create one parking setting.

You can connect a parking setting to a template:
# Go to edit your template.
# Find the parking menu, and select the parking setting you want for you template.
# [[File:Parking template.png|center|thumb|A parking setting is connected to a template.]]

=== Legacy Parking Settings ===

==== 1. ParkZone setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> Parkzone -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Test Plads'
* 'Client Key settings' - Insert the provided client key from ParkZone. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group' - Insert the provided parking location ID from ParkZone
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
[[File:Parking permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for ParkZone.]]
The picture below illustrates the settings when managing the client key.
[[File:Parkzone clientkeysettings.png|none|thumb|439x439px|Manage client key settings for ParkZone.]]

==== 2. APCOA setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> APCOA -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Setup'
* 'Client key settings' - Insert the provided client key from APCOA. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group ID' - Insert the provided parking location ID from APCOA
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
* 'Mail Domain' - User suffix
[[File:Apcoa permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for APCOA.]]

The picture below illustrates the settings when managing the client key.
[[File:Apcoa clientkeysettings.png|none|thumb|332x332px|Manage client key settings for APCOA.]]

== App ==

=== Parking spaces ===
This view is a list of all parking spaces the school has available (based on your template).

If you only have 1 present, this will automatically be selected, and this step will be skipped.
[[File:Parking Spaces App.png|center|thumb|First choose your Parking Space.]]

=== Parking registrations ===
When you have selected a parking space, you will see a list of your registered license plates, along with a timestamp of when this was registered.

Here you can edit and delete existing registrations, as well as create more, up to the allowed number of registrations the school has specified.
[[File:Parking registrations.png|center|thumb]]
[[File:You can add a license plate.png|center|thumb|You can add a license plate by clicking on the "plus sign" in the top right.]]

== FAQ ==

File:You can add a license plate.png

2018-05-25T07:00:31Z

Phk:

You can add a license plate

File:Parking registrations.png

2018-05-25T06:58:53Z

Phk:

Parking registrations

File:Parking Spaces App.png

2018-05-25T06:57:41Z

Phk:

Parking Spaces App

Parking

2018-05-25T06:28:04Z

Phk: Updated parking with the new settings.

The Parking function makes it easy to avoid parking tickets at schools, which administer their parking spaces with the parking company. Through the app, students and employees can get a valid, digital parking permit simply by entering their vehicle’s registration number in the app or in UMS Web. When the registration number has been entered, it becomes visible to the parking company, who then knows that the user is allowed to park at the school. Available integration includes Parkzone, Apcoa and City Parkering.

== Prerequisites ==

=== Supported administrative systems ===
* Parkzone
* Apcoa
* City Parkering

=== Module requirements ===
Parking

=== Should third party be contacted ===
You'll need a client key (and possibly a password) from the parking company before UMS can communicate with their services.

== Installation ==
It is necessary to have a running UMS installation.

== Configuration settings ==
There are two ways of settings up parking: New Parking and Legacy Parking. In the future legacy will be moved to the new system. Currently new Parking settings are used for City Parkering and legacy parking settings are used for ParkZone and Apcoa.

=== New Parking Settings ===
In the configurator go to:

Modules -> Parking
[[File:ParkingSettingsConfigurator.png|center|thumb|Parking settings in the configurator]]

There are 3 main parts of the parking system that needs to be set up:

'''Parking servers'''
[[File:Parking Servers Settings.png|center|thumb|The list of parking servers.]]
It is possible to set up multiple parking server systems.

You can add, edit or remove a system.
[[File:Parking server settings.png|center|thumb|Parking server settings]]
First you choose your parking system (currently only City Parkering is available, but more will be added in future releases).

The description is used as a name or reference in the configurator, but is not visible to users.

You should have been provided a company key and a password by your parking provider, enter them in these parking server settings.

'''Parking places'''
[[File:Parking Places.png|center|thumb|Parking Places]]
You can have multiple parking places, and you can edit, add or delete them.
[[File:Parking place seetting edit.png|center|thumb|Each parking place is connected to a parking system. ]]
This parking place description is shown to the user if they have access to multiple parking systems to choose from, so make sure that this is a good identifier.

When "Delete users" is enabled, users that are removed in UMS will also be deleted from the parking system.

When "Cleanup" is enabled, users that exists in the parking system but not UMS will also be deleted.

Mail Domain is used only when a parking is created for a user that does not have a private email address entered. If there is a private email address it will be used, otherwise the username concatenated with the Mail Domain will be send.

'''Parking settings'''
[[File:Parking Settings.png|center|thumb|You can have multiple parking settings.]]
[[File:Parking setting setup.png|center|thumb|A parking setting is a collection of allowed and not allowed parking places.]]
You can set up a parking setting per template, so that one set of users have access to some parking places but not others.

If you only have one parking place, and everyone has access to it, you can just create one parking setting.

You can connect a parking setting to a template:
# Go to edit your template.
# Find the parking menu, and select the parking setting you want for you template.
# [[File:Parking template.png|center|thumb|A parking setting is connected to a template.]]

=== Legacy Parking Settings ===

==== 1. ParkZone setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> Parkzone -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Test Plads'
* 'Client Key settings' - Insert the provided client key from ParkZone. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group' - Insert the provided parking location ID from ParkZone
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
[[File:Parking permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for ParkZone.]]
The picture below illustrates the settings when managing the client key.
[[File:Parkzone clientkeysettings.png|none|thumb|439x439px|Manage client key settings for ParkZone.]]

==== 2. APCOA setup ====
All settings for the Parking module is set in the configurator. Go to Template Editor -> APCOA -> Manage -> Add
* 'Description' - This is the name for your setting, i.e. 'Setup'
* 'Client key settings' - Insert the provided client key from APCOA. To edit the settings for the client key, click 'Manage'. See picture below for illustration.
* 'Permission group ID' - Insert the provided parking location ID from APCOA
* 'Delete users' - Check this box if a user should be disabled when removed from AD. If left unchecked, the user will only be disabled if the end date is set to now
* 'Cleanup' - Check this box if UMS should synchronise if users are active or deleted
* 'Maximum number of license plates' - Set the limit of license plates a user may add
* 'Mail Domain' - User suffix
[[File:Apcoa permissiongroupsettings.png|none|thumb|435x435px|Permission group settings for APCOA.]]

The picture below illustrates the settings when managing the client key.
[[File:Apcoa clientkeysettings.png|none|thumb|332x332px|Manage client key settings for APCOA.]]

== FAQ ==

File:Parking template.png

2018-05-25T06:27:01Z

Phk:

Parking template

File:Parking setting setup.png

2018-05-25T06:25:17Z

Phk:

Parking setting setup

File:Parking Settings.png

2018-05-25T06:24:25Z

Phk:

Parking Settings

File:Parking Places.png

2018-05-25T06:18:20Z

Phk:

Parking Places

File:Parking server settings.png

2018-05-25T06:16:54Z

Phk:

Parking server settings

File:Parking Servers Settings.png

2018-05-25T06:15:16Z

Phk:

Parking Servers Settings in configurator.

File:ParkingSettingsConfigurator.png

2018-05-25T06:13:55Z

Phk:

Parking in configurator