UmsWiki - User contributions [en]

Moodle

2018-02-05T15:48:20Z

Juh: /* Upload employee information */

Our Moodle integration is developed for schools, which want to avoid hour-long administrative tasks. The integration automatically creates, maintains and deletes users, based on data from your student administrative system. It also creates and maintains group rooms, which teachers and students can use for teaching purposes. The rooms automatically use the language you require and can be categorized according to your needs, making them easier to find. Rooms that are no longer in use are deleted automatically.

=== Configuration in UMS ===
The integration makes it possible to upload pictures of the users to Moodle, making it easy for teachers and students to see whom they are interacting with. If these pictures are replaced in UMS, they are automatically updated in Moodle. Last, but not least, the module can integrate with the AD. This allows users to log into Moodle with the same password they use to access the school’s IT-system. The Moodle integration gives you an easy overview and ensures that the users’ data is always managed correctly, without requiring any manual updates. This frees up time for the IT-department, who can focus on other tasks instead.

If you want to make it easy for students and teachers to keep track of their timetables, you can embed our Web Timetable module in Moodle as an iframe. By doing this, users can access homework and notes that are registered on the various timetable blocks in the timetable. Please note: To embed Web Time Table, the Web Timetable and SSO modules are required. In order to see homework, the Homework module is required.

== Prerequisites ==

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

=== What to have ready ===
Moodle

== Installation ==
Open UMS Configurator and go to Modules > Moodle > Organization settings
[[File:Image.png|none|thumb|537x537px]]

Click Add.
[[File:Moodleorganizationsettings.png|none|thumb|535x535px]]

== Organization settings ==
[[File:Moodle organization settings2.png|none|thumb|508x508px]]

'''Description'''

Give your Organization setting a name.

'''DatabaseServer'''

Name of database server hosting the Moodle database.

'''DatabaseName'''

Name of Moodle database.

'''Database TablesPrefix'''

Table prefix set when installing Moodle.

'''UserName'''

UserName of the user that can access the database.

'''Password'''

Password of the user that can access the database.

'''URL'''

URL for your Moodle installation ex. <nowiki>http://moodle.inlogic.dk</nowiki>

'''Webservice Token'''

Token created in Moodle siteadministration. [https://docs.moodle.org/24/en/Using_web_services Guide to create access and token] ( Remember: When adding functions to webservice, add all functions )

'''DataPath'''

Moodle data path ex. \\moodle.inlogic.dk\c$\Moodle\server\moodledata\filedir.

The user running moodle exe must have access to this path.

'''DatabaseType'''

Choose Database type used for Moodle. can only be one in the list below.
* Microsoft SQL
* MySQL
* Oracle SQL

== Moodle Site settings ==
From Configurator, Edit existing template > Moodle > Manage > Add or Configurator > Modules > Moodle > Site Settings > Add
[[File:Moodle Settings.png|none|thumb|824x824px]]
'''Description:'''

Give the Site settings a name.

'''Organization settings'''

Choose the Organization setting you want to use for this site setting.

'''Default country'''

Choose default country. This is used when creating users.

'''Authentication method'''

Login method for the users

'''Mail domain for new students'''

The address appended to their username in moodle to give them an email address

'''Mail domain for new employees'''

The address appended to their username in moodle to give them an email address

=== Upload student information ===
Check these boxes to send and update information on students
* Address
* Phone (Phone1)
* Mobile Phone (Phone 2)
* Mail

=== Picture library ===
Upload pictures of students

See [[Configurator/Picture_libraries|Picture libraries]]

=== Upload employee information ===
Check these boxes to send and update information on employees
* Address
* Phone (Phone1)
* Mobile Phone (Phone 2)
* Mail

=== Picture library ===
Upload pictures of employees

See [[Configurator/Picture_libraries|Picture libraries]]

=== Course ===

[[File:Moodle Course Settings.png|none|thumb|732x732px]]

See [[LMS Settings]] for options not descriped below

'''Language'''

The language set on a site when is it created.

'''Course category'''

The category the is put on the site when it's created

==== Activity sites ====
See [[Site selection settings]]

==== Course sites ====
See [[Site selection settings]]

=== Cohort ===

[[File:Moodle Cohort Settings.png|none|thumb|733x733px]]

See [[LMS Settings]] for options not descriped below
==== Activity sites ====
See [[Site selection settings]]

==== Course sites ====
See [[Site selection settings]]

== Template Settings ==
You need to attach a cohort setting to a template. This will tell UMS that cohorts will be created from this template.
[[File:Moodle Template Cohort Settings.png|none|thumb|675x675px]]

'''Description'''

Enter a description for this setting

'''Cohort category'''

Enter a category that will be attached to the cohorts when they are created

'''SQL Groups'''

See [[LMS Settings]] for this option

== FAQ ==

Moodle

2018-02-05T15:41:37Z

Juh: header

Our Moodle integration is developed for schools, which want to avoid hour-long administrative tasks. The integration automatically creates, maintains and deletes users, based on data from your student administrative system. It also creates and maintains group rooms, which teachers and students can use for teaching purposes. The rooms automatically use the language you require and can be categorized according to your needs, making them easier to find. Rooms that are no longer in use are deleted automatically.

=== Configuration in UMS ===
The integration makes it possible to upload pictures of the users to Moodle, making it easy for teachers and students to see whom they are interacting with. If these pictures are replaced in UMS, they are automatically updated in Moodle. Last, but not least, the module can integrate with the AD. This allows users to log into Moodle with the same password they use to access the school’s IT-system. The Moodle integration gives you an easy overview and ensures that the users’ data is always managed correctly, without requiring any manual updates. This frees up time for the IT-department, who can focus on other tasks instead.

If you want to make it easy for students and teachers to keep track of their timetables, you can embed our Web Timetable module in Moodle as an iframe. By doing this, users can access homework and notes that are registered on the various timetable blocks in the timetable. Please note: To embed Web Time Table, the Web Timetable and SSO modules are required. In order to see homework, the Homework module is required.

== Prerequisites ==

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

=== What to have ready ===
Moodle

== Installation ==
Open UMS Configurator and go to Modules > Moodle > Organization settings
[[File:Image.png|none|thumb|537x537px]]

Click Add.
[[File:Moodleorganizationsettings.png|none|thumb|535x535px]]

== Organization settings ==
[[File:Moodle organization settings2.png|none|thumb|508x508px]]

'''Description'''

Give your Organization setting a name.

'''DatabaseServer'''

Name of database server hosting the Moodle database.

'''DatabaseName'''

Name of Moodle database.

'''Database TablesPrefix'''

Table prefix set when installing Moodle.

'''UserName'''

UserName of the user that can access the database.

'''Password'''

Password of the user that can access the database.

'''URL'''

URL for your Moodle installation ex. <nowiki>http://moodle.inlogic.dk</nowiki>

'''Webservice Token'''

Token created in Moodle siteadministration. [https://docs.moodle.org/24/en/Using_web_services Guide to create access and token] ( Remember: When adding functions to webservice, add all functions )

'''DataPath'''

Moodle data path ex. \\moodle.inlogic.dk\c$\Moodle\server\moodledata\filedir.

The user running moodle exe must have access to this path.

'''DatabaseType'''

Choose Database type used for Moodle. can only be one in the list below.
* Microsoft SQL
* MySQL
* Oracle SQL

== Moodle Site settings ==
From Configurator, Edit existing template > Moodle > Manage > Add or Configurator > Modules > Moodle > Site Settings > Add
[[File:Moodle Settings.png|none|thumb|824x824px]]
'''Description:'''

Give the Site settings a name.

'''Organization settings'''

Choose the Organization setting you want to use for this site setting.

'''Default country'''

Choose default country. This is used when creating users.

'''Authentication method'''

Login method for the users

'''Mail domain for new students'''

The address appended to their username in moodle to give them an email address

'''Mail domain for new employees'''

The address appended to their username in moodle to give them an email address

=== Upload student information ===
Check these boxes to send and update information on students
* Address
* Phone (Phone1)
* Mobile Phone (Phone 2)
* Mail

=== Picture library ===
Upload pictures of students

See [[Configurator/Picture_libraries|Picture libraries]]

=== Upload employee information ===
Check these boxes to send and upTemplate Settingsdate information on employees
* Address
* Phone (Phone1)
* Mobile Phone (Phone 2)
* Mail

=== Picture library ===
Upload pictures of employees

See [[Configurator/Picture_libraries|Picture libraries]]

=== Course ===

[[File:Moodle Course Settings.png|none|thumb|732x732px]]

See [[LMS Settings]] for options not descriped below

'''Language'''

The language set on a site when is it created.

'''Course category'''

The category the is put on the site when it's created

==== Activity sites ====
See [[Site selection settings]]

==== Course sites ====
See [[Site selection settings]]

=== Cohort ===

[[File:Moodle Cohort Settings.png|none|thumb|733x733px]]

See [[LMS Settings]] for options not descriped below
==== Activity sites ====
See [[Site selection settings]]

==== Course sites ====
See [[Site selection settings]]

== Template Settings ==
You need to attach a cohort setting to a template. This will tell UMS that cohorts will be created from this template.
[[File:Moodle Template Cohort Settings.png|none|thumb|675x675px]]

'''Description'''

Enter a description for this setting

'''Cohort category'''

Enter a category that will be attached to the cohorts when they are created

'''SQL Groups'''

See [[LMS Settings]] for this option

== FAQ ==

UMS License Install

2017-04-12T13:51:58Z

Juh: /* Har du to servere til UMS, så skal du gøre følgende: */

=== Har du én server til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C[[File:Licens1.png|none|thumb]]
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen.

            Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 1
# Ved at starte configuratoren op på serveren kan man tjekke om der er tilføjet det ønskede modul eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes manuelt fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

=== Har du to servere til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS serverens hostname Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen

            Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS Web serverens hostname
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5

            '''Fortsæt med punkt 9, hvis configurator er installeret på frontend (ved anvendelse af gæstebruger eller massebrugere),'''

            '''så skal frontend licensen nemlig også kopieres til ”UserManagement” folderen på UMS Web serveren.''' '''Hvis ikke configurator er installeret på frontend, gå til punkt 11.'''
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5
# Ved at starte configuratoren op på serveren kan man tjekke, om det ønskede modul er tilføjet eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

UMS License Install

2017-04-12T13:49:12Z

Juh: /* Har du én server til UMS, så skal du gøre følgende: */

=== Har du én server til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C[[File:Licens1.png|none|thumb]]
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen.

            Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 1
# Ved at starte configuratoren op på serveren kan man tjekke om der er tilføjet det ønskede modul eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes manuelt fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

=== Har du to servere til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS serverens hostname Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS Web serverens hostname
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5 '''Fortsæt med punkt 9, hvis configurator er installeret på frontend (ved anvendelse af gæstebruger eller massebrugere),''' '''så skal frontend licensen nemlig også kopieres til ”UserManagement” folderen på UMS Web serveren.''' '''Hvis ikke configurator er installeret på frontend, gå til punkt 11.'''
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5
# Ved at starte configuratoren op på serveren kan man tjekke, om det ønskede modul er tilføjet eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

UMS License Install

2017-04-12T13:32:06Z

Juh: pagebreak test

=== Har du én server til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C[[File:Licens1.png|none|thumb]]
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen. Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 1
# Ved at starte configuratoren op på serveren kan man tjekke om der er tilføjet det ønskede modul eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes manuelt fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

=== Har du to servere til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS serverens hostname Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS Web serverens hostname
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5 '''Fortsæt med punkt 9, hvis configurator er installeret på frontend (ved anvendelse af gæstebruger eller massebrugere),''' '''så skal frontend licensen nemlig også kopieres til ”UserManagement” folderen på UMS Web serveren.''' '''Hvis ikke configurator er installeret på frontend, gå til punkt 11.'''
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5
# Ved at starte configuratoren op på serveren kan man tjekke, om det ønskede modul er tilføjet eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

UMS License Install

2017-04-11T14:51:45Z

Juh: tilretning af tekst

=== Har du én server til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C[[File:Licens1.png|none|thumb]]
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen. Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 1
# Ved at starte configuratoren op på serveren kan man tjekke om der er tilføjet det ønskede modul eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes manuelt fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

=== Har du to servere til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS serverens hostname Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS Web serverens hostname
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5 '''Fortsæt med punkt 9, hvis configurator er installeret på frontend (ved anvendelse af gæstebruger eller massebrugere),''' '''så skal frontend licensen nemlig også kopieres til ”UserManagement” folderen på UMS Web serveren.''' '''Hvis ikke configurator er installeret på frontend, gå til punkt 11.'''
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5
# Ved at starte configuratoren op på serveren kan man tjekke, om det ønskede modul er tilføjet eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

UMS License Install

2017-04-11T14:50:09Z

Juh: UMS License Install manual

=== Har du én server til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C[[File:Licens1.png|none|thumb]]
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen. Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 1
# Ved at starte configuratoren op på serveren kan man tjekke om der er tilføjet det ønskede modul eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes manuelt fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

=== Har du to servere til UMS, så skal du gøre følgende: ===
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS serverens hostname Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen Dette kan være relevant, hvis man oplever mangler ved den nye licensfil.
# Indsæt den licensnøgle du kopierede under punkt 1
# Kopier den fremsendte licensnøgle som er navngivet ud fra UMS Web serverens hostname
# Åben ”bin” folderen C:\inetpub\wwwroot\bin[[File:Licens3.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5 '''Fortsæt med punkt 9, hvis configurator er installeret på frontend (ved anvendelse af gæstebruger eller massebrugere),''' '''så skal frontend licensen nemlig også kopieres til ”UserManagement” folderen på UMS Web serveren.''' '''Hvis ikke configurator er installeret på frontend, gå til punkt 11.'''
# Åben ”UserManagement” folderen C:\Program Files\UserManagement[[File:Licens2.png|none|thumb]]
# Omdøb den licensnøgle der ligger i denne folder til ”[filnavn]_old”, så den kan indlæses igen
# Indsæt den licensnøgle du kopierede under punkt 5
# Ved at starte configuratoren op på serveren kan man tjekke, om det ønskede modul er tilføjet eller om udløbsdato er ændret[[File:Licens4.png|none|thumb]] Hvis du ikke har en genvej til configuratoren, så kan den startes fra ”UserManagement” folderen:[[File:Licens5.png|none|thumb]]

File:Licens5.png

2017-04-11T14:39:32Z

Juh:

Licens5

File:Licens4.png

2017-04-11T14:32:30Z

Juh:

Licens4

File:Licens3.png

2017-04-11T14:29:09Z

Juh:

Licens3

File:Licens2.png

2017-04-11T14:27:49Z

Juh:

Licens2

File:Licens1.png

2017-04-11T14:22:35Z

Juh:

Licens1

UMS License Install

2017-04-11T14:21:34Z

Juh: Created page with "Har du én server til UMS, så skal du gøre følgende: 1. Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C"

Har du én server til UMS, så skal du gøre følgende:

1. Kopier den fremsendte licensnøgle. Højreklik på fil og klik på ”Copy/Kopier” eller tryk CRTL+C

Attendance Registration Card System

2017-03-13T12:18:24Z

Juh: /* Is there something to be obtained - physical */

Attendance Registration Card System is developed for schools, where students to register their own attendance by swiping a card and checking-in when they arrive at the school as well as checking-out when they leave again. By integrating UMS with the card system, it is easy to monitor the students’ attendance. All registrations made through the card system automatically become available in [[UMS]].

Through the user-friendly interface, the teacher can see if everyone has registered correctly and make corrections if necessary. We currently integrate to the Buanco card system. If you prefer to integrate to another card system, please contact us for price and availability.

== Prerequisites ==

=== Supported administrative systems ===
All

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

[[Attendance Registration]]

=== Testing after setup ===
UMS can receive card information from the external card system.

=== What to have ready ===
An external card system with terminals (eg. Buanco). The Card System must be able to exchange cards information with UMS.

=== Is any physical item required ===
External card system.

=== Should third party be contacted ===
Supplier of card system regarding the exchange of card data

== Installation ==
Attendance Registration Card System is part of [[Attendance Registration]]. It will be available when you have the license.

=== Configurations ===
Settings can be found under “Modules\Absence\Card servers”
[[File:Absencecardcardservers.png|none|frame]]

Currently UMS supports 2 different card-systems:
[[File:Absencecardcardserverssettings.png|none|frame]]
* Buanco: Covers cardsystems from Buanco.

* inLogic: All other cardsystems.

=== Cardsystems ===
All cardsystems supported by UMS works with a web service running on the cardsystem server, which UMS querys on a regular basis for any new card entries (come/go).

Enter the necessary information for the cardsystem that are used.
[[File:Absencecardadd.png|none|frame]]

To identify which user has which card, a relationship between the UMS user data and the card identifier needs to be entered. Which field is used is different between systems, typically CPR/SSN is used.

'''Note: UMS only supports one card system pr. Installation. But it is allowed to use cards only for some of the students/departments.'''

=== Service setup ===
Now that the card system is setup, the card-import service needs to be enabled.

This is done under Settings\services:
[[File:Absencecardservicessetup.png|none|frame]]

Enter a valid server name under “Absence card import server”. The server needs to have UMS installed, and also needs to have IP access to the card servers web service.

Finally, the relevant student needs to have cards activated. This is done pr. Template that are using absence (Templates\Edit).
[[File:Absencecardtemplateeditor.png|none|frame]]

Simply check the “Use cards” option on all templates where the card system is used.
[[File:Absencecardmanage.png|none|frame]]

== Technical settings ==

== FAQ ==

UMS Welcome

2017-03-13T12:16:23Z

Juh: /* Is there something to be obtained - physical */

The initial contact with the school's future students is extremely important and with UMS Welcome, you will have the opportunity to give the future students a good first impression when they start school.
UMS Welcome consists of two main elements;

* The welcome window
* Setup page

In this manual we come around all both elements and how they are set up and used in practice.
With the module you will get ample opportunity to combine the welcome by the school's specific needs. It introduces the future students for the most necessary information, so you guarantee that new users make use of the school's technology, already from the start.

== Prerequisites ==

=== Supported administrative systems ===

* User information: Easy-A, SIS and Lectio (Only mobile number).

=== Module requirements ===

==== Must have ====
* UMS
* UMS Web

==== Needed for full support ====
* User information
* UMS Photo
* IT Rules
* Change Password
* SMS Welcome

=== Additional functionality ===

UMS Velkomst skriver "kun" brugerinfo tilbage, hvis man har brugerinfo og export bruger information license.
UMS Velkomst hjælper med, at kunden altid har opdateret kontakt informationer for nye brugere.

=== Testing after setup ===

=== What to have ready ===

Fully updated UMS and UMS Web installation.

=== Is any physical item required ===

If UMS Welcome SMS is wanted, you want a form of SMS modem, or a service that allows sending SMS.

=== Should third party be contacted ===
No.

== Installation ==

=== Installation ===

* Install lastest updates
* Install new license with UMS Welcome

=== Need configuration ===

In order to get your UMS Welcome to work, you need to have access to the "[[control panel]]" link, inside your UMS Web.

== Technical settings ==

This can be done in two different ways. You can either put one welcome up for the entire site, so for example. all fields of study receive the same welcome. This is done under "Web setup" and "Welcome". Here you will see the dropdown menu that allows you to choose your welcomes in.
Alternatively, you can choose to put the welcome on a single template, for example. if the school has different study programs or classes to be shown different welcomes in. This is done by selecting "Edit eksisterende template" and "Welcome". Also here you will see a drop down menu where you can choose from your welcomes in. This way you have the opportunity to make multiple welcomes in for different templates so that they can be adapted directly to the recipient.

[[File:UMSWelcome_Tech1.png]]

App

2017-03-13T12:15:38Z

Juh: /* Is there something to be obtained - physical */

[[File:UMS School App from inLogic.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"]

== 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: Extended: gives “your attendance”, which shows student statistics
*Attendance Registration for UMS School App: gives employee “attendance registration” and student the ability to call in sick
*Homework: gives the employee the ability to create homework
*Link Collection: gives links/bookmarks the school can setup
*Parkzone Integration: gives the ability to create and edit parking permits from Parkzone
*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 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
*Employee Id: this is an id card for an employee similar to the student id
*Parking (Parkzone/Apcoa)
*User information (add/edit)

Note: All Attendance functionality requires Attendance Registration Basic.

=== 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.
*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.

=== Is any physical item required ===

Having a smartphone is a necessity, either an Android, iPhone or a Windows Phone.

=== 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 ==

*Install [[UMS Web]]. The website needs to be public available and run SSL.
*Provide the UMS Web url path to inLogic (+4542408815). 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.
*Setup and run the scheduled job "getStudents"

These are the minimum for the app where you’ll be able to login. inLogic will publish the app either through inLogics account or your schools own account if you have acquired one.

== Technical settings ==

Each chapter only covers specific configuration that involves and applies to the app. For a full detail guide for each module open the corresponding manual. This manual also doesn’t include how to setup schedules task and services that isn’t directly affiliated with the app, the only exception is the service “UMS RSS Feeds” that is specific for the app.

If you can’t find the module you’re looking for in this guide please search for the page. E.g. ParkZone is not describe in this guide as there is no specific configuration that will affect the app alone. Be aware that some changes in the configurator listed in this guide will not only effect the app but also the UMS Web for that specific module.

'''Important''' Most changes will require an IIS reset on the server before it will take effect due to many settings is only loaded once when the website is initializing. The app retrieves settings from UMS once a day, so when you make a change it will take effect in the app the next day or when you log in.

=== Menu Settings ===

This describes how to modify which menu should be shown in the app.
#Open UMS Configurator
#Menu -> Web Setup -> Edit -> App
#Choose modules shown in App
[[File:App_menusettings.png|none|thumb]]
In the example “Grades” has been disabled and will not be shown in the app.

=== 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]]

==== 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]]
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]]
'''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]]
Restart the service to test it and check the output in /UserManagement/RSSFeeds.Log
[[File:App rssfeedlog.png|none|thumb]]

==== 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
#*https://graph.facebook.com/v2.8/inlogic.dk/
Your facebook page url feed should look something like this:
*https://graph.facebook.com/v2.8/schoolname/

This is your feed URL.

Now 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]]
Now you have the access token you need to paste into the configurator.
[[File:App rssfeedurl.png|none|thumb]]
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]]
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]]
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]]
Grades in the app

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.

==== User information ====

----

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

Configurator -> Web Setup -> Edit -> Userinfo
[[File:App userinfo.png|none|thumb]]
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]]
This will enable selfie function.

==== Student ID ====

----

Student ID uses user information and UMS Photo and has no configuration specific for the app.

Make sure Anonymous Authentication is enabled for the folder ‘Webservices’ in Internet Information Services (IIS) Manager for the Default Web Site

To let the users, change their student ID card profile image go to the chapter for User information.

Template:NewPage

2017-03-13T12:12:36Z

Juh: /* Is there something to be obtained - physical */

IT Rules

2017-03-13T12:11:54Z

Juh: /* Module requirements */

The module allows you to display and enforce IT rules for the users. IT rules can be displayed both on domain joined PC’s and in the UMS web Portal.

== Prerequisites ==

=== Supported administrative systems ===
All

=== Module requirements ===
Working UMS installation (Frontend & backend)

=== Additional functionality ===

=== Testing after setup ===
Log on with a uses that is a member of the group that are affected by the IT Rule, both via UMS web portal and a domain PC

=== What to have ready ===
Nothing

=== Is any physical item required ===
No

=== Should third party be contacted ===
No

== Installation ==

This module is already installed with the standard UMS installation.

It requires a valid license for the module, which can be checked under “Help/License info”:
[[File:Help_info.jpg|none|thumb]]
The required license is called “IT Rules”:
[[File:License information.jpg|none|thumb]]

After the license has been verified, UMS is ready to be configured.

=== Configuration of IT rules ===

The IT rules is configured via the already created UMS-templates. This allows for different IT rules for different types of users, UMS supports one IT rule per template.

Settings are found under “Template\IT rules” on each template:
[[File:Configuration.jpg|none|thumb]]
A IT rule consist of the following settings:
[[File:Configuration - it rules.jpg|none|thumb]]

* Description -> Simply enter a saying description of the rule
* AD Group -> Enter a AD group in which the users are made members after they have accepted the IT rule
* Logon before showing rule -> Number of userlogins before the rule is shown
* Logon before sanction -> Number of login before the chosen sanction is applied
* Sanction -> Choose sanction for user that declines the rule.
* IT rule -> Choose which rule is displayed. The rules are html documents, and should be created for each language used on the school.
* Accept/decline buttons -> Enter which text that should be shown on the buttons.

== Technical settings ==

After the initial setup of the module (installation manual), there is two recurring tasks:
* Design of the displayed rules
* Setup of UMS web so that some of the admin tasks can be done via the UMS frontend module.
Design of the IT rules

The IT rules that are shown to the users, are HTML documents.

The documents can be found under each IT rule setting (found on the template).
[[File:It rules document.jpg|none|thumb]]
[[File:It rules Setting.jpg|none|thumb]]
Click manage on the rule you want to edit.

Below is shown an example of a simple IT rule:
[[File:IT Rules editor.jpg|none|thumb]]

As described earlier the IT rule are HTML documents. All standard HTML tags is supported.

Please note that if you wish to use pictures or other linked objects, make sure that the referring links is located on a resource that will work for student (and not a file on a local drive)!

It is possible to add UMS variables to the document, so that it possible to achieve more personalized message/IT rule.

In the example shown above the variable <FirstName> is substituted with the loggedin users firstname at runtime.

The preview button will show how the IT rule will look like for the user:
[[File:IT Rules preview.jpg|none|thumb]]

=== Reset IT rules for a user ===
UMS has a web interface where its possible to reset the IT rule for a user. The interface is found under the common “Controlpanel” in the UMS Frontend.

Before the Controlpanel can be access, a AD group needs to have access granted through the UMS Configurator under “Web Setup”:
[[File:IT Rules web setup.jpg|none|thumb]]

The group needs to be placed under “Global admin group”.

After the group is entered, the following button is available in the UMS Frontend (for members of the group):
[[File:Control panel.jpg|none|thumb]]
Under the control panel, the user will have access to find a user, and reset counters for the IT rule the user is under.

== FAQ ==

IT Rules

2017-03-13T11:43:31Z

Juh: /* Configuration of IT rules */

Introduction text.

== Prerequisites ==

=== Supported administrative systems ===

=== Module requirements ===

=== Additional functionality ===

=== Testing after setup ===

=== What to have ready ===

=== Is there something to be obtained - physical ===

=== Should third party be contacted ===

== Installation ==

This module is already installed with the standard UMS installation.

It requires a valid license for the module, which can be checked under “Help/License info”:
[[File:Help_info.jpg|none|thumb]]
The required license is called “IT Rules”:
[[File:License information.jpg|none|thumb]]

After the license has been verified, UMS is ready to be configured.

=== Configuration of IT rules ===

The IT rules is configured via the already created UMS-templates. This allows for different IT rules for different types of users, UMS supports one IT rule per template.

Settings are found under “Template\IT rules” on each template:
[[File:Configuration.jpg|none|thumb]]
A IT rule consist of the following settings:
[[File:Configuration - it rules.jpg|none|thumb]]

* Description -> Simply enter a saying description of the rule
* AD Group -> Enter a AD group in which the users are made members after they have accepted the IT rule
* Logon before showing rule -> Number of userlogins before the rule is shown
* Logon before sanction -> Number of login before the chosen sanction is applied
* Sanction -> Choose sanction for user that declines the rule.
* IT rule -> Choose which rule is displayed. The rules are html documents, and should be created for each language used on the school.
* Accept/decline buttons -> Enter which text that should be shown on the buttons.

== Technical settings ==

After the initial setup of the module (installation manual), there is two recurring tasks:
* Design of the displayed rules
* Setup of UMS web so that some of the admin tasks can be done via the UMS frontend module.
Design of the IT rules

The IT rules that are shown to the users, are HTML documents.

The documents can be found under each IT rule setting (found on the template).
[[File:It rules document.jpg|none|thumb]]
[[File:It rules Setting.jpg|none|thumb]]
Click manage on the rule you want to edit.

Below is shown an example of a simple IT rule:
[[File:IT Rules editor.jpg|none|thumb]]

As described earlier the IT rule are HTML documents. All standard HTML tags is supported.

Please note that if you wish to use pictures or other linked objects, make sure that the referring links is located on a resource that will work for student (and not a file on a local drive)!

It is possible to add UMS variables to the document, so that it possible to achieve more personalized message/IT rule.

In the example shown above the variable <FirstName> is substituted with the loggedin users firstname at runtime.

The preview button will show how the IT rule will look like for the user:
[[File:IT Rules preview.jpg|none|thumb]]

=== Reset IT rules for a user ===
UMS has a web interface where its possible to reset the IT rule for a user. The interface is found under the common “Controlpanel” in the UMS Frontend.

Before the Controlpanel can be access, a AD group needs to have access granted through the UMS Configurator under “Web Setup”:
[[File:IT Rules web setup.jpg|none|thumb]]

The group needs to be placed under “Global admin group”.

After the group is entered, the following button is available in the UMS Frontend (for members of the group):
[[File:Control panel.jpg|none|thumb]]
Under the control panel, the user will have access to find a user, and reset counters for the IT rule the user is under.

== FAQ ==

IT Rules

2017-03-13T11:41:09Z

Juh: /* Technical settings */

Introduction text.

== Prerequisites ==

=== Supported administrative systems ===

=== Module requirements ===

=== Additional functionality ===

=== Testing after setup ===

=== What to have ready ===

=== Is there something to be obtained - physical ===

=== Should third party be contacted ===

== Installation ==

This module is already installed with the standard UMS installation.

It requires a valid license for the module, which can be checked under “Help/License info”:
[[File:Help_info.jpg|none|thumb]]
The required license is called “IT Rules”:
[[File:License information.jpg|none|thumb]]

After the license has been verified, UMS is ready to be configured.

=== Configuration of IT rules ===

The IT rules is configured via the already created UMS-templates. This allows for different IT rules for different types of users, UMS supports one IT rule per template.

Settings are found under “Template\IT rules” on each template:
[[File:Configuration.jpg|none|thumb]]
A IT rule consist of the following settings:
[[File:Configuration - it rules.jpg|none|thumb]]

* Description Simply enter a saying description of the rule
* AD Group Enter a AD group in which the users are made members after they have accepted the IT rule
* Logon before showing rule Number of userlogins before the rule is shown
* Logon before sanction Number of login before the chosen sanction is applied
* Sanction Choose sanction for user that declines the rule.
* IT rule Choose which rule is displayed. The rules are html documents, and should be created for each language used on the school.
* Accept/decline buttons Enter which text that should be shown on the buttons.

== Technical settings ==

After the initial setup of the module (installation manual), there is two recurring tasks:
* Design of the displayed rules
* Setup of UMS web so that some of the admin tasks can be done via the UMS frontend module.
Design of the IT rules

The IT rules that are shown to the users, are HTML documents.

The documents can be found under each IT rule setting (found on the template).
[[File:It rules document.jpg|none|thumb]]
[[File:It rules Setting.jpg|none|thumb]]
Click manage on the rule you want to edit.

Below is shown an example of a simple IT rule:
[[File:IT Rules editor.jpg|none|thumb]]

As described earlier the IT rule are HTML documents. All standard HTML tags is supported.

Please note that if you wish to use pictures or other linked objects, make sure that the referring links is located on a resource that will work for student (and not a file on a local drive)!

It is possible to add UMS variables to the document, so that it possible to achieve more personalized message/IT rule.

In the example shown above the variable <FirstName> is substituted with the loggedin users firstname at runtime.

The preview button will show how the IT rule will look like for the user:
[[File:IT Rules preview.jpg|none|thumb]]

=== Reset IT rules for a user ===
UMS has a web interface where its possible to reset the IT rule for a user. The interface is found under the common “Controlpanel” in the UMS Frontend.

Before the Controlpanel can be access, a AD group needs to have access granted through the UMS Configurator under “Web Setup”:
[[File:IT Rules web setup.jpg|none|thumb]]

The group needs to be placed under “Global admin group”.

After the group is entered, the following button is available in the UMS Frontend (for members of the group):
[[File:Control panel.jpg|none|thumb]]
Under the control panel, the user will have access to find a user, and reset counters for the IT rule the user is under.

== FAQ ==

File:Control panel.jpg

2017-03-13T11:39:27Z

Juh:

Control panel

File:IT Rules web setup.jpg

2017-03-13T11:38:14Z

Juh:

IT Rules web setup

File:IT Rules preview.jpg

2017-03-13T11:36:52Z

Juh:

IT Rules preview

File:IT Rules editor.jpg

2017-03-13T11:34:54Z

Juh:

IT Rules editor

File:It rules Setting.jpg

2017-03-13T11:33:26Z

Juh:

It rules Setting

File:It rules document.jpg

2017-03-13T11:05:10Z

Juh:

It rules document

IT Rules

2017-03-13T10:46:59Z

Juh: /* Configuration of IT rules */

File:Configuration - it rules.jpg

2017-03-13T10:46:37Z

Juh:

it-rules settings

File:Configuration.jpg

2017-03-13T10:45:34Z

Juh:

it-rules in configurator

IT Rules

2017-03-13T10:40:12Z

Juh: /* Installation */

IT Rules

2017-03-13T10:38:35Z

Juh: /* Installation */

IT Rules

2017-03-13T10:37:15Z

Juh: /* Installation */

File:License information.jpg

2017-03-13T10:35:43Z

Juh:

license information window

File:Help info.jpg

2017-03-13T10:33:10Z

Juh:

License info under help

IT Rules

2017-03-13T10:18:38Z

Juh: /* Installation */

IT Rules

2017-03-13T10:17:47Z

Juh: Created page with "Introduction text. == Prerequisites == === Supported administrative systems === === Module requirements === === Additional functionality === === Testing after setup ===..."