Skip to content
Vehistra
Documentation navigation

Settings and catalogs

Company data

Company name and logo appear in the interface and on the PDF reports.

Warning levels

The thresholds of the deadline monitoring define when a date starts to stand out and when it becomes urgent. They apply to all vehicles – see Deadlines and maintenance.

Inspections have three levels: notice, due soon and critical. The critical level applies before the date – seven days before it by default. When saving, the program puts the three values into a sensible order.

How long a vehicle may stay in the workshop before it stands out is configurable as well: seven days by default, critical from twice that.

Your own master data

Three catalogs can be maintained under Settings – create, rename, deactivate and delete:

| Catalog | What for | | ------------------ | ------------------------------------- | | Vehicle categories | Areas of use for the vehicles | | Damage categories | Classification of damage reports | | Vehicle statuses | State of a vehicle in daily operation |

Every entry has an edit dialog with color, description, order and state – not just a name field.

The same rules apply everywhere:

  • Shipped entries can be deactivated, but not deleted.
  • Only entries that are not in use anywhere can be deleted; otherwise the message names what still refers to them. History and recorded events are never changed.
  • A deactivated entry disappears from the selection but stays on records already assigned to it, and can be switched back on.
  • Duplicate names are rejected, including in different spellings.

Vehicle statuses

For each status you define whether vehicles in it count as operational or as available. The dashboard metrics build on that – a new status without this setting will not appear where you expect it.

That mapping is called the operational meaning. It decides which status a workflow sets – retirement, workshop, import. All nine meanings are shipped and assigned, so a new one cannot be invented: a meaning is transferred, and the previous holder gives it up in the same step, so exactly one status carries it at any time. The dialog asks first. Removing it is blocked – otherwise a workflow would silently stop setting a status.

The program safeguards three points:

  • Shipped status values may be renamed: workflows rely on the meaning, not on the name.
  • The shipped damage category “Unfall” (accident) cannot be renamed – the damage report created from an accident finds it by name. Deactivating is possible, and the assignment keeps working.
  • The last active vehicle status cannot be deactivated. Without an active status no vehicle could be created any more.

Document size

The maximum file size for documents is configurable and starts at 25 MB. The storage additionally enforces a hard limit of 50 MB; a higher value is clamped to that range when saved, so the interface never promises what the storage will not hold.

Changing existing values

Renaming is uncritical: assignments stay intact. Existing values should not be repurposed to express something new – create a new value instead. Otherwise you retroactively change the meaning of old records.

Logs

Vehistra writes log files with daily rotation to:

C:\ProgramData\LSP Virtual Services\Vehistra

For a support request a support package can be produced from them. It contains logs, version details and system diagnostics – but no passwords, no SQL credentials and no vehicle or personal data.