Loading

What’s New in Actualog

These notes explain the practical effect of documented platform changes, with the latest implementation review dated 5 November 2026. They are organized by documented change date.

A change recorded here does not, by itself, confirm deployment to every hosted environment. Available functions depend on the deployed release, permissions, company entitlement and configured services. When planning an integration or rollout, confirm the behavior in your target environment.

5 November 2026 — reliability and domain ownership

More reliable editing and recovery

Persistence corrections ensure that changes to existing records are saved through their owning data access paths. Affected areas include background-job progress, roles, identifier namespaces, document metadata, facets and category metadata. Identifier replacement now uses the existing retry-aware transaction boundary, so its validation and related saves are treated as one command.

Channel requirement profiles also advance their concurrency token when a new version is appended without changing the profile name. This lets a later editor detect that the underlying profile changed instead of silently acting on an earlier version.

Production and passport preparation retain more precise recovery information. A retained preparation receipt can recover an accepted result after the owning operation has committed but its import acknowledgment was interrupted. These changes improve recovery of the same operation; they do not authorize a second operation or bypass current access checks.

Clearer technical ownership

Core product definitions, Logistics, Commerce, Billing and AI now use separate runtime Entity Framework Core models. They still share the existing physical database and migration history. This is a platform ownership improvement, not a claim that Actualog has become five independently deployed databases.

Company and Community catalog counters, Dashboard catalog cards, product logistics calculations and production actor labels read their authoritative sources through the relevant domain boundaries. The intended user behavior and record identities remain consistent while internal persistence responsibility becomes clearer.

More consistent operational data

Serial allocation responses preserve UTC timestamps. Packaging calculations retain category ancestry and declared base units, preventing an available base packaging definition from disappearing during source composition. Category and catalog filtering continue to apply authorization and paging before returning the visible result set.

For users: reopen an edited record to confirm its persisted state; use the existing operation result or retry mechanism after an interrupted response. A lost browser response is not evidence that a command failed.

4 November 2026 — account access, Billing and service controls

Verified e-mail ownership

Account e-mail addresses use one canonical ownership registry, including a primary address and confirmed aliases. Confirmation and recovery flows use standard ASP.NET Core Identity tokens. Confirmation links first show a preview; the actual confirmation is submitted through a protected form.

The account workflow includes correction of an unconfirmed registration address, resending primary confirmation, and a password reset form. Recovery is sent to the requested confirmed address. External sign-in uses the provider's proven address for automatic linking; an unproven new address remains subject to confirmation. Social registration uses password setup links instead of sending a password by e-mail.

See E-mails for the user workflow.

One Billing entitlement source

Company feature admission uses the effective Billing period. The former company-level paid-until field has been retired from the current contract. Integration consumers using the plan summary should use entitlementEndUtc together with the effective plan and active state.

Display projections support directory filtering and account labels; the Billing entitlement service remains responsible for admission. A displayed plan label does not independently grant a feature.

Better Assistant recovery and explicit service state

When AI processing is disabled, authorized conversation history, task status and cancellation remain available. The Assistant shows the unavailable processing state and can recover when processing is enabled, rather than leaving a reply spinner running indefinitely.

Administrative service controls own worker and AI enablement. Telemetry has its own setting. Worker execution state is distinguished from a saved configuration value, helping administrators see whether work can actually run.

2 November 2026 — delegated MCP tools

Actualog hosts its registered Model Context Protocol tools through the application. Delegated access continues to require native account sign-in, applicable MFA, consent, OAuth scopes and domain authorization. Environment capability switches determine which tools are available.

Connecting an agent does not grant unrestricted access. An agent must inspect the current capability context, respect the approved scope, and use the native review and command workflows. Category operations remain bounded by their published, populated and consumed model protections. See Actualog MCP.

15 October 2026 — Measures and Units

The measurement model now records qualification, conversion kind, affine offset, pinned source version and source-system membership. A Measure has one designated base unit, and UCUM identifiers are case-sensitive within its rules.

The administrative source-review workflow supports a reconciled QUDT inventory, dependency and value-impact review, stale-review refusal, and receipt-based recovery. The reviewed catalogue was applied in Development; its presence in another environment must be confirmed separately.

Existing identifiers, translations and stored product values are preserved. Unqualified legacy units are excluded from new selections rather than silently treated as verified conversions. Historical captures retain their own unit definitions; a newer dictionary does not rewrite an older product contract.

14 October 2026 — Category models and service requests

Separate Group values, Variant values and identity

Category bindings distinguish shared Group fields, a Variant's own characteristics, and the required axes used for identity. Group naming and identity exclude values that belong only to an individual Variant. Existing captures and hashes remain preserved by the documented transition.

For example, a shared manufacturer model can describe a Group while a concrete size or voltage distinguishes its Variants. Required identity fields and attribute importance answer different questions and should be reviewed independently. See Category Attribute Template and Effective Template.

One entry point for managed-service inquiries

Demo and proposal requests use a shared contact workflow with editable service context. The request is retained before notification attempts, and administrators can follow its ownership, quotation, acceptance and handover. A request starts a commercial discussion; it does not create an accepted quotation automatically.

Other established platform workflows

Production records connect approved Product Releases, manufacturing Batches, actual Facilities and individual Product Instances. Passport preparation selects an exact Model, Batch or Item subject. A published Digital Product Passport retains a reviewed snapshot; editing a working source is not the same as replacing that publication.

External catalog publishing uses separate commercial offers, channel requirements and delivery records. Warehouse reports own authoritative stock quantities; an offer price change does not overwrite inventory. Availability can remain unknown or outdated, and integrations must inspect its explicit state.

For workflow details, continue with Product Definitions, Production and Compliance, Digital Product Passports and External Catalog Publishing Concepts.