Logidav Interfaces

Use this section to move from the Logidav interface entry point to its route, controller, and documented workflow family. The endpoint inventory is a static reading of one pinned source revision; it does not establish a user's live menu or a deployed route table.

Home and dashboard flow

The Home item in Builder::mainMenu() points to homepage. The root annotation import in app/config/routing.yml and DashboardController::indexAction() bind that route to /; the annotation declares no HTTP method, so this source review does not infer one. checkMenuPermission() forces the Home menu item to display, which describes menu rendering only and does not prove controller authorization.

The controller asks KnpMenu for Builder::mainMenu() with dashboardMenu: true. The builder collects entries carrying dashboard metadata and sorts them by their configured dashboard.order; the dashboard template renders displayed entries using their dashboard.name, icon or image, and menu URI. The controller separately calls service ID mz.statistic and method getHomeDashbord() for dashboard response data, then renders the dashboard template. These calls establish the source navigation path, not the current metric values or a live user's rendered dashboard.

Source path: Builder.php Home declaration → DashboardController::indexAction() → Dashboard/index.html.twig.

Menu and endpoint inventory

Menu endpoints lists every active addChild() declaration, its hierarchy and label, route parameters, static path/controller/method match, visibility notes, and linked workflow family. It also reports folders, dynamic source expressions, commented-out declarations, missing-name coverage, and the duplicate Payline/Ezyness route definition that prevents an unambiguous effective-controller claim.

Workflow families

• Orders and fulfilment
• Stock and purchasing
• Product content and media
• Supplier catalogues and publication
• Pricing and monitoring
• Stores and marketplaces
• Customer service and payments
• Shipping, reporting and admin

The menu grouping provides a navigation aid for these workflow pages. Each workflow page identifies its own source-backed segment and remaining runtime or owner-acceptance gaps.