System Management: IVCO Visit System Keys

There are a number of system keys set up that determine how the IVCO Visits System will function:

Key	Description	Explanation
VI		This key is just a placeholder and is not used.
VI__DATA	Where is the IVCO Visits Data?	This key is currently not used.
VI__INSTALLED	Is the IVCO Visits System Installed?	This key is currently not used.
VI_BC_USE_SITE_CODE	Use Site Code to print Company Address	This key determines whether the Company Address on the Blue Card is printed using the information from the Site Code field. It can be used if WiSeMan is being operated as a multi-site installation. If set to Y and if there is a Site Code entered on the Blue Card the address associated with the Site Code will be printed. If set to N, or if there is no Site Code entered on the Blue Card, the address found in the system keys SYS_CO_ADDRESS_1 and SYS_CO_ADDRESS_2 are used instead.
VI_CASUAL_COURIER	Print the Casual Courier statement on the BP	This key determines whether the Casual Courier statement is print on the Blue Card Business Persons certificate. If set to Y the Casual Courier statement is included. If set to N the Casual Courier statement is not included.
VI_CHECK_AUTH_EXPIRY	Check Visitors Clearance Expiry Date against Visit	This key is used in the Visitor Validation routine and determines whether a person's Clearance Authorisation Expiry date is checked on a visit. If set to Y a person will fail validation on a visit if their Clearance expires before the end date of the Visit. If set to N a person's Clearance Expiry is not checked as part of the validation procedure.
VI_CHECK_SECURITY	Check Visitor Clearance Level against Visit	This key is used in the Visitor Validation routine and determines whether a person's Clearance Level is sufficient for the Classification of the Visit. If set to Y a person will fail validation on a visit if their Clearance Level is lower than the Classification Level of the Visit. If set to N a person's Clearance Level is not checked as part of the validation procedure.
VI_COMPANY_TYPE	Type of Company for RFV Forms	This key is used when producing the RFV / eRFV and specifies what type of company in running the Visits system. This must be set to one of the following values: EU Government Industry Military NATO
VI_DEF_TS_REF	Default TS Reference Code	This key is used in the Blue Card Entry / Update option to give a default IVCO-approved Classification Code for the individual. The default value is NS (NATO Secret).
VI_DEFAULT_SITE	Default Requesting Site Code	This key is only used if you are operating WiSeMan in a multi-site environment with each site responsible for their own visits. It is set to the Site Code of the site generating the most Visits. Leave Blank if you are not operating a multi-site installation or if only one site is responsible for submitting Visits.
VI_EMAIL_FAIL	Email Send Failure Status Code	This key is not currently used.
VI_EMAIL_IVCO	Email Address for IVCO Visits	This key is not currently used.
VI_EMAIL_KEEP	Keep Attachments after Sending	This key is not currently used.
VI_EMAIL_OUTPUT_DIR	Output Directory doe Outward Visit Files	This key is not currently used.
VI_EMAIL_SEND	Send Email automatically	This key is not currently used.
VI_EMAIL_SETUP	Is Email Available for Outward Visits?	This key is not currently used.
VI_EMAIL_SITE_CODE	IVCO Supplied Company Code	This key is not currently used.
VI_EMAIL_STATUS	Visit Status for Electronic Send to IVCO	This key is not currently used.
VI_EMAIL_SUBJECT	Email Subject Line Prefix	This key is not currently used.
VI_IVCO_AUTO_NO	Is Automatic IVCO Visit Numbering Required?	If set to Y then the system will generate a Visit Number for any New Visits if the user does not enter a number manually. If set to N then the system will ensure that the user always enters the number manually.
VI_IVCO_CONT_EMAIL	Email of the Site IVCO Contact	The value entered in this key will be printed on all Visit Forms in the Section 5 - Certification of Security Clearance section, e.g. ivco@company.com .
VI_IVCO_CONT_NAME	Name of the Site IVCO Contact	This key is no longer used.
VI_IVCO_CONT_TEL	Telephone Number of the Site IVCO Contact	This key is no longer used.
VI_IVCO_CONT_TITLE	Job Title of the Site IVCO Contact	This key is no longer used.
VI_IVCO_LAST_NO	Last IVCO Visit Number Used	This key is used to generate a Visit Number for any New or Duplicated Visits if the key VI_IVCO_AUTO_NO is set to Y. This key has the format ££££/££ where £ is a number, e.g. 0016/18. Only the first four digits will be incremented. This key needs to be reset at the beginning of the year, i.e. 0147/18 becomes 0000/19.
VI_IVCO_LOCAL_CNTRY	Local Country Code	This key determines the code that is put into the Country field for New Visits. This value should be a valid country code, see Country Codes.
VI_MAX_UPDATES	Maximum Number of Amendments allowed	This key is checked when adding Visitors to an existing Visit. Once the number of amendments made reaches this number, a new Visit must be submitted to IVCO.
VI_MULTI_CONTROLLER	Allow Multiple Security Controller Details	This key determines whether there are multiple Security Controllers that can authorise site visits, e.g. in a multi-site installation. This key is checked when producing all RFV / eRFV forms as well as printing Blue Cards. If set to Y a pop-up window will be displayed when printing relevant forms allowing the user to pick the correct Security Controller details to be used on the forms. If set to N the Security Controller details held in the system keys SYS_CO_CONTROL, SYS_CO_CONTROL_EMAIL, SYS_CO_CONTROL_FAX, SYS_CO_CONTROL_TEL and SYS_CO_CONTROL_TITLE are used on the forms.
VI_PASSPORT_EXP_MONTHS	Number of Months before Passports Expire	This key is used on the Blue Card and when adding a new Visitor to a Visit. In Blue Card Entry / Enquiry, if the Visitor's passport expires less than this number of months from the current system date, a warning message will be displayed on the screen in red. In Visit Entry / Enquiry a Visitor's passport cannot expire less than this number of months from the current system date or less than this number of months from the Visit Start Date. If it does, the Visitor will fail the Validation check.
VI_PRINT_NOTES	Print IVCO Visit Notes as Comments on Visit Request	This key determines whether any information stored in the Notes section of a Visit are printed in the Comments section of all RFV / eRFV forms. If set to Y any Notes for a Visit will be printed in the Comments section of the RFV / eRFV. If set to N Notes for a Visit will not be printed in the Comments section of the RFV / eRFV. Care must be taken to only add relevant information in Notes if this key is set to Y.
VI_RFV_DUPLEX	Is the RFV printed on both sides of the paper	This key allows the RFV form to be produced in a format to allow printing on both sides of the paper. If set to Y any RFV form with an odd number of pages on the Site details will have a blank page added to ensure the correct separation from the Visitor details when printed. If set to N no blank page will be printed.
VI_RFV_ERFV	Name of the eRFV Template File	This key holds the name of the IVCO-supplied eRFV template file. It should only be changed if the site changes the name of this file. Please consult with Quartz Computing before modifying this key.
VI_RFV_EXPORT_FOLDER	Sub-Folder for eRFV XML Export/Import Files	This key holds the name of the folder that all eRFV export files will be stored. It should only be changed if the site changes the location of these files. Please consult with Quartz Computing before modifying this key.
VI_RFV_XFA_API	eRFV XFA API Version	This key holds details of the API version required to use the XFA auto-import function of the eRFV. This key should never need modifying unless the PDF-writer functionality changes. Please consult with Quartz Computing before modifying this key.
VI_RFV_XFA_GEN	eRFV XFA Generator	This key holds details of the Generator version required to use the XFA auto-import function of the eRFV. This key should never need modifying unless the PDF-writer functionality changes. Please consult with Quartz Computing before modifying this key.
VI_SEC_CON_POC	Allow the use of the Security Controller as P.O.C	This is used in the Visit Entry / Enquiry screen and determines whether it is possible to use the Site to be Visited Security Controller's details as the Second Point of Contact for a Visit. If set to Y and there is a Site Code entered for the Site to be Visited and there are Security Controller details already entered for that Site, the user will be asked if they want to use this information as the Second Point of Contact for the Visit. If set to N or there is no Site Code entered or there is no Security Controller details entered for the Site, the user will not be asked this question and will have to fill in the Second Point of Contact manually.