5dbe2fb5bb
- Added support for downloading labels and barcodes per package - Fixed proof of delivery behavior to ensure accurate completion records - Updated waypoint activity flow to rely on the `complete` flag - Added support for setting waypoints as either pickup or dropoff - Enabled sending notifications to order customer, driver, and facilitator - Added events and notifications for `order.completed` and `order.failed` states - Fixed route optimization logic and minor issues during order creation - Normalized `meta` response structure to always return an object (never array) - Patched issue with order config: deleting custom field categories no longer breaks config
Fleetbase Console
⭐️ Overview
The Fleetbase Console, a vital component of the Fleetbase Platform, serves as the graphical user interface that facilitates interaction with all Fleetbase extensions. It's architecturally designed to be lightweight, primarily employing Ember Engines for its operational foundation. Ember Engines, a scalable development paradigm for ambitious web applications, allow the Console to dynamically load and manage extensions, ensuring a streamlined and efficient user experience.
The responsibilities of the Console are kept minimalistic to maintain its performance and agility. The Console's key responsibilities encompass administration management, configuration of organization and user settings, and establishing a robust connection to the Fleetbase extensions repository. In its administrative capacity, it provides an intuitive interface for configuring the Fleetbas instance.
Lastly, the Console plays a pivotal role in connecting to the Fleetbase extensions repository. This provides the flexibility to add, update, or remove extensions as per the organizational needs and preferences, all while ensuring the seamless operation and integrity of the Fleetbase Platform.