FSM Employee Model Reference
This reference is intended for administrators and developers who work with Employee model mappings and defaults.
This model represents employee. Standard mappings cover employee names and email, FSM labor cost, inventory location, work calendar, region, skills, coordinates, and FSM Mobile fields. The subsidiary mapping is present when Subsidiaries is enabled. The inventory mapping is custentity_nx_location, work calendar is custentity_nx_work_calendar, and skills are mapped as a multiselect through custentity_nx_skill[]. The prototype.defaults property is empty.
Standard default structure (JSON fragment):
{
"models/employee": {
"prototype": {
"record": "employee",
"map": {
"firstname": "firstname",
"middlename": "middlename",
"lastname": "lastname",
"email": "email",
"cost": "custentity_nx_labor_cost",
"password": "custentity_nx_password",
"newpassword": "|password",
"giveaccess": "giveaccess",
"mobileuser": "custentity_nx_mobile_user",
"inventory": "custentity_nx_location",
"workcalendar": "custentity_nx_work_calendar",
"region": "custentity_nx_region",
"skill": "custentity_nx_skill[]",
"latitude": "custentity_nx_latitude",
"longitude": "custentity_nx_longitude",
"id": "internalid"
},
"defaults": {}
}
}
}
The prototype.map.subsidiary mapping is "subsidiary" when Subsidiaries is enabled. It is omitted from this fixed-value fragment.
The prototype.map.inventory mapping connects the Employee inventory-location attribute to custentity_nx_location. It identifies the Employee field containing that location. The location value is set on the Employee record. Retain this mapping when using the standard FSM inventory-location field. It is separate from the Transaction prototype.inventory setting, which selects a line collection for bin, serial, and lot assignment conversion.
The model is used by Employee FSM Mobile-login notifications and account FSM Mobile-user lookup. Its FSM Mobile link includes the Employee email. Authentication and access fields are part of those product operations. These fields are not a recipe for bypassing access controls or moving credentials to another field.
Use FSM Mobile user-resource configuration to change which supporting resources an employee receives. Schedule Board employee selection and mapping have their own definition. Neither is configured by adding filters or resources to models/employee.