Every object in Log+Key has the same basic fields: object name, description, type, location, storage location, linked tag and photos. Anything else your organisation wants to record goes into custom fields — for example the contract number of a home emergency call subscriber, a cost centre or the locking system a key belongs to. This page shows how you get custom fields and where they appear.
Two field types
- Free text — for values that differ from object to object: contract numbers, inventory numbers, cost centres.
- Selection — for a fixed list of values to pick from when creating or editing an object: locking systems, building sections, vehicle classes. A selection keeps the spelling consistent — a free-text “Locking system” quickly ends up with “SA Nord 04”, “SA-Nord04” and “Nord 4” side by side.
Fields for certain types
A custom field can apply to all objects or only to certain types: keys get a locking system, tools a serial number, vehicle keys a registration plate. When requesting a field, say which types it should apply to – it then appears only on objects of those types. The assignment is currently done by Log+Key; managing the fields yourself is planned for a later release.
How to get custom fields
Log+Key sets up custom fields for your organisation; you don’t create them in the web app yourself. Send your contact person or hallo@log-key.de the following for each field:
- the name as it should appear in the form (for example “Vertragsnummer”),
- the type — free text or selection,
- for a selection, the values (for example “SA-Nord 04” and “SA-Süd 02”),
- optionally the types the field should apply to.
The fields are then available on every object. Existing objects stay empty until you fill in the values while editing.
Where the fields appear
In the object form — when creating as well as when editing — the custom fields sit below Linked tag: free text as an input field, a selection as a list. They are not mandatory. Roles with the permission Edit Custom Fields can also adjust custom fields during take-out and return, if the field is set up for that.
On an object’s detail page, the filled-in fields appear with their value below the basic data.
In the object list, every custom field gets a column at the right-hand end of the table. The search above the list also matches values of custom fields — “SA-Nord” shows every key of that locking system. The filter, by contrast, only knows status, location and type.
Which columns you see is up to you via View → Columns: tick or untick, then Save. The selection is remembered. Hide Description, Taken by and Storage location, for example, and Schließanlage and Vertragsnummer move into view.
Screencast: custom fields “Schließanlage” and “Vertragsnummer” on the detail page and in the edit form, then searching “SA-Nord” finds all matching objects
Tips
- Keep the number of fields small. Every field is a column in the list and a question when creating an object.
- Use a selection whenever the possible values are known in advance, and free text only for numbers and identifiers.
- Values that live in the description today — contract numbers, say — belong in a custom field: then they are a sortable column instead of running text.