-
Select
.
-
Click Find to search for the employee. To perform an advanced search, click
the down arrow next to the Find button.
-
After you find the employee, click Edit next to the employee.
-
Navigate to the section.
These fields are displayed:
- Value
- Employee-specific data value that is related to
the UDF Name
field. For example, if you create a UDF employee data field named City, then
the Value field
is the specific city of each employee’s address, such as Toronto or Atlanta.
- Last Updated
- Date when the Value field was last updated.
- UDF Name
- You cannot make changes to these fields. This
field provides the name of the employee data field and describes what
employee information the field captures. For example, the employee’s
driver’s license number could be captured in a field with a UDF Name value of DRIVER
LICENSE.
For any information that cannot be placed in the
existing data locations, you can add an unlimited number of employee data
fields. Consider carefully when deciding how much employee information to
store in the system. Some data is required to properly interpret and
calculate the organization’s payroll rules. Other data is important
because the data provides useful information to supervisors and managers,
although the data does not directly affect payroll.
Employee data fields are not date-effective in the same
way employee detail attributes are (including the available user-defined
fields). Generally, relatively static information is stored in these
fields.
During this phase of an installation, you should consult with relevant
parties in the organization to be sure that all possible data fields are
considered. At minimum, you should contact your payroll administrator, HR
manager, and employee supervisors to determine which data fields are required
for their departments and job functions.
When determining the data that should be stored, remember that this data
may exist in other systems and can be interfaced automatically so that the data is
available to application users. Thus, you should determine what information is suitable
and helpful for application users without concern for where the information is
maintained. Also, not all the data that is stored in an external system is necessarily
required in a Workforce Management system. Only data elements that are required
by the system itself should be defined within the system.