logo
1
Ideas

Query forms: persist the cross-installation search checkbox per user

Query forms: persist the cross-installation search checkbox per user Customer feedback from training: the Anlagen- und Gebaeude-uebergreifend suchen checkbox at the top of the query forms (Keys, Cylinders, Copies, Issues, History) resets to unchecked every time the form opens. The five query types share one form (_frmSucheErsetzen with fArt switch) and one checkbox (chb_FA_Master). The state is read at search time but never written to or read from CUSTOMIZE. Add per-user persistence so customers who routinely work across all installations can default the checkbox to on, mirroring the US_LastRessource_OBJ_ID pattern already used in the same form.

1
Ideas

CAD plan: colour-code cylinders by installation

CAD plan: colour-code cylinders by installation Customer feedback from training: when two installations share a CAD plan, operators cannot visually tell installation G cylinders from installation H cylinders. The CAD viewer renders markers from imported DXF/DWG layer colour; no code path varies cylinder marker colour by Anlage_ID. Add an installation-level colour assignment that drives marker rendering on the plan.

1
Ideas

Buildings: surface the existing many-to-many relationship to installations in the UI

Buildings: surface the existing many-to-many relationship to installations in the UI Customer feedback from training: customers want to associate one physical building with multiple installations. The data model already supports this via the RE_ANLAGE_GEBAEUDE join table, but the building form does not offer a clear path to add a building to a second installation, and the derived getAnlagenliste() reads from the cylinders that live in the building (group by Anlage_ID on ZYLINDER) rather than from the join table. Expose the M:N relationship in the building form so operators can attach one building to multiple installations directly.

1
Ideas

Audit log: in-app browser for user actions

Vision records key movements and deletions, but it does not yet keep a field-level record of who changed what and when. This covers building that record and a screen to query it: filters by operator, date, entity and action, with an export for auditors.

1
Ideas

Reminder report: operator-triggered actions on selected rows

Reminder report: operator-triggered actions on selected rows Customer feedback from training: the Reminder form shows upcoming key return deadlines and end-of-activity dates but is read-only. Operators want to act on selected rows directly from the grid: send a one-off reminder email to a specific key holder, log a contact attempt, or mark a follow-up. Distinct from the automated scheduled-reminder engine in progress; this ticket covers manual operator-triggered actions on the form itself.

1
Ideas

Reminder report: keep persons with outstanding keys regardless of end-of-activity window

Reminder report: keep persons with outstanding keys regardless of end-of-activity window Customer feedback from training: the Reminder grid filter is a window of (Today minus 100 days, Today plus nTage), so a person whose EndeDatum is more than 100 days in the past drops out of the report even if they still hold outstanding issued Exemplare. The report should keep persons visible for as long as they hold outstanding keys, independent of the date window on EndeDatum.

1
Ideas

Personnel and key assignment CSV export

Export personnel records together with the keys they hold, to a CSV that HR and ERP systems can read directly. Vision has no export of this kind today. What the receiving system expects decides the column set, so that is the part worth scoping before anything is built.

1
In progress

Scheduled tasks and service status panel in Companion

Scheduled tasks and service status panel in Companion A new always-on background service runs scheduled jobs (reminders, exports, sync) without manual triggering. Companion gets a task management page where operators can create, configure, pause and inspect scheduled tasks. A status panel shows service health, last run, next run and recent errors at a glance.

1
In progress

Supervisor field on personnel records with reminder CC

Supervisor field on personnel records with reminder CC A supervisor field on the personnel record links each key holder to a responsible manager. Outstanding-key reminders can be sent with the supervisor on copy, so escalation is built into the standard process. The field is editable manually and stays in step with the directory source when automated personnel sync is in use.

1
In progress

Automated email reminders for outstanding keys

Automated email reminders for outstanding keys Configurable email reminders sent automatically when a key has not been returned by its due date. Each reminder records its target, schedule and body. Built-in retry, rate-limiting and dry-run mode let operators preview the full reminder list before the first real send. Replaces manual chase work for departed employees and overdue assignments.