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

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

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

    לאתר החברה

    שחרורים ואימות

    שחרור חוויית המוצר

    רשומת שינוי חוויית המוצר מ־9 בנובמבר 2026.

    בעמוד הזה

    The four account capacities remain Personal 1, Family 3, Business 10, Enterprise unlimited. This release changes presentation and navigation, not paid entitlements or charging authorization.

    Action hierarchy#

    • The driver discovery heading offers Scan QR. The global vehicle search was replaced with station discovery; registration lookup stays in the vehicle flow.
    • Other driver screens and every workspace header offer a compact QR entry. History and charging pages link back to the map.
    • Workspace page actions follow the resource: add a vehicle, add a driver, create a charging credential, or invite a member, subject to existing permissions and capacity checks. The unrelated fallback “my vehicles” action is removed.
    • Settings put the workspace identity first, followed by account-plan controls and preferences. Cost-center configuration is shown only in Business and Enterprise.

    Identity and visual language#

    Personal uses teal, Family magenta, Business violet, and Enterprise blue. All share the same readable dark sidebar, active-state shape, gradient identity surfaces, typography, card/table treatment and primary scan action. Both appearance modes and narrow viewports are supported.

    The authenticated personal profile presents the actual Clerk identity, image, email verification, two-factor status, account creation month and authorized workspaces. The verified Clerk editor remains responsible for photo and sensitive identity updates. The account summary remounts on user ID changes to avoid carrying workspace state across identities.

    Workspace profiles include the saved logo, plan, role, contact summary, recommended-field completion, grouped company/contact/address fields, and explicit save/cancel states. Completion is based on saved fields; filling a draft does not claim completion. Logos retain the existing file limits and protected upload implementation. Personal and Family do not show company registration or website fields. Demo profiles remain explicitly local.

    QR behavior and limits#

    components/charge-entry.tsx decodes camera frames and image files locally using a lazily loaded jsQR decoder. Camera access requires a click, HTTPS/localhost and permission. Closing the dialog, leaving the tab or unmounting stops camera tracks, including a stream returned after the user closed the dialog. Escape returns focus to the initiating button. Camera denial has image/manual fallbacks.

    QR contents are untrusted. Only explicit mot:<id>/mot-<id> national reference identifiers or exact HTTPS product station URLs can resolve to an internal station. The reference endpoint checks the ID against the existing station catalog before showing a link. Arbitrary scanned URLs are never fetched or navigated to. The active workspace is preserved in internal map/station links. A missing station, unreadable image, network error or unsupported provider code is reported explicitly.

    This release does not enable remote charging, payment, or interoperability with provider QR schemes. Provider codes need contracted integrations and a verified connector-to-EVSE mapping. The dialog states this limitation. QR images are neither uploaded nor retained.

    Verification#

    • TypeScript, ESLint, 175 unit tests.
    • Four-plan navigation, onboarding and vehicle-capacity regression coverage.
    • Four-plan profile layout in light/dark at 1440, 390 and 320 pixels.
    • Saved completion/cancel behavior, contact and logo persistence in demo.
    • Actual QR image decoding; trusted resolution; unsupported-code handling; camera denial; closing during pending camera permission; workspace preservation and focus restoration.

    A physical mobile camera and authenticated Clerk profile changes are not exercised by the local browser suite. Those integrations retain their existing server contracts; no real customer profile data was changed for verification.