Always mandatory fields
There are a few person information fields that are required by Nepton service and are always needed to have present values and values for the entire history and future. If there is one value, its validity cannot have a start date and the validity cannot end. If there are multiple values for different times, the first value cannot have a start date, for all validity periods defined there must be a value and the last value cannot end.
The always mandatory fields for Nepton are:
- Last name
- First name
- User account enabled
- Service usage language
When adding a new person via person form, the username will get a default value based on the first name and last name of the person. It can be changed before saving. Also the user account is always enabled at first when adding a new person. For existing person the password can be changed and the user account can be disabled via Additional functions tab under Person's information. If values are missing for any other of the mandatory fields, an error message is displayed when trying to save the person.
For person import only the Last name and First name fields are mandatory when importing - other always mandatory fields will get default values in person import if not provided. These default values in person import are:
A unique username of is generated based on the first and last name with possibly numeric digits added to the username. The resulting username is no more than 22 characters in length.
Employee by default
A random password is generated for a new person. In order to login the person must have an e-mail address stored and use the Forgot password link in the login page.
- User account enabled:
Enabled by default.
- Service usage language:
The default language of the working community.
If values for first or last name are missing at least for some time in history, present or future, the person cannot be imported at all.
Mandatory fields entered as persons additional fields
When persons additional fields are added via Administration of Employees (see Manage persons additional fields), the fields can be marked as mandatory for all or some of the person roles. If the person has a role that requires a certain field to be present, it must have present values and values for the entire history and future when entered via Person form, just like for Always mandatory fields.
In person import the mandatory persons additional fields are also expected to have present values and values for entire history and future. However, if values for persons mandatory additional fields are missing in person import fields, the person details can be imported despite the missing information and a warning is displayed for manual import or for automated person imports a warning message is produced in the service log.