Skip to content
English
  • There are no suggestions because the search field is empty.

Release notes Business Engine January 2026

This release introduces generic discard functionality across core entities, new integration to Tarana, support for using one ONT across multiple Objects, and backend support for FSM-triggered customer notifications.

Generic Discard Functionality

A generic Discard mechanism has been added to support data lifecycle management.

Discarded entities are excluded from API searches by default.

A configurable filter allows discarded entities to be included when required.

Supported entities

  • Customer – Fully anonymized when discarded; requires no active orders.

  • Object / ObjectGroup – Discard depends on related entities being discarded.

  • Order – Must be inactive.

  • Network Element – Must not be connected to objects or other network elements; name and identifiers are updated.

  • Service – All related orders must be discarded; discard is performed from the service list.

  • User – Must be disabled; username updated and email cleared.


Tarana System Integration

This release introduces a new integration with Tarana, a fixed wireless access (FWA) solution for delivering broadband services over radio networks. The integration supports provisioning, network element management, and operational actions through the Tarana Cloud Suite (TCS).


One ONT for Multiple Objects

The platform now supports provisioning services (via Calix SMx) using a single ONT across multiple Objects by assigning different ONT ports to each Object. This enables scenarios such as a single ONT installed in an apartment complex, where individual apartments are connected and provisioned independently through separate ONT ports.


FSM-Triggered Customer Notifications

It is now possible to automatically send email or SMS notifications when a work order is marked as “En Route” in FSM. This enables proactive customer communication when the technician begins traveling to the service location.