Difference between revisions of "User Record Import Guide"

From Adjutant Wiki
 
(19 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
__NOTOC__
 +
==General Data Import Notes==
  
−
==General Import Template File Notes==
+
Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.
  
−
*Template files are typically generated from their respective Import screen using an 'Export Template' button.
 
−
*Using the 'Export Template' button from an updated system will help ensure that you provide the customer with the most up-to-date import file, and will help avoid errors.
 
−
*Templates generally (but not in all cases) contain 3 rows of header information.
 
−
**The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed.
 
−
**The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the mapping process difficult.
 
−
**The third row is labelled with the same values from row 2, an is available to create a customer-friendly name for the associated data column. 
 
−
***The third row should be removed from the source file prior to importing.  It will cause errors since it will be treated as the first import record on the file.
 
−
*Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format (until further notice). The import screens will generate errors if the file type is not correct.
 
  
−
*It is a good idea to perform a Mapping Table Import using a current source list before beginning on any imports.  Without a current mapping table, the quality of imports can be compromised.
+
 
−
**Export a current list from a good source (such as ABIS)
+
==User Record Import Notes==
−
**Perform a Mapping Table Import on the target system with the XLS file from the step above
+
 
 +
The Import User screen creates the User in Adjutant attribute record, links it to the Contact ID, and can complete all of the required fields in the User Details tab and the User Password Settings tab.  The import program can even establish user security mimics.
  
  
−
==User Record Import Notes==
 
  
 
===Timing and Preparation===
 
===Timing and Preparation===
 +
 +
User in Adjutant details and all of the appropriate named user license flags should be set up as soon as possible once the core system setup items have been completed. User licenses are generally billed from the very beginning of the implementation, so customers should be able to access the system as soon as it is available. Setting up user records immediately avoids a situation where customers are being billed for user licenses that they are unable to use.
  
 
All Address Book setup items should be completed prior to beginning the Contacts, Customer, and Vendor imports. The [[Address Book Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing customer, vendor and contact records.
 
All Address Book setup items should be completed prior to beginning the Contacts, Customer, and Vendor imports. The [[Address Book Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing customer, vendor and contact records.
  
−
Internal Contacts such as employees or other contacts linked to the parent organization should be imported first. User records, resource records, salespersons, account managers, buyers, and project attributes should be established for employee records prior to importing the Organization (Customer and Vendor) records. Both the Customer and Vendor imports can link the employee records, such as salespersons, directly to the organizations if the employee contact records exist beforehand.  
+
The User Import can be completed immediately after the employee contact records have been imported with the [[Contact Import Guide|Import Contacts]] screen, or after they have been added manually. The internal contact records should be added prior to completing the Customer and Vendor imports. User records, resource records, salespersons, account managers, buyers, and project attributes should be established for employee records prior to importing the Organization records so that links to salespersons, account managers, and buyers can be made in the organization import files.
  
−
Both the Customer and Vendor import templates can create and link up to 4 contacts per organization. In many cases, this will be enough to complete the basic Contact imports for most organizations. For organizations with more than 4 contacts, a separate Contact import will be required.
 
  
  
 
===General Notes===
 
===General Notes===
  
−
'''Phone Numbers''' - It is best practice to follow a set pattern for the 4 phone number codes that can be imported.  Using the codes from the Contact Phone Codes (PHONECODES) rule, establish a consistent pattern for coding all imported phone number. For example, all Phone1 Codes should be Cell(CE), all Phone2 codes should be Home(HO), and so on. Ideally, the order of the phone codes should match the order set in the rule.  
+
Many of the fields on the Import User Records template are mandatory. Required fields are noted below in the file definitions section.
 +
 
 +
The Password Settings fields must be filled in on the import file.  CID password setting defaults are not loaded during the import.
 +
 
 +
 
 +
 
 +
==User Record Import File Data Scrubbing==
 +
 
 +
Since nearly all of the data fields in the User Import file are Adjutant security specific fields, the customer will not have a source file to provide for this data. Generally, the only customer-supplied data for this file will be the userids, passwords, and email settings. In many cases the userids and passwords will be generated by ABIS personnel.
 +
 
 +
Because the data for this file is mostly generated by ABIS personnel to speed up the process of adding users, there is no customer data scrubbing required.
 +
 
 +
 
 +
 
 +
==Import User Screen (IMPORTUSER)==
 +
 
 +
Menu Location: Transaction>>Importers/Exporters>>Other>>Import User Records
  
−
'''Contact Attributes''' - The contact import process can attach all of the required contact attributes during the import process.  However, it is important to know that each attribute selected during the import process will be applied to ALL contacts imported on that import process. The contact import file may need to be split into several separate import files, and run in batches, if unique attributes are needed for certain groups of contacts.  
+
[[File:IMPORTUSER.png]]
  
−
'''Address Data''' - Addresses will not automatically pull from the associated Custno.  The AddressA (Business) details must exist in the import file in order to get created with the contact record.
 
  
 +
'''Import File Name/Browse:''' Use the Browse button to locate and select the completed User import template file (in XLS format)
  
 +
'''Export Template:''' Generates a blank User Import template file
  
−
==Contact Import File Data Scrubbing==
+
'''Map Fields:''' Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping.  Repeat for any red lines on the left that should be mapped.  If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.
  
−
Every customer's data will have different issues that need addressing. SOme of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing.  This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during contact data scrubbing include:
+
'''Validate to XLS File:''' Selecting this box will create an XLS errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.
  
−
* '''Address Standardization''' - Standardize the data in the address2 and address3 fields for all records.  For example, if you see suite numbers in both address2 and address3, try to move them all to address2. Sort the file by address columns and try to correct spelling issues in city. Standardize the state codes and fill in any obvious missing or incomplete entries.
 
  
−
* '''Email Addresses''' - Move any email addresses from incorrect data columns to the correct email data column. Look for any obvious email format issues like missing the '.com' or misspelled common email domains.
+
==User Record Import File Definitions==
  
−
* '''Phone Numbers''' - Make sure phone numbers are complete, with area code if possible.  Discuss any incomplete phone number details with customer prior to import. Provide a list of phone numbers that may not import, or may import but will be unusable.
+
Required fields are indicated with *
  
−
* '''Invalid Data''' - Address any invalid, incomplete, or otherwise bad data with the customer as soon as possible. Avoid importing and perpetuating bad data.  Give the customer an opportunity to fix any data prior to import.  We don't want to carry forward any bad habits or bad records if we have a chance to avoid it.
+
'''*f1 - Contid''' - Contact ID (CONTID (keyno) of contact record)
  
 +
'''f2 - Userid''' - Desired User ID. If left blank, the system will generate a UserID based of the contact name.
  
 +
'''f3 - Password''' - Desired Password
  
−
==Contact Import Screen (IMPORTCONTACT)==
+
'''f4 - Admin''' - Should the user be an Admin in Desktop (Y/N)
  
−
Menu Location: Transaction>>Importers/Exporters>>Address Book>>Contact Import
+
'''f5 - Defprinter''' - User's Default Printer ID
  
−
[[File:IMPORTCONTACT.png]]
+
'''f6 - Termid''' - Scanner terminal ID
  
 +
'''f7 - Freq''' - Scanner frequency setting
  
−
'''File Name/Browse:''' Use the Browse button to locate and select the completed contact import template file (in XLS format)
+
'''*f8 - Defloctid''' - Default Warehouse name. Enter the Warehouse name, not the LOCTID value.
  
−
'''Export Template:''' Generates a blank Contact Import template file
+
'''*f9 - Defcid''' -  Default CID name
  
−
'''Map Fields:''' Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped.  If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.
+
'''f10 - DefLaser''' - Default Laser Printer name
 +
 
 +
'''f11 - DefLaserNo''' - Default Laser Printer ID
 +
 
 +
'''*f12 - Lang''' -  User's default language. Use ENG for English.
 +
 
 +
'''*f13 - Active''' - Sets the Active field in the USERID datatable. Should be Y for all new user imports.
 +
 
 +
'''f14 - Ext''' - Phone extension
  
−
'''Contact Attributes:''' Select any attributes that should be assigned to ALL contact records in the import file.  
+
'''f15 - DefScreen''' - Blank will default to 'CID Pulldown for Menu'.  In order to set a different screen default, it must be entered in the format 'do form sogrid' where you would replace the 'sogrid' part with the desired screen name.
  
−
'''Overwrite Duplicates''' Selecting this box will attempt to match import records to existing records using the contact full name and the organization Custno. Matched records will update the existing record with data from the import file.  Blank import file fields will not overwrite, or clear out existing data.
+
'''f16 - FaxUser''' - Fax UserID value
  
 +
'''f17 - FaxPass''' - Fax Password value
  
 +
'''f18 - FaxPress''' - Fax Press Name value
  
−
==Contact Import File Definitions==
+
'''*f19 - DMenu''' -  Default menu name. Must match exactly to a valid saved menu.  'Default' is the most common entry.
  
−
'''f1 - Custno''' - Adjutant Organization ID for the associated company record
+
'''f20 - SMTPserver''' - SMTP server name
  
−
'''f2 - FirstName''' - Contact first name
+
'''*f21 - ReqLet''' - Require letters in password. Enter Y or N.
  
−
'''f3 - MiddleName''' - Contact middle name or initial
+
'''*f22 - ReqNum''' - Require numbers in password. Enter Y or N.
  
−
'''f4 - LastName''' - Contact last name
+
'''*f23 - ReqOth''' - Require special characters in password. Enter Y or N.
  
−
'''f5 - Phone1Num''' - Primary phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+
'''*f24 - MaxLen''' - Maximum length for password. DO NOT LEAVE BLANK. The number entered must be equal to or higher than the entry in MinLen, otherwise there will be issues during password reset. If left blank, it will import zero and prevent any password entry over 0 characters.
  
−
'''f6 - Phone1Code''' - A two-digit code that defines the phone type. The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
+
'''*f25 - MinLen''' - Minimum length for password. For best practices, enter a value of 8 or higher.  
  
−
'''f7 - Phone2Num''' - Second phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+
'''f26 - Expin''' - Number of days for password to expire
  
−
'''f8 - Phone2Code''' - A two-digit code that defines the phone type. The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
+
'''*f27 - NeverExp''' - Enter Y to check the 'Never Expire' box. Enter N to expire password according to the 'Expire In' days.
  
−
'''f9 - Phone3Num''' - Third phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+
'''f28 - ReuseIn''' - Allow the same password to be reused in '''XX''' days
  
−
'''f10 - Phone3Code''' - A two-digit code that defines the phone type. The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
+
'''f29 - LoAfter''' - Lock the user out after '''##''' unsuccessful login attempts. DO NOT LEAVE BLANK. This entry must be greater than 0.  
  
−
'''f11 - Phone4Num''' - Fourth phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+
'''f30 - LoFor''' - If the user is locked out, lock them out for '''##''' minutes
  
−
'''f12 - Phone4Code''' - A two-digit code that defines the phone type.  The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
+
'''f31 - PasswordExpDate''' - Sets the manual password expiration date in the USERID datatable
  
−
'''f13 - Email1''' - Primary email address, typically the work address
+
'''*f32 - ActiveUser''' - Enter Y to set the 'Active User' flag. Enter N to leave the 'Active User' field blank.
  
−
'''f14 - Email2''' - Secondary email address. This is typically a personal email address or text messaging address.
+
'''*f33 - NoChange''' - Enter Y to set the 'User Cannot Change Password' flag. Enter N to leave it blank and allow password changes.
  
−
'''f15 - Job Title''' - Contact job title
+
'''*f34 - ForceChange''' - Enter Y to set the 'Change Password at Next Login' flag.  Enter N to leave it blank.
  
−
'''f16 - Address1a''' - Business street address (Address1 line)
+
'''f35 - SMTPuser''' - SMTP User ID
  
−
'''f17 - Address2a''' - Business suite or office number (Address2 line)
+
'''f36 - SMTPpassword''' - SMTP password
  
−
'''f18 - Address3a''' - Business additional address details (Address3 line)
+
'''f37 - SMTPdomain''' - SMTP domain
  
−
'''f19 - Citya''' - Business city
+
'''*f38 - ESMTP''' - Enter Y to set the ESMTP flag. Enter N to leave it blank.
  
−
'''f20 - Statea''' - Business two-character postal code
+
'''*f39 - DNUFlag''' - Enter Y to set the Desktop Named User flag.  Enter N to leave it blank.
  
−
'''f21 - Countrya''' - Business country code
+
'''*f40 - WNUFlag''' - Enter Y to set the Web Named User flag. Enter N to leave it blank.
  
−
'''f22 - Address1b''' - Home street address (Address1 line)
+
'''*f41 - TNUFlag''' - Enter Y to set the Terminal Named User flag. Enter N to leave it blank.
  
−
'''f23 - Address2b''' - Home suite or apartment number (Address2 line)
+
'''f42 - MimicID''' - Enter the CONTID value for the UserID that this record should mimic
  
−
'''f24 - Address3b''' - Home additional address details (Address3 line)
+
'''f43 - SMTPPort''' - SMTP port number
  
−
'''f25 - Cityb''' - Home city
+
'''f44 - TUserID''' - Terminal UserID for scanners
  
−
'''f26 - Stateb''' - Home two-character postal code
+
'''f45 - TuPassword''' - Desired password for scanners
  
−
'''f27 - ZipCodeb''' - Home zip code
+
'''f46 - DST''' - Enter Y to set the DST (Daylight Savings Time) flag.  Enter N to leave it blank.
  
−
'''f28 - Countryb''' - Home country code
+
'''f47 - GMTOff''' - Enter the number of hours to offset the user's system time based on GMT. Negative hours are allowed.
  
−
'''f29 - Salutation''' - Contact salutation, such as Mr., Mrs., or Dr.
+
'''*f48 - SMTPTLS''' - Enter Y to set the SMTP TLS flag. Enter N to leave it blank.
  
−
'''f30 - ZipCodea''' - Business zip code
+
'''*f49 - SMTPSSL''' - Enter Y to set the SMTP SSL flag. Enter N to leave it blank.
  
−
'''f31 - DefCont''' - Enter a 'Y' in this column to check the 'Default Contact' field. This will not update the contact name on the organization screen.  
+
'''f50 - SMTPAuth''' - Sets the SMTP Authorization type. Entry must exactly match one of the system-defined types. Most common entry is 'Default'. Other possible entries are 'None', 'Login', and 'Plain'.
  
  
  
−
==Contact Import Reconciliation==
+
==User Record Import Reconciliation==
  
 
Reconciling imported data should begin with spot-checking several records field-by-field for complete data import.  Pick records from the source file that have the most data columns filled in.  Verify that all source file data fields imported correctly and display as expected.
 
Reconciling imported data should begin with spot-checking several records field-by-field for complete data import.  Pick records from the source file that have the most data columns filled in.  Verify that all source file data fields imported correctly and display as expected.
  
−
Verify that all phone numbers and phone codes imported as expected. Spot-check several phone1 through phone4 records.
+
Verify that the following fields imported as expected by spot-checking the User In Adjutant Detail tab:
−
 
 
−
Verify that all records have the expected attributes assigned and that the attribute screens load as expected.
 
  
−
Manually update any attributes as needed.
+
*Default Screen
 +
*Default Menu
 +
*Mimic ID
 +
*SMTP Authorization
  
 +
Review the License Status screen and verify that the expected number of user licenses matches the value in the Actual column for each license type.
 +
all phone numbers and phone codes imported as expected. Spot-check several phone1 through phone4 records.
  
−
==Contact Import Additional Steps==
+
Test several passwords by logging in, or having imported users log in and verify that basic log in works as expected.
  
−
There are no additional steps needed to complete the Contact import.
 
  
 +
==User Record Import Additional Steps==
  
 +
The User Import process does not establish security tokens, unless imported users are mimics of a user with established security tokens. Set up desired security for each user by using Bulk Security Update or by setting up mimic users with security.
  
−
==Contact Import Database Tables==
+
'''ABIS-ONLY:''' For new clients, create a Contact Import file from the user data that can be imported into live ABIS. This contact import will build the contact names and email addresses for use with the support ticketing system.
  
−
Importing contact records can affect the following databases:
 
  
−
'''VCONTACT''' - Each imported user is assigned a unique CONTID value. This is the keyno. Each CONTID is linked to a CUSTID, which matches the ENTID keyno from the ENT table.
+
==User Record Import Database Tables==
  
−
'''USERID''' - Nothing gets automatically created in this table from the contact import, but if you edit and save the User in Adjutant screen, it will create a table entry.
+
Importing user records can affect the following databases:
  
−
'''RTRESOURCE''' - Similar to USERID, nothing gets automatically created in this table unless you edit and save the Resource screen.  
+
'''USERID''' - Each imported user is assigned a unique USERID value and a unique KEYNO. Each USERID is linked to a CONTID that matches the user's contact record.
  
−
'''PCXREF''' - Each attribute record will also create an entry in this table. The PTABLE value for all of these should be CONTACT, and the TYPE value should match the attribute name from Text1 of the associated attribute rule. The PARENTID and CHILDID values will correspond to CONTIDs from the VCONTACT table.   
+
'''PCXREF''' - Each imported user will create an entry in this table. The PTABLE value for all of these should be CONTACT, and the TYPE value should be USER. The PARENTID and CHILDID values will correspond to CONTIDs linked to the USERID.   
  
  
Line 169: Line 196:
  
 
[[Category: Address Book]]
 
[[Category: Address Book]]
−
[[Category: Conversion Guides]]
+
[[Category: Import Guides]]
 
[[Category: System Manager]]
 
[[Category: System Manager]]

Latest revision as of 15:54, 25 January 2023

General Data Import Notes

Refer to the Data Import General Information page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.


User Record Import Notes

The Import User screen creates the User in Adjutant attribute record, links it to the Contact ID, and can complete all of the required fields in the User Details tab and the User Password Settings tab. The import program can even establish user security mimics.


Timing and Preparation

User in Adjutant details and all of the appropriate named user license flags should be set up as soon as possible once the core system setup items have been completed. User licenses are generally billed from the very beginning of the implementation, so customers should be able to access the system as soon as it is available. Setting up user records immediately avoids a situation where customers are being billed for user licenses that they are unable to use.

All Address Book setup items should be completed prior to beginning the Contacts, Customer, and Vendor imports. The Address Book Setup Guide covers all of the Rule Maintenance records that should be completed prior to importing customer, vendor and contact records.

The User Import can be completed immediately after the employee contact records have been imported with the Import Contacts screen, or after they have been added manually. The internal contact records should be added prior to completing the Customer and Vendor imports. User records, resource records, salespersons, account managers, buyers, and project attributes should be established for employee records prior to importing the Organization records so that links to salespersons, account managers, and buyers can be made in the organization import files.


General Notes

Many of the fields on the Import User Records template are mandatory. Required fields are noted below in the file definitions section.

The Password Settings fields must be filled in on the import file. CID password setting defaults are not loaded during the import.


User Record Import File Data Scrubbing

Since nearly all of the data fields in the User Import file are Adjutant security specific fields, the customer will not have a source file to provide for this data. Generally, the only customer-supplied data for this file will be the userids, passwords, and email settings. In many cases the userids and passwords will be generated by ABIS personnel.

Because the data for this file is mostly generated by ABIS personnel to speed up the process of adding users, there is no customer data scrubbing required.


Import User Screen (IMPORTUSER)

Menu Location: Transaction>>Importers/Exporters>>Other>>Import User Records

IMPORTUSER.png


Import File Name/Browse: Use the Browse button to locate and select the completed User import template file (in XLS format)

Export Template: Generates a blank User Import template file

Map Fields: Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.

Validate to XLS File: Selecting this box will create an XLS errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.


User Record Import File Definitions

Required fields are indicated with *

*f1 - Contid - Contact ID (CONTID (keyno) of contact record)

f2 - Userid - Desired User ID. If left blank, the system will generate a UserID based of the contact name.

f3 - Password - Desired Password

f4 - Admin - Should the user be an Admin in Desktop (Y/N)

f5 - Defprinter - User's Default Printer ID

f6 - Termid - Scanner terminal ID

f7 - Freq - Scanner frequency setting

*f8 - Defloctid - Default Warehouse name. Enter the Warehouse name, not the LOCTID value.

*f9 - Defcid - Default CID name

f10 - DefLaser - Default Laser Printer name

f11 - DefLaserNo - Default Laser Printer ID

*f12 - Lang - User's default language. Use ENG for English.

*f13 - Active - Sets the Active field in the USERID datatable. Should be Y for all new user imports.

f14 - Ext - Phone extension

f15 - DefScreen - Blank will default to 'CID Pulldown for Menu'. In order to set a different screen default, it must be entered in the format 'do form sogrid' where you would replace the 'sogrid' part with the desired screen name.

f16 - FaxUser - Fax UserID value

f17 - FaxPass - Fax Password value

f18 - FaxPress - Fax Press Name value

*f19 - DMenu - Default menu name. Must match exactly to a valid saved menu. 'Default' is the most common entry.

f20 - SMTPserver - SMTP server name

*f21 - ReqLet - Require letters in password. Enter Y or N.

*f22 - ReqNum - Require numbers in password. Enter Y or N.

*f23 - ReqOth - Require special characters in password. Enter Y or N.

*f24 - MaxLen - Maximum length for password. DO NOT LEAVE BLANK. The number entered must be equal to or higher than the entry in MinLen, otherwise there will be issues during password reset. If left blank, it will import zero and prevent any password entry over 0 characters.

*f25 - MinLen - Minimum length for password. For best practices, enter a value of 8 or higher.

f26 - Expin - Number of days for password to expire

*f27 - NeverExp - Enter Y to check the 'Never Expire' box. Enter N to expire password according to the 'Expire In' days.

f28 - ReuseIn - Allow the same password to be reused in XX days

f29 - LoAfter - Lock the user out after ## unsuccessful login attempts. DO NOT LEAVE BLANK. This entry must be greater than 0.

f30 - LoFor - If the user is locked out, lock them out for ## minutes

f31 - PasswordExpDate - Sets the manual password expiration date in the USERID datatable

*f32 - ActiveUser - Enter Y to set the 'Active User' flag. Enter N to leave the 'Active User' field blank.

*f33 - NoChange - Enter Y to set the 'User Cannot Change Password' flag. Enter N to leave it blank and allow password changes.

*f34 - ForceChange - Enter Y to set the 'Change Password at Next Login' flag. Enter N to leave it blank.

f35 - SMTPuser - SMTP User ID

f36 - SMTPpassword - SMTP password

f37 - SMTPdomain - SMTP domain

*f38 - ESMTP - Enter Y to set the ESMTP flag. Enter N to leave it blank.

*f39 - DNUFlag - Enter Y to set the Desktop Named User flag. Enter N to leave it blank.

*f40 - WNUFlag - Enter Y to set the Web Named User flag. Enter N to leave it blank.

*f41 - TNUFlag - Enter Y to set the Terminal Named User flag. Enter N to leave it blank.

f42 - MimicID - Enter the CONTID value for the UserID that this record should mimic

f43 - SMTPPort - SMTP port number

f44 - TUserID - Terminal UserID for scanners

f45 - TuPassword - Desired password for scanners

f46 - DST - Enter Y to set the DST (Daylight Savings Time) flag. Enter N to leave it blank.

f47 - GMTOff - Enter the number of hours to offset the user's system time based on GMT. Negative hours are allowed.

*f48 - SMTPTLS - Enter Y to set the SMTP TLS flag. Enter N to leave it blank.

*f49 - SMTPSSL - Enter Y to set the SMTP SSL flag. Enter N to leave it blank.

f50 - SMTPAuth - Sets the SMTP Authorization type. Entry must exactly match one of the system-defined types. Most common entry is 'Default'. Other possible entries are 'None', 'Login', and 'Plain'.


User Record Import Reconciliation

Reconciling imported data should begin with spot-checking several records field-by-field for complete data import. Pick records from the source file that have the most data columns filled in. Verify that all source file data fields imported correctly and display as expected.

Verify that the following fields imported as expected by spot-checking the User In Adjutant Detail tab:

  • Default Screen
  • Default Menu
  • Mimic ID
  • SMTP Authorization

Review the License Status screen and verify that the expected number of user licenses matches the value in the Actual column for each license type. all phone numbers and phone codes imported as expected. Spot-check several phone1 through phone4 records.

Test several passwords by logging in, or having imported users log in and verify that basic log in works as expected.


User Record Import Additional Steps

The User Import process does not establish security tokens, unless imported users are mimics of a user with established security tokens. Set up desired security for each user by using Bulk Security Update or by setting up mimic users with security.

ABIS-ONLY: For new clients, create a Contact Import file from the user data that can be imported into live ABIS. This contact import will build the contact names and email addresses for use with the support ticketing system.


User Record Import Database Tables

Importing user records can affect the following databases:

USERID - Each imported user is assigned a unique USERID value and a unique KEYNO. Each USERID is linked to a CONTID that matches the user's contact record.

PCXREF - Each imported user will create an entry in this table. The PTABLE value for all of these should be CONTACT, and the TYPE value should be USER. The PARENTID and CHILDID values will correspond to CONTIDs linked to the USERID.

Retrieved from "http://www.abiscorp.com/faq/index.php?title=User_Record_Import_Guide&oldid=4555"