Changelog
Every release with new features, improvements, fixes and – where applicable – changes that require action.
1.3.0
StableAdded
- From this version on, releases are no longer marked as a beta.
- The catalogs have a proper edit dialog: color, description, order and state instead of a single line for the name. For vehicle statuses the operational meaning is added – it decides which status a workflow sets. All nine meanings are assigned, so a meaning is not invented but transferred: the previous holder gives it up in the same step. The dialog asks first.
- A third warning level for inspections: you can set how many days before the date a deadline counts as critical (7 days by default). Previously a deadline only became critical once it had passed.
- The workshop long-stay warning is configurable (7 days by default, critical from twice that) instead of fixed in the program. Clicking the figure opens the workshop list with exactly that filter.
- Backup retention: the program can remove old backups itself. Off by default. The three most recent backups and every backup taken before a migration are always kept; only the configured directory is cleaned, and only files matching the program’s own naming scheme.
- Driver record: everything about one driver on a single page – master data, contact, all vehicles with history, damages, accidents and workshop cases. Every section checks its own permission.
- Counters on the tabs of the vehicle record, such as “DAMAGES (3)”. Empty sections stay without a number.
Fixed
- Two safeguards had no effect: when deactivating the last active vehicle status and when renaming a shipped damage category, the new value was compared against the already loaded object. If the caller had edited that very object, both values matched and the safeguard did nothing. The comparison values now come fresh from the database.
- The notification “inspection overdue” carried that title even for deadlines that were still valid, because it depended on the warning level. It now depends on the date.
1.2.0
BetaAdded
- Lists on the reports page can be written as Excel, CSV or PDF. Previously PDF was the only option. Excel is the default, because lists are usually processed further.
- The dashboard figures are clickable: clicking a number opens the list behind it, already filtered – for example “no permanent driver”, “inspection overdue”, “open damages” or “in the workshop”. 22 figures lead into the matching list this way.
- Four new filters in the vehicle list: manufacturer (taken from the fleet, not from a fixed list), driver assignment (with or without a permanent driver), registration (registered or deregistered) and the roadworthiness test by stage – overdue or due within 14, 30 or 60 days.
- New export “Driver assignments”: the full history of permanent drivers per vehicle, with from, to (“ongoing” while open), assigned by and note.
- The maximum document size is now configurable, 25 MB by default. The storage additionally enforces a hard limit of 50 MB; a higher value in the settings does not lift it.
Fixed
- Documents are checked by their content, not by their file extension. Anything that looks like a program – EXE or DLL, ELF, Java, script with a shebang – is rejected, even if the file is called “invoice.pdf”. If the content does not match the extension, for example a PNG named .pdf, it is rejected as well. Formats without a reliable signature such as .txt, .csv and .eml remain allowed.
- Exporting a list now explicitly requires the “export data” permission.
- Export file names are in German instead of the internal English names.
1.1.1
BetaImproved
- The guide now also states what a checksum does and does not do: it detects an incompletely copied or altered package, but does not protect against someone who may write to the update share. Code signing and an update folder writable only by administrators do.
Fixed
- The checksum of the update package had never been verified: the check existed and was tested, but nothing called it. An update package from the share therefore ran unverified with administrator rights. The update service now verifies it itself, immediately before the start, and refuses to run on a mismatch.
- The expected value comes from latest.json; if it is missing, the checksum file next to the package applies. If neither exists, the package counts as unverified and is not started either.
- The check sits in the service, not in the interface – so no caller can bypass it. Under “Updates” the result is shown in plain words before you click install.
1.1.0
BetaAdded
- Your own master data under “Settings”: vehicle categories, damage categories and vehicle statuses can be created, renamed, deactivated and deleted – until now the shipped entries were the only choice.
- For each vehicle status you can define whether vehicles in it count as operational or available. The dashboard metrics build on that.
- Only entries that are not in use anywhere can be deleted; otherwise the message names what still refers to them. A deactivated entry disappears from the selection but stays on records already assigned to it.
Fixed
- Lists showed changes only after a manual refresh: reloading after a command ran into the same lock that catches double clicks and was silently discarded. 19 places in 15 views were affected.
1.0.0
BetaAdded
- A solo installation no longer needs a database server: the database is a single file, and Microsoft SQL Server Express does not have to be installed for it.
- Setting up a solo installation therefore takes about ten minutes and requires nothing to be installed afterwards.
- Backups of a solo installation are created as a complete file copy and then opened and checked for damage – even while the program is running.
- The setup wizard speaks the right language in solo mode: database file instead of server name, no search for SQL instances, no configuration file for further workstations.
- If the database file is missing or empty, Vehistra reports this at startup with the steps to check, instead of silently creating an empty database.
- The server check names the operating mode and skips everything that does not exist in solo mode: network shares, SQL service, firewall.
- Vehistra is published under the MIT license; the license file is installed with it.
Improved
- Database errors in solo mode are translated into understandable messages: file locked, no write permission, disk full, file damaged.
- The backup guide explains in its own chapter how the database file is backed up and restored; troubleshooting has a chapter on solo mode.
Fixed
- System diagnostics and the support package named a server in solo mode that does not exist – they now state operating mode, database file and its size.
- The recovery help and the notice window pointed to the SQL service, firewall and Management Studio in solo mode.
- System diagnostics reported “0.00 MB” for a populated database in solo mode.
0.6.0
BetaAdded
- The installer now asks for the operating mode: network installation for a workstation in the company network, or solo installation with everything on one computer.
- In solo mode the setup wizard is installed as well, linked in the start menu and offered right after the installation.
- If Microsoft SQL Server Express is missing, the installer explains this beforehand instead of leading into a dead end.
- The setup wizard recognises a solo installation: server and folders are pre-filled and network shares are no longer asked for.
- A new guide “Set up a solo installation” with eight chapters, including the move to network operation without data loss.
Improved
- The update package keeps the originally chosen operating mode: a solo installation does not lose its setup wizard, and a networked workstation does not get one pushed onto it.
- Release notes now state what has changed instead of only listing what is included.
0.5.0
BetaAdded
- Vehicles, drivers, inspections, mileage, maintenance, damages, accidents, workshop orders, plates, reservations, registration, retirement, insurance, keys and documents.
- Vehicle detail page with thirteen tabs and a continuous timeline. History is appended, never overwritten.
- Workshop report and accident report as true vector PDFs, blank and pre-filled.
- Server setup in twelve steps and a diagnostics program with plain-text messages instead of SQL error numbers.
- Updates through a central location with checksums, mandatory updates and a migration lock.
- Five guides as Markdown and PDF.