NEW! Release notes Business Engine August 2026
This release brings improvements to order notifications, reporting, billing flexibility, customer management, and API capabilities, along with ongoing stabilization work and security enhancements across the platform.
Orders & Signups
Notification for Resumed Orders
Customers now receive an email notification when a paused order is resumed, matching the notification they already get when the order is paused. The new mail template is called Customer:Resumed Order. This applies regardless of how the order is resumed, whether manually from Admin, through the Partner API, automatically when an overdue invoice is paid, or through the standard workflow.
Cancellation Reason for Surveys and Signups
When discarding a signup or survey, or rejecting an order, users can now select a reason from a configurable dropdown. The reason field can be set as mandatory or optional.
Reporting
Order and Survey history reporting
Order history events can now be tracked in the reporting database. Two new report views expose the workflow history behind orders and surveys, so operators can trace status changes over time, including who performed each step and when, similar to work order history tracking in FSM.
Billing
This information applies only when end-customer billing is enabled.
Batch Schedule now available for SuperAdmin Profile
Super Admins can now manage the batch schedule for invoice creation, payments, and auto pause directly in Admin, without needing COS involvement.
Extended Promotion Stacking
Extended support for stacking promotions and credits on top of existing discounts, allowing more flexible combinations such as adding a temporary credit during an ongoing discount period.
New Billing Endpoints in API
New endpoints have been added for Transactions and BillingInvoiceRows, giving billing related data access through the API.
API
New: ready-to-use login link in the Customer Token API
The Customer Token API (POST /api/v1/Customer/Token/Create/{customerId}) now returns a ready-to-use LoginUrl and PortalUrl, in addition to the existing TokenId.
An optional ReturnUrl parameter can be included in the request to deep-link the customer to a specific page (e.g. the billing page) right after login. The link is a one-time credential: it can only be used once and expires after the configured validity period.