This page (revision-33) was last changed on 26-Nov-2021 10:22 by Meg McFarland

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
33 26-Nov-2021 10:22 7 KB Meg McFarland to previous
32 26-Nov-2021 10:22 7 KB Meg McFarland to previous | to last
31 26-Nov-2021 10:22 7 KB Meg McFarland to previous | to last
30 26-Nov-2021 10:22 7 KB Meg McFarland to previous | to last
29 26-Nov-2021 10:22 7 KB Meg McFarland to previous | to last
28 26-Nov-2021 10:22 7 KB Meg McFarland to previous | to last
27 26-Nov-2021 10:22 7 KB Karen Parrott to previous | to last
26 26-Nov-2021 10:22 7 KB kparrott to previous | to last
25 26-Nov-2021 10:22 7 KB kparrott to previous | to last
24 26-Nov-2021 10:22 7 KB kparrott to previous | to last
23 26-Nov-2021 10:22 7 KB kparrott to previous | to last
22 26-Nov-2021 10:22 7 KB kparrott to previous | to last
21 26-Nov-2021 10:22 6 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
IEID
IEID

Version management

Difference between version and

At line 1 removed one line
[{TableOfContents }]
At line 3 removed one line
The Maintain Identity Information (IEID) form holds an employee's non date-sensitive information that is used to uniquely identify them in the organization and to the government (i.e. gender, birth date, legal name and identification).
At line 3 added 4 lines
[{TableOfContents }]
The Maintain Identity Information (IEID) form holds an employee's non date-sensitive information that is used to uniquely identify them in the organization and to the government (i.e. gender, birth date, legal name and identification).\\
At line 19 changed one line
;[Person Code|PERSON_CODE]:This field holds the unique code or number assigned to this employee by the organization (i.e. employee number, personal ID number, badge number). This code may be auto-generated by the system when the employee is added, in addition, it may be changed with no loss of information or integrity. Person_Code is assigned on the IEHR form.
;[Person Code|PERSON_CODE]:This field holds the unique code or number assigned to an employee by the organization, such as employee number, personal ID number, badge number. This code can be auto-generated by the system when an employee is added, and it can be changed with no loss of information or integrity. Person_Code is assigned on the IEHR form.
At line 21 changed one line
;[Gov’t Code Origin|GOVT_CODE_ORIGIN]:This field indicates the country associated with the government code provided. Setting this variable to USA or Canada will result in the government code being formatted accordingly (999-99-9999 for the USA and 999-999-999 for Canada)
;[Gov’t Code Origin|GOVT_CODE_ORIGIN]:This field defines the country associated with the government code provided. Setting this variable to USA or Canada will result in the government code being formatted accordingly (999-99-9999 for the USA and 999-999-999 for Canada)
At line 23 changed one line
;[SSN|GOVERNMENT_CODE]: U.S.A.: This field displays the employee’s Social Security Number (SSN). Canada: This field displays the employee’s Social Insurance Number (SIN).
;[SSN|GOVERNMENT_CODE]: For USA installations: This field displays the employee’s Social Security Number (SSN). For Canadian installations: This field displays the employee’s Social Insurance Number (SIN).
At line 27 changed one line
;[Salutation|SALUTATION]:This field uses the usual forms of address (i.e. Ms, Mr., Dr, etc.).
;[Salutation|SALUTATION]:This field defines the usual forms of address, such as Ms, Mr., Dr, etc.
At line 33 changed one line
;[Last Name|LAST_NAME]:This is the legal surname of the employee, as specified on their SSN/SIN card.
;[Last Name|LAST_NAME]:This is the legal surname of the employee, as documented on their SSN/SIN card.
At line 35 changed one line
;[Rank|RANK]:This field shows any name extension (i.e. Jr., Sr., III etc.) the employee may have.
;[Rank|RANK]:This field shows any name extension, such as Jr., Sr., III etc. the employee may have.
At line 37 changed one line
;[Drivers License|DRIVERS_LICENSE]:This field holds the employee’s driver’s license number.
;[Drivers License|DRIVERS_LICENSE]:This field displayed the employee’s driver’s license number.
At line 42 changed one line
;[Age]:This field shows the age of the employee in years. Age is calculated by by the system and cannot be updated.
;[Age]:This field shows the age of the employee in years. Age is calculated by the system and cannot be updated.
At line 46 changed one line
;[Gender|GENDER]:This field indicates whether the employee is male or female. The value is entered on the IEHR form, but may be changed.
;[Gender|GENDER]:This field indicates whether the employee is male or female. The value is entered on the IEHR form, but can be changed.
At line 52 added 2 lines
;[CDN Ethnicity|CDN_ETHNICITY]: This field displays the employee's Canadian Ethnicity, as defined in a lexicon list.
At line 52 changed one line
;[US Ethnicity|US_ETHNIC]: This field displays the employee's US Ethnicity as defined in a lexicon list.
;[US Ethnicity|US_ETHNIC]: This field displays the employee's US Ethnicity, as defined in a lexicon list.
At line 60 changed one line
;[User Profile|USER_NAME]:This is a user name that the employee is assigned, for access to Self Service modules.
;[Initialize Access to Self Service]: A Self Service Accessor record can be set up by clicking on this button. \\
At line 62 changed 2 lines
;[Person Code|PERSON_CODE] / [First Name|FIRST_NAME] /[Last Name|LAST_NAME]:
These fields identify the employee by their employee number and name.
%%information NOTE: It is imperative that before the accessor record is defined, the employee MUST be set up with an email address on their work assignment record (IEAS). If no email address is defined on the IEAS form, the system sends the Access Key to the personal email address defined on the IEPI form. If no email is defined, the Access Key remains unset.%%\\ \\
If the employee’s access record is manually created through the IEID form, the employee will NOT automatically receive their password. Instead, once the employee’s password information is generated, the information must be manually emailed to the employee.\\ \\
At line 65 changed one line
;[Current Email|DRV_EMAIL_ADDRESS]:The employee’s email address will be displayed in this field.
If LDAP is ON, when the Initialize Accessor for Self Service is clicked, the password will not be set nor will an email be sent to the employee.
At line 67 changed 8 lines
;[PIN Changed By|PIN_NUMBER]:This field displays the employee or user who changed the PIN. PIN_Number_Changed_By is system updated.
;[PIN Changed On|PIN_NUMBER_CHANGED_DATE]:This date is the last time the employee changed their PIN. PIN_Number_Changed_Date is system updated.
;[Access Key|ACCESSOR_KEY]:This field provides an alternative method for logging into Self Service if the system is so configured. The value in this field will be the key value (AKA user name) used in the login screen instead of the person code and last name.
;[Access Start|ACCESS_START_DATE] / [End Date|ACCESS_END_DATE]:These dates indicate the time frame for which the employee has access.
;[User Profile|USER_NAME]:Displays the user profile, such as EE_SS, that is assigned to the employee(s).
;[Current Email|DRV_EMAIL_ADDRESS]:The employee’s email address is displayed in this field.
;[Access Key|ACCESSOR_KEY]:This field provides an alternative method for logging into Self Service if the system, if configured. The value in this field will be the key value, such as a user name, used to login instead of a person code and last name.
;[Domain]:
;[Access Start|ACCESS_START_DATE] / [End Date|ACCESS_END_DATE]:These dates define the time frame the employee has access to Self Service.
;[Force Password Change on Next Login|FORCE_PASSWORD_CHANGE]:If this toggle is set to ON, the employee must change their password the next time they login.
At line 76 changed 9 lines
;[Logins To Date|LOGINS_TO_DATE]:This field indicates the number of logins the employee has made.
;[Force Password Change on Next Login|FORCE_PASSWORD_CHANGE]:If this toggle is on, the employee must change their password when they next log on.
;[Set/Reset Password|ACT_RESET_PASSWORD]:This button allows you to reset an employer’s password.
;[Reactive|ACT_SET_ACTIVE]:If the employee has lost access to the system, this button allows you to reactivate their account.
;[Logins To Date|LOGINS_TO_DATE]:This field displays the number of logins the employee has made.
;[Set/Reset Password|ACT_RESET_PASSWORD]:This button allows users to reset an employee’s password.
;[Clear Password]:
;[Reactivate|ACT_SET_ACTIVE]:If an employee has lost access to the system, this button allows users to reactivate their account.
At line 86 changed 3 lines
;[Failed Attempts|FAILED_ATTEMPTS]:The number of failed login attempts the employee has made is recorded here.
;[Failed Attempts|FAILED_ATTEMPTS]:Displays the number of failed login attempts the employee has made.
At line 95 changed one line
This is used by UEMAIL, it tracks all the emails and their attachments sent to an employee using this facility. It can also be used by clients to manually key in things they want to track/log with or without attachments.
This tab is used by the UEMAIL function and tracks all the emails and any attachments sent to an employee using this facility. It can also be used by organizations to manually enter items they want to track/log with or without attachments.
At line 97 changed one line
;[Date/Time|CREATE_DATE]:This is the date/time that this record was created, either from an email that was sent using the UEMAIL function or from a record that manually keyed by the user.
;[Date/Time|CREATE_DATE]:This is the date/time that this record was created, either from an email that was sent using the UEMAIL function or from a record that was manually entered by the user.
At line 101 changed one line
;[Category|LOG_CATEGORY]: This is a user-defined field that uniquely identifies the category to which the log record belongs. This field is for information purposes only and has no functionality behind it. There is only one supplied option (Not Specified) to select from; however, users can create new lexicon values accordingly.
;[Log Category|LOG_CATEGORY]: This is a user-defined field that uniquely identifies the category the log record belongs to. This field is for information purposes only and has no functionality behind it. There is only one supplied option (Not Specified) to select from, however, users can create new lexicon values if required.
;[Entered For]:
;[Description]:The description of the record being added. If this is a record from the UEMAIL, this field will be the from the ‘Subject’ line of the email or was manually keyed by the user.
At line 103 removed one line
;[Current Email|DRV_EMAIL_ADDRESS]:The employee’s email address will be displayed in this field.
At line 105 removed 2 lines
;[Description]:The description of the record being added. If this is a record from the UEMAIL, this field will be the from the ‘Subject’ line of the email.
;[Log Text]:This field is a text field and if the record is from the UEMAIL, this field will be the ‘body’ of the email.
At line 108 changed 4 lines
;[Date/Time|CREATE_DATE]:This is the date/time that this attachment was added to this record from an email that was sent using the UEMAIL function or from a record that manually keyed by the user.
;[Attachment]: This field holds the name of the file that is to be attached to the log record.
;[Description]: This field is a more descriptive text that describes the attachment file.
%%
__Attachments Section__\\
;[Create Date]:
;Attachment: This field holds the name of the file that is attached to the log record.
;[Description]: This text field describes the attachment file.
At line 113 removed one line
\\
This page (revision-33) was last changed on 26-Nov-2021 10:22 by Meg McFarlandTop