mirror of
https://github.com/fleetbase/fleetbase.git
synced 2025-12-19 14:18:57 +00:00
v0.7.9 ~ shorter default data retention + template variable resolver + patched order vehicle update via api
This commit is contained in:
12
RELEASE.md
12
RELEASE.md
@@ -1,12 +1,16 @@
|
||||
# 🚀 Fleetbase v0.7.8 — 2025-08-12
|
||||
# 🚀 Fleetbase v0.7.9 — 2025-08-13
|
||||
|
||||
> “Improved system maintenance”
|
||||
> “Template variable resolver + patch vehicle update on order via API”
|
||||
|
||||
---
|
||||
|
||||
## ✨ Highlights
|
||||
- Improved and optimizes maintenance scripts
|
||||
- Patched OSX binary build
|
||||
- Patched vehicle assignment update on orders via API
|
||||
- Added ability to use variables in order config activity objects for the `status` and `details` properties
|
||||
- Tigher data retention time by maintenance scripts
|
||||
|
||||
### Variable Usage
|
||||
Now in your activity status and details fields you can do things like "Driver completed {waypoint.type}" or "{capitalize waypoint.type} has been completed". These use of variables will then be resolved, say "waypoint.type" = "pickup", then in the inserted activity status those examples would resolve to "Driver completed pickup", and "Pickup has been completed".
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user