2025.2
Platform & Core
Stock Management Feature
The Sku actor has been extended with comprehensive stock management capabilities. Stock locations, reservations, back orders, and allocations are now first-class concepts within the Sku lifecycle.
Additionally, order lines now support a skuMap that carries the exact SKUs needed to fulfill a line, enabling precise inventory tracking from order to delivery.
Custom Routes for HTTP Ingresses Feature
HTTP ingresses now support custom route definitions with route parameters, decoupling the HTTP route from the ingress resource ID. Routes can include dynamic segments (e.g., api/orders/{orderId}) that are automatically extracted and bound to component parameters.
Previously, ingress routes were determined by convention from the ingress resource ID. With this change, you have full control over your API’s URL structure.
Learn more about HTTP Ingresses →
Improved Tax Model and Invoicing Improvement
The invoicing system has been rebuilt for resilience, addressing edge cases around tax calculations and discount handling. The updated tax model now supports absolute tax values alongside VAT-based percentage tax factors, enabling more accurate tax modeling across different regions and scenarios.
Changes to Assets and Tickets Improvement
Two changes to custom actors:
- Custom asset numbers — Asset actors now support custom-generated asset numbers, giving you control over your asset identification scheme
- Required type key — Assets and tickets now require a type key to be specified at creation, ensuring consistent classification from the start
Improved Apps Support Improvement
The app system has been expanded with additional capabilities:
- Registry entries — Apps can now include registry entries, allowing them to configure platform behavior as part of installation
- Rules — Apps can now bundle rules, enabling apps to react to system events and enforce business logic out of the box
- Cross-resource references — Components within an app can reference modules included in the same app and use graph customizations that result from the app’s own registry entries
Component Runtimes
Rule Modules Feature
The rule runtime now supports importing modules, enabling reusable code to be shared across multiple rules. This reduces duplication and makes it easier to maintain complex rule logic by extracting common patterns into shared modules.
dynamicQuery Macro Feature
A new dynamicQuery macro provides an alternative to the typed query keyword. Unlike the standard query macro which validates the query structure at compile time and returns a typed result, dynamicQuery accepts the query as a dynamic record and uses pattern matching to parse the result.
This is particularly useful when the final query needs to be assembled at runtime based on state or input parameters — for example, building queries where the selected fields or filters vary depending on user input.
Filtrera Update Improvement
Components now run on the latest Filtrera build, incorporating language-level improvements and bug fixes.
Graph
New Graph Fields Feature
The following fields have been added to the graph:
| Node | Field | Description |
|---|---|---|
| Delivery | finalizedAt | Timestamp when the delivery was finalized |
| Order | cancelledAt | Timestamp when the order was cancelled |
| OrderLine | salesQuantity | The sales quantity for the order line |
| Ticket | closedAt | Timestamp when the ticket was closed |
Dimension Key Format Improvement
Dimension keys in the graph are now available exactly as configured. Previously, dimension keys were automatically camel-cased when exposed through the graph. This change ensures consistency between how dimensions are defined and how they appear in query results.
Identities in Graph Feature
Identity data is now queryable through the graph, making it possible to include identity information in graph queries alongside other business entities.
Portal
Stack View Manager Feature
A new Stack view manager has been introduced as an alternative to the tab-based Workspace. The Stack view manager uses a stack-style navigation that is optimized for small screens and embedded scenarios — such as rendering Hantera inside a Zendesk ticket view or other constrained environments.
Improved Responsiveness Improvement
General responsiveness improvements across the portal, ensuring a better experience across different screen sizes and devices.
Copy Address from Order View Improvement
You can now copy addresses directly from the order detail view, making it quick and easy to grab delivery or invoice addresses for use in other systems.
Excel Export from Queries Feature
Query results can now be exported to Excel directly from the portal, providing a convenient way to extract data for reporting and analysis.
Design System & Portal App Development
useGraphDataProvider Feature
A new useGraphDataProvider composable is available in @hantera/portal-app, making it easy to create DataTables backed by a graph query. This significantly simplifies the process of building data-driven views in portal apps.
New Components Feature
Several new components have been added to the design system:
- NavigationBar — An alternative to TabBar for section-level navigation
- MessageTemplate — A component for rendering structured message templates
- ActivityLog — A component for displaying chronological activity entries
- ElasticInput — A text input that dynamically resizes to fit its content
Design System Improvements Improvement
- Box CSS classes — New utility classes for common box/container patterns
- DecimalInput — Now supports a
lazymodifier for deferred value updates - DropdownMenu — Automatically resizes when content changes and properly mounts/unmounts its children when opening and closing, improving both performance and correctness
Global Portal Components Feature
New globally available components for portal app developers (via @hantera/portal-app):
- FilesImage — Display images from the Hantera Files resource
- EmbeddedView — Embed other portal views within your app’s interface
- ProductSelector — A ready-made product selection component for building order-related workflows