Overview

What this module covers

Paths omit trailing slashes in everyday use; the app normalizes them.

Finding these screens

The main dashboard sidebar does not currently expose Maintenance or Work Order as top-level items. Tenants usually arrive by:

1. Bookmark or shared link to one of the URLs above.
2. Deep link from another workflow (for example a future email or report link your organization provides).

Optional vehicle-level tabs for “Work Order” and “Issue And Incidents” exist in the codebase but are commented out in the vehicle detail layout, so you should not expect those tabs on the Vehicle screen in the current build.

Data source in the reviewed console build

This manual is written against the sass-console tenant UI. In that codebase:

• Issues and incidents lists are seeded from in-app sample data (mockIssues / mockIncidents). Creating, editing, or deleting only updates the browser session state unless your deployed build replaces this layer with API calls.
• Issue and incident detail pages load records from the same sample data in the route loader, not from /vehicles or a dedicated REST resource.
• Service tasks, refuel work orders, service work orders (list and detail), and /v public views use static or generated mock data.
• The live vehicle detail API (GET /vehicles/:id) is used for the main vehicle profile, but the TypeScript contract for that response does not include workOrders or issuesIncidents; vehicle sub-routes that expect those arrays are not aligned with the typed API model in the reviewed code.

📌 Note: Treat everything below as user-interface and validation documentation. For your organization’s production environment, confirm with your administrator whether real APIs back these screens.

Suggested reading order

1. Access & permissions
2. Issues: list → forms → detail
3. Incidents: list → forms → detail
4. Service and refuel work orders
5. Public links if you share work orders outside the dashboard