The System Parameters view is used to maintain system-wide settings and module specific settings.
The create, amend, and delete permissions are turned on and off from the Security Control window. If these flags are set to inactive, the user will not be able to perform any of the processes. |
Only modules (that have a system parameter option) available to your organisation should appear on the list. |
System Maintenance - System Parameters
When a client/company is first created, the system parameter records will be created alongside the client. Each will have a default value (if there is any).
Module panels
The System Parameters view is made up of collapsible grid panels. Each panels represents a module where the user can set module settings.
Module |
Parameter |
Description |
---|---|---|
Maintenance |
Company Name |
The "Company Name" that you want to appear on the report header. |
Address Line 1 |
Address Line 1 |
|
Address Line 2 |
Address Line 2 |
|
Town |
Town |
|
County |
County |
|
Postcode |
Postcode |
|
Extra Report Line |
The text in this system parameter will appear below the Company Name on the report header. |
|
Hide Location/Organisation Entry Form |
When set to Yes, the Entry form on the Location/Organisation views will be hidden. This will stop the users from adding/updating new structures in the system and will only retain the data imported for them when they first started using the system. |
|
By default, when user creates a new room, the risk is taken from the functional area's risk level. Setting this option to Yes, displays the Risk Level field in the Physical Location - Rooms view which allows the user to change the risk level for specific rooms. |
||
When a value has been added in this system parameter, the mobile users will need to type in this pin code when they make changes to the device settings, including the clearing of device settings.
Please note, the Mobile Pin Code is not required when registering a token for the first time, it is only required after the token has been registered. |
||
Physical Location Room Tier *read-only |
This parameter is set-up by Asckey. It is to indicate which tier from the structure is the room tier. |
|
Cleaning |
Random Audit % |
This is the percentage of the available audits that will be selected when you select the 'Random' button on the Monitoring - Create Multiple Audits view. |
Target Completed Room Audit % |
This is the percentage of the target total completed rooms against an Audit Group / Functional Area. |
|
Optional Corrective Actions |
Setting this value to "True" will make the corrective actions optional when failing an element. |
|
Add Item When Present x Times |
When an item had been added to the monitoring element list for a given audit over x consecutive audits, the element will be added to the cleaning area that the audit is for. When you carry out audits, if you consistently add an element to the audit, when you have added the same element to an audit x number of times, it will be automatically added to the cleaning area for that audit and any subsequent audits for that cleaning area will then also have that element added.
|
|
Remove Item When Not Present x Times |
This is the opposite to the above add item. The difference being where you remove an element x times, it will be removed from the cleaning area. |
|
Populate the Result Failure "Checked By/Date" when a Reaudit is Signed Off (Yes/No) |
If the parameter is set to "Yes", when a re-audit is signed off, this will automatically populate the Checked By & Checked Date fields of the original audit failure results. |
|
If value = 'Yes', then only show the latest audit record of any audits that have been re-audited. E.g. If Audit #1 achieved a failed score and created a system generated Audit #2, all the reports will then look at Audit #2 and disregard Audit #1. |
||
If Value = "Yes", then the reports will filter based on the cleaning audits "Original Audit Date" value. E.g. If Audit 1 is carried out on 28/06/2016, then a re-audit record was created (Audit 2), the Original Audit Date of Audit 2 will be equal to 28/06/2016.
|
||
The default survey template ID that you want to associate with the cleaning audit record. |
||
If set to “Yes”, once a cleaning audit record has been created, create a new survey for the *Linked Survey Template ID* if there are no outstanding survey for the same functional area on the same audit date.
If set to “No”, once a cleaning audit record has been created, the user will be given a message box where the user can specify a different survey template ID or leave the field blank to create/not create a survey link.
|
||
The Default Audit By value of the re-audit record. If this is not filled in, the re-audit will automatically get allocated to the person who completed the original audit. |
||
If set to "Yes", the tier 0 description will be excluded from the location path when audits are downloaded on the Mobile application. |
||
If set to "Yes", the audit score (%) gets displayed on the mobile application for the cleaning module. |
||
Update Outstanding Audits Following Area Change |
If set to "Yes", when user change the element list in a cleaning area, all of the outstanding audits get updated: 1. If an element is removed from the cleaning area, all outstanding audits for the area should mark the element as "Not Present". 2. If an element is added to the cleaning area, all outstanding audits for the area should automatically add the element to the monitoring-results list.
|
|
The default score for the elements on a room audit. |
||
Commit Signed Off Audits After "X" Number of Days |
The number of days when the signed off audits get "committed" and becomes read-only e.g.: Setting the value of this parameter to 30 days, mean that the audits that are signed off from Dec 01, 2019, will become read-only from Dec 31, 2019 onwards.
|
|
Auto Audit Grouping |
If set to Yes, the system will do the grouping depending on the functional area, audit date, and monitoring type. If you’re adding a room audit to an existing group, and the functional area, monitoring type, and audit date match the group properties, then the room audit will automatically belong to the existing group, otherwise it will create a new audit group. |
|
Survey |
Allow "Commit" on Mobile |
If set to "Yes", the "Save & Commit" button will show on the mobile interface for Survey. It will also auto commit any surveys that are signed off. |
Ticket Administration |
Default Priority ID |
Default Priority ID used when creating new tickets. |
Auto-Sync Time (Every x Minutes) |
The number of minutes when the mobile application makes a call to the server to download tickets. e.g. When set to 15, providing a network connection is available, the mobile will download tickets every 15 minutes. |
|
Mobile Ticket List Colour Style |
The ticket list in the mobile application will be coloured based on this parameter. Currently defaults to PRIORITY, which means the list will be coloured based on the colour set against the priority in Task Advanced Options. |
|
Mobile - Display Travel Time |
If set to Yes, the Arrive / Start Work button will be displayed in the Ticket Details page in the mobile application. This feature is useful for users who have to travel to get to a job. To use this, the user will have to click on the Log On button before setting off to the job and press the Arrive / Start Work button when they get to the destination. This will record the travel time against the Work-In-Progress event. |
|
Mobile - Ticket Event Download Days |
The number of event days to download in the mobile application. e.g. If the system parameter is set to 5 days, this will download the Ticket Events that have a created date greater than or equal to (Today - 5 Days). |
|
Commit Closed Ticket After X Days |
The number of days to commit all closed tickets. e.g. If set to 30 days, all tickets that have a Closed Date/Time of older than 30 days will become read-only / unchangeable. |
Copyright © 2006-2023 ASCKEY Data Services Limited. All rights reserved.