Skip to content

Resources

Workplaces, people and named values for the reporting side — Administration > Requirements > Resources.

This page described something else until 2026-08

It listed module management (switching modules on and off), system-wide defaults and physical quantities. None of that belongs to AdminResourceController. Modules cannot be switched via resources; defaults live in General settings, physical quantities in Requirements. What the menu entry actually manages is described here.


One table, three uses

The resource table comes from V1 and serves three unrelated purposes. That is historical, and worth knowing when maintaining it: a row reads quite differently depending on which purpose it serves.

1. Workplaces and people

name, type and working_hours describe a calibration bench, a climate chamber or a person — for example "Kalibrierplatz Elektrik", type "Arbeitsplatz", working hours "Mo-Fr 07:00-16:00".

Documentation, not scheduling

working_hours is free text and is evaluated by no program logic — neither in V1 nor in V2. There is no booking calendar deriving appointments from it. Anyone who needs one has to build it; this column is not a basis for it.

2. Environmental conditions for the calibration certificate

environment_resources carries the target range printed on the certificate. Format: temperature, vertical bar, humidity.

21,0 ... 23,0 °C|40 ... 60 %

The row is found by its name: the report variable environmental_conditions holds the name of the resource the value is pulled from. Renaming breaks that link without any complaint — the certificate then simply prints nothing in that place.

Target range, not a limit

The value is printed, not checked. The actually measured values live on the calibration (temperature, humidity, pressure) and are captured optionally during the procedure preflight. Nobody compares target against actual; there is no limit monitoring, no history and no alarm. Anyone needing lab monitoring needs a module V2 does not have.

No pressure: the format knows only the two values.

3. Report layout variant

report_template is a switch. If it holds 1, the report picks its alternative layout variant; any other value leaves it at the default. Again the row is addressed by name, this time from the report variable reportVariantCode.

Fields

Field Meaning
name Display name and address — the reporting side looks the row up by it
type Free classification, e.g. workplace, person, environment
working_hours Free-text working hours, purely documentary
environment_resources Target range for the certificate, temperature\|humidity
report_template 1 switches the alternative layout variant
user_uID Assigned user, carried over from V1, without effect
enabled Row active

Permissions

Its own triad rather than the broad basic_setting_admin:

Operation Allows
resource_view seeing resources
resource_edit creating and changing
resource_delete deleting

Without resource_view the tab hides itself; the other requirement tabs stay reachable.

  • Requirements — test standards, SI prefixes, physical quantities, quality provisions
  • Master reports — where the report variables are maintained