דילוג לתוכן
מרכז התיעוד
לאתר LinkNodes Energy
LinkNodesENERGYתיעוד

טוענים את החיפוש…

    חיפוש גם בתוך המאמרים ↑ ↓ לניווט Esc לסגירה

    לאתר החברה

    מוצר ויכולות

    הוספת רכב לפי רישוי

    זיהוי רכב רשום, אימות נתונים ומצבי שגיאה בזרימת ההוספה.

    בעמוד הזה

    The product identifies vehicles exclusively by a 7- or 8-digit Israeli registration number. The driver garage, global vehicle action, national directory and connected fleet editor no longer offer manual manufacturer/model selection. Old ?model= links cannot preselect a vehicle. The illustration gallery remains an asset preview, not a vehicle-selection form.

    Identification and imagery#

    • POST /api/reference/vehicle requires an authenticated session, same-origin JSON, validated input and the existing per-user lookup quota. The registration travels in the request body, never in a URL or analytics event.
    • The server queries the official registry by exact registration, checks the returned number, and joins the official catalog using manufacturer code, model code and production year. Fuel and trim distinguish variants. Equivalent duplicate catalog rows can resolve to one identity; conflicting bodies, trims or generations cannot.
    • The result includes the canonical catalog record and the shared reviewed image. The image appears immediately, then in saved vehicle cards, fleet tables and the current workspace's dashboard card. Missing illustrations use an explicit neutral placeholder; absence of an image does not prevent saving an identified vehicle.
    • The result describes a model and is labeled as AI artwork. Registration lookup does not verify ownership. Owner and VIN fields are neither requested nor returned.

    Saving and state#

    • Connected vehicle writes accept registration plus editable fleet metadata. They reject client-supplied model IDs, catalog snapshots, image URLs and tenant fields.
    • New vehicles and changed registration numbers are independently resolved on the server before writing. Permission checks, tenant scoping and the lookup quota apply. A metadata-only update preserves the existing identity and avoids another registry request.
    • Changing the input invalidates the previous result and cancels pending requests. A delayed response cannot replace the result for a different registration. Saving a new or changed vehicle is unavailable until identification succeeds in the interface; the server enforces the authoritative match independently.
    • Missing records, ambiguous variants, unavailable sources and quota exhaustion produce explicit retry/error states without manual selection or a sample-car fallback.
    • Demo workspaces retain their clearly labeled sample vehicles, without a manual catalog picker. They do not perform live identification.

    Validation#

    • Unit coverage includes authoritative code/year/fuel/trim matching, ambiguous bodies, incomplete upstream responses, input privacy, connected write authority, quota failures and tenant-scoped edits.
    • Browser fixtures cover lookup-to-image-to-save, stale response cancellation, changing the number, authentication/source/quota errors, fleet editing and narrow light/dark layouts. Fixture plates are synthetic and all registration/write requests are intercepted; these checks do not write customer data.
    • The actual public catalog was queried to verify its manufacturer/model/year filters. Production smoke checks must also verify the unauthenticated boundary and the deployed UI. A successful lookup of a real registration requires the customer's authenticated session and an in-scope registration number.

    Production acceptance · 2026-11-08#

    • Runtime commit: 875f8dae82555506c691ed4eab3303a403eff4bc.
    • Vercel deployment: [operational-id-redacted], READY and assigned to product.linknodesenergy.com.
    • 150 unit tests, ESLint, TypeScript and the production build passed. Twenty distinct local browser checks passed, followed by the narrow-screen regression after the final layout adjustment. Desktop and dark mobile result cards were inspected visually using a synthetic registration response.
    • Seven production browser checks passed: four intercepted registration UI scenarios and three gallery/reference checks, including all 132 images. The authenticated fleet write scenario ran locally and was deliberately skipped in production; no customer accounts or records were modified.
    • Verified HTTPS returned the registration-only page. Unauthenticated same-origin lookup returned 401; a cross-origin lookup returned 403, with no vehicle data. Real-number identification remains authenticated; no customer's registration was used for the release tests.
    • Product: https://product.linknodesenergy.com/vehicle.