Admin: Redirected page to Category:System management

2014-04-28T14:25:41Z

Redirected page to Category:System management

Admin: Created page with "System Management in PARS is the main area where technical configuration is carried out. In general, users should not have access to it unless they are involved with the t..."

2014-04-28T13:28:00Z

Created page with "System Management in PARS is the main area where technical configuration is carried out. In general, users should not have access to it unless they are involved with the t..."

New page

System Management in PARS is the main area where technical [[configuration]] is carried out. In general, users should not have access to it unless they are involved with the technical administration of PARS .net.

If the user has the correct [[List of permissions|permissions]], they will see the following items under the System Management section of the [[PARS main menu]].

==[[Configure Permissions|Configure user permissions]]==

This is where individual [[List of permissions|permissions]] can be assigned to a user. It is also where permissions templates can be [[Configure Permissions|configured]] and then applied to groups of similar users. All of the items on the [[PARS main menu]] can be hidden or assigned to a user by using permissions.

==[[Configure Preferences]]==

[[Configure Preferences|Preferences]] are global in PARS, once set they affect every user in the same way.

==[[Registration preferences]]==

[[Registration preferences]] are global and affect all users who take registers. Note that Registration preferences only apply to attendance marks recorded via a [[Register|register]] screen and not other data entry screens (e.g. [[Attendance View]], [[Deal with unexplained marks]]. For this reason, it is important that in general teachers are only able to enter attendance marks via the [[Register|register]] screen.

[[Registration preferences]] affect the visual appearance of the register, the options teachers can access on the register, the warnings that can appear during registration, the configuration of [[Biometrics|biometric readers]], the way [[Session]] marks can be automatically changed and finally the time that registration takes place.

==PARS Connect kickout==
You can use this option to kick all users out of PARS Connect.

==[[Configure proxy server]]==

If a [[Configure proxy server|proxy server]] is used to access the internet (e.g. for the purposed of sending [[Email|emails]], [[Text Messaging|SMS/text messages]] etc) then the details of the server may need to be entered here.

==Repair console==

The [[Repair Console]] allows SQL statements to be run on tables in the database, it is used for more advanced troubleshooting where the school has no access to SQL management tools from Microsoft.

==[[Kill MS SQL Processes]]==

When running a SIMS update it is sometimes necessary to kick all users out of PARS .net so the database can be locked. This option allows the person doing the update to remove all PARS users from the database and prevent them from logging in until an unlock password is entered.

==[[Manage Helpdesk Tickets]]==

If an error occurs with the PARS .net software, a ticket is automatically posted to the [[Helpdesk]]. The ticket contains technical details about exactly which area of the software has gone wrong and why the error occurred. Existing tickets can be reviewed and exported from here.

==[[Management reports]]==

These [[Management reports|reports]] are useful for troubleshooting problems with group lists and startup times.

==[[Maintain codes]]==

The list of available attendance codes can be extended to include new codes not found in SIMS.

==[[Configure external status]]==

If the school uses [[Configure external status|swipe cards]] to record [[:Category:Attendance|attendance]] or pupils' [[Signing in|signing in]] status, some technical configuration will need to be carried out here.

==[[Configure Custom Launch]]==

Users can add shortcuts to other software packages to the [[Configure Custom Launch|Custom launch]] option on the [[PARS main menu]].

← Older revision		Revision as of 14:25, 28 April 2014
Line 1:		Line 1:
−	~~System Management in PARS is the main area where technical~~ [[~~configuration]] is carried out. In general, users should not have access to it unless they are involved with the technical administration of PARS .net.~~	+	#REDIRECT[[Category:System management]]
−
−	~~If the user has the correct [[List of permissions\|permissions]], they will see the following items under the~~ System ~~Management section of the [[PARS main menu]].~~
−
−
−	~~==[[Configure Permissions\|Configure user permissions]]==~~
−
−	This is where individual [[List of permissions\|permissions]] can be assigned to a user. It is also where permissions templates can be [[Configure Permissions\|configured]] and then applied to groups of similar users. All of the items on the [[PARS main menu]] can be hidden or assigned to a user by using permissions.
−
−	~~==[[Configure Preferences]]==~~
−
−	~~[[Configure Preferences\|Preferences]] are global in PARS, once set they affect every user in the same way.~~
−
−	~~==[[Registration preferences]]==~~
−
−	[[Registration preferences]] are global and affect all users who take registers. Note that Registration preferences only apply to attendance marks recorded via a [[Register\|register]] screen and not other data entry screens (e.g. [[Attendance View]], [[Deal with unexplained marks]]. For this reason, it is important that in general teachers are only able to enter attendance marks via the [[Register\|register]] screen.
−
−	[[Registration preferences]] affect the visual appearance of the register, the options teachers can access on the register, the warnings that can appear during registration, the configuration of [[Biometrics\|biometric readers]], the way [[Session]] marks can be automatically changed and finally the time that registration takes place.
−
−	~~==PARS Connect kickout==~~
−	~~You can use this option to kick all users out of PARS Connect.~~
−
−	~~==[[Configure proxy server]]==~~
−
−	If a [[Configure proxy server\|proxy server]] is used to access the internet (e.g. for the purposed of sending [[Email\|emails]], [[Text Messaging\|SMS/text messages]] etc) then the details of the server may need to be entered here.
−
−	~~==Repair console==~~
−
−	~~The [[Repair Console]] allows SQL statements to be run on tables in the database, it is used for more advanced troubleshooting where the school has no access to SQL~~ management ~~tools from Microsoft.~~
−
−	~~==[[Kill MS SQL Processes]]==~~
−
−	When running a SIMS update it is sometimes necessary to kick all users out of PARS .net so the database can be locked. This option allows the person doing the update to remove all PARS users from the database and prevent them from logging in until an unlock password is entered.
−
−	~~==[[Manage Helpdesk Tickets]]==~~
−
−	If an error occurs with the PARS .net software, a ticket is automatically posted to the [[Helpdesk]]. The ticket contains technical details about exactly which area of the software has gone wrong and why the error occurred. Existing tickets can be reviewed and exported from here.
−
−	~~==[[Management reports]]==~~
−
−	~~These [[Management reports\|reports]] are useful for troubleshooting problems with group lists and startup times.~~
−
−	~~==[[Maintain codes]]==~~
−
−	~~The list of available attendance codes can be extended to include new codes not found in SIMS.~~
−
−	~~==[[Configure external status]]==~~
−
−	If the school uses [[Configure external status\|swipe cards]] to record [[:Category:Attendance\|attendance]] or pupils' [[Signing in\|signing in]] status, some technical configuration will need to be carried out here.
−
−	~~==[[Configure Custom Launch]]==~~
−
−	~~Users can add shortcuts to other software packages to the [[Configure Custom Launch\|Custom launch]] option on the [[PARS main menu~~]].

System management - Revision history

Admin: Redirected page to Category:System management

Admin: Created page with "System Management in PARS is the main area where technical configuration is carried out. In general, users should not have access to it unless they are involved with the t..."