Creating your own fields


In some cases, you may need different or additional fields to those provided by your AXM Classic. Additional fields for person properties are also exported in the GDPR report (see Exporting the data protection report (GDPR)).
For this reason, you can also create your own fields (see Subsequently modified user-defined fields for more information on the properties of your own fields):
- AXM Classic open.
- Identification medium available.
- Click on the orange AXM icon
.
- AXM bar opens.
- Select the entry in the group.
- The AXM bar will close.
- The window with identification media opens.
- Click on any identification medium.
- The identification medium window will open.
- Click on the tab.
- Window switches to the tab.
- Click on the
configuration button.
- The window will open.
- Click on the button.
- The window will open.
- Enter the name of your user-defined field in the field (example: office no.).
- This name will be displayed in front of the input field later.
- If an entry in your field needs to be mandatory: activate the check box (example: office no. is not mandatory – not every employee has an office with a number).
- If an entry in your field must not be reused for the same field for another person: activate the check box (example: office no. is not clear – a number of employees work in the same office – therefore do not activate the check box).
- Click on the button.
- window closes.
- Your new user-defined field is now listed.
- Click on the button.
- window closes.
- The identification medium window displays your new user-defined field in the tab (example: The office no. field is displayed).
- Click on the button.
- Your new user-defined field is available in all locking systems belonging to the same project.
NOTE
AXM Classic’s behaviour with user-defined fields created or modified at a later date
User-defined fields can be created at any time and changed at a later date. Example: you create a required field even though some people already exist in the locking system.
This results in this newly created required field being empty for existing persons, even though it is marked as
.- Find out how AXM Classic responds in such cases (see Subsequently modified user-defined fields).