We have the opportunity to create custom fields on client level for the employee card either in the “General” tab, “Contracts” tab or on the card for “End of employment”.
These can be seen as a Parent which can have fields dependent on them or simply stand alone.
Types
Yes / No
Number
Text
Date
Select box
Multiple choice
We have a strict name validation for custom fields to avoid duplicate names for same type field. This includes case insensitive. This means that names like "FieldName" and "fieldname" is considered identical and not allowed as separate fields.
Note: we only support the type of “Select box” on the card for “End of employment”.
Within the options “Select box” and “Multiple choice” we have the option to:
Drag-and-drop values
Ordering of values within the drop-down within the User card
Delete specific values
Deletion of value will remove it from all existing employee cards if selected
Make value inactive
Making a value inactive will mean that it will stay for employees if previously selected. However, it will no longer appear within the drop-down and therefor not be possible to select.
Edit value
If editing a value we will ensure the value is updated to be correct on employee cards if previously selected. It will also be updated within the drop-down.
Note: it is not possible to edit a value if used as trigger value on a child field.
Remove field as trigger on child field → edit value → add as trigger on child field
Field levels
Parent:
A standard custom field that will equal level 1 in a hierarchy. This can be placed in either the “General” or the “Contracts” tab in the employee card.
Child:
This custom field will be dependent on a Parent field and will equal level 2 in a hierarchy. A child will have to follow the Parent field tab placement in the employee card.
Grandchild:
This custom field will be dependent on a Child field and will equal level 3 in a hierarchy. A grandchild field will have to follow Parent and Child field tab placement in the employee card.
Note:
We have no level restrictions for setups with dependencies.
Settings
Only for Admin and Required Logic: If logged in as a level below Administrator, but with access to “General” and “Contracts” tab, this custom field setup will be overlooked within employee creation / update. If logged in as the level of Administrator this custom field setup will be required and action button inactive for current tab until given required fields are given a value. For example, if a required field such as ID '9305' is missing, an error will occur during contract creation. This field is only visible and editable to users with Administrator roles, emphasizing the importance of Administrator access for completing such setups.
So, it can be described as situational required. If we did not do this then we would block all users with "full access" to "General" and "Contracts" permissions, but without providing any reason and any way to remove the blocker (as the field would be hidden) - meaning that they would be able to go through the entire flow but never would be able to complete it. Note: If Parent field is set as Only for Admin this will determine settings for depending fields (child and grandchild) For instance, if an Administrator does not complete a required field in a previous contract, it can block the creation of new contracts for the same employee. This highlights the cascading impact of missing data in admin-only fields.
Required
Logic:
If logged in as a user with access to “General” and “Contracts” tab, no matter level, this custom field will require to be given a value or else the action button will be inactive at employee creation / update for current tab.
Only for Admin Logic: If logged in as a level below Administrator, but with access to “General” and “Contracts” tab, this custom field setup will be overlooked within employee creation / update. This custom field will only show for the Administrator title, but will not affect the action button if not given a value.
For example, field ID '9305' is a required field visible only to Administrators. If this field is not completed, it can lead to errors during contract creation, underscoring the necessity of Administrator involvement in such cases. Note: If Parent field is set as Only for Admin this will determine settings for depending fields (child and grandchild)
Title selection
Logic:
Title selection is available if the custom field is placed in the “Contracts” tab of the employee card. This will ensure that the custom field will only appear on titles for selected title(s).