Rules¶
Under Administration > Basic settings > Rules (/v2/admin/settings, "Rules" tab), the system rules taken over from calServer V1 are managed. The values live — as in V1 — as properties under settings/calibration (or settings/customer) and are carried over unchanged by the V1→V2 migration.
Due-date and traffic-light rules¶
| Rule | Effect | Default |
|---|---|---|
Due date period (due_date_period) |
Lead time in days from which a calibration counts as "due" (dashboard statistics) | -30 |
Critical level 1 (critical_date_period_1) |
First warning level of the due-date traffic light | -14 |
Critical level 2 (critical_date_period_2) |
Second warning level | -7 |
Critical level 3 (critical_date_period_3) |
Third level — already overdue here | 7 |
Signs: the boundary is always today - period. A negative value
therefore counts into the future (early warning: -14 = 14 days ahead of the
date), a positive one into the past (7 = up to 7 days overdue). 0
switches the bucket off — its tile then counts nothing.
The shipped defaults form a ladder that narrows as the date approaches and ends
with an overdue level: "due" 30 days ahead, then 14, then 7 days ahead, then 7
days overdue. Existing installations whose four values still matched the old
defaults (60 / -60 / -14 / -7) were moved to the new ladder by a migration;
customised values are left untouched.
Field assignments¶
Moved (ADR-031)
Field assignments (status field, type field, display fields), the customer search and the global counters left this tab with ADR-031 and have been under Requirements, tab "Feldvorgaben", since 2026-08-17 (field management was the intermediate stop). The field registry is available there, so an assignment is picked instead of typed. Storage is unchanged — settings/calibration and settings/customer as before; only the place to edit them has moved.
Status field, additional status field, type field, certificate field, customer e-mail field and customer search fields define which registry fields the respective system function uses.
Barcode¶
Barcode type (DataMatrix, QR, Code 128/39 or disabled) and the source field whose value is encoded. The label layout and height are not settings: both live in the label report template, and the print dialog takes the size from the generated PDF.
Number ranges (counters)¶
Edited under Requirements, tab "Feldvorgaben" — see the note above.
- Global counters are the global number ranges; default-value templates (e.g.
[GLOBAL_COUNTER_1],[GLOBAL_COUNTER_2], …) increment them atomically. Four counters are available by default; use Add counter / Remove last counter to adjust how many. Removing is non-destructive — the stored counter value is kept and a[GLOBAL_COUNTER_N]token keeps working even when the counter is hidden from the UI. - Automatic reset: per counter, a reset can be enabled daily, weekly (Monday), monthly (1st) or yearly (Jan 1st). The nightly run
php artisan counters:reset(scheduler, 00:00 — V1:yiic resetCounter) resets due counters to 0.
Security rules¶
| Rule | Effect in V2 |
|---|---|
Prevent duplicate asset numbers (disable_double_asset_number) |
Creating/updating with an existing asset number is rejected |
Prevent duplicate order numbers (disable_double_booking_number) |
Creating with an existing order number is rejected |
Warn about open orders (enable_user_opens_order) |
When creating an order, a warning is shown if the customer already has orders in an active status (order numbers included in the warning) |
Documents¶
| Rule | Effect in V2 | Default |
|---|---|---|
Badge in DMS file view (enable_badge_dms_view) |
Shows/hides the release-status badge (released/draft) in document views | on |
Show empty documents (show_empty_doc) |
Shows document areas even when no file is attached | on |
What "Show empty documents" does. The document view groups a record's files by DMS category (the folders from file management). Switched on, every category gets its own area, empty ones included — they show "Keine Dateien" plus the upload button. Switched off, the view lists only categories that hold a file; if none does, it says "Keine Dokumente vorhanden".
That is the same decision calServer V1 makes in its document tab. One difference remains: in V2 the upload hangs off the area. So the path into a still-empty category does not disappear, the view offers users with write permission a control at the end of the list that pulls the hidden empty categories back in.
The rule covers documents, not device images — those live in their own area in
V2 as in V1 (_img categories).
Rules removed from V2¶
Six rules sat in this tab without calServer V2 ever reading them. A switch that
does nothing costs more explanation than it is worth, so they were removed from
the V2 UI. The values stay in property: an installation still running V1
alongside reads them unchanged and maintains them in the V1 UI.
| Removed setting | What V1 does with it | What applies in V2 instead |
|---|---|---|
Label print format (barcode_field_print) |
Label layout (TEXT:BARCODE:FIELD) |
The layout lives in the label report template |
Label height (barcode_label_height) |
Label height in millimetres | The template sets the label size; the print dialog takes it from the PDF |
Enable local user accounts (enable_local_user_accounts) |
Login with intranet service accounts from the server configuration | V2 authenticates only against database user accounts and API tokens |
Fixed table headers (enable_fixed_grid_header) |
Turns on the fixed header of the V1 grids | V2 grids keep the header row and the action column pinned by construction |
Order tabs (pic_doc_code) |
Order of the extra tabs in the inventory view (picture, documents, barcode) | The V2 detail page derives its tabs from modules and permissions |
Download folder (download_folder) |
System-wide suggestion on download | Standard download folder in the user profile (/v2/settings/profile), so per user |
Still V1-only, but elsewhere: the file store paths and, under Requirements, the field assignments that address V1 codes (status field, type field, certificate field — V2 addresses calibration fields by their api_name).
Permissions¶
The tab and its endpoints (/admin/properties) require the basic_setting_admin operation.