Moltaro 0.0.58-beta

Release date: 2026-09-11

File Protection now guides administrators through connecting an Agent and configuring its local source file. Task Definitions gain instructions and configurable number prefixes, while fixes improve entity configuration saves, table sorting and completion of file uploads when the message broker is unavailable.

Highlights

• Configure a File Protection Source directly from its status or detail view, with generated local configuration instructions and clear Agent readiness.
• Maintain Markdown instructions and ordered File Storage references on Task Definitions, with a configurable number prefix.
• Save Form and Card changes reliably when edits overlap, and retain local sorting in administration tables.
• Manage the Workflow module’s foundation settings and readiness; process execution is not included in this release.

Detailed changes

File Protection

Source setup explains archive extraction, the local file path, configuration application, service restart and confirmation by the Agent heartbeat. Missing local configuration has a direct setup action. The new configure-source Agent command validates the selected installation, Agent and Source before merging one mapping into the existing configuration. Other mappings and settings are preserved, and a backup of the previous local configuration is retained.

Agent status uses a consistent icon, text and color. Source, history and audit views use compact empty states. Clicking navigation behind a non-modal preview drawer both closes the preview and performs the requested navigation. Signal file filters discard selections that no longer belong to the current source or access context.

Tasks configuration

Task Definition instructions support Markdown and up to twenty ordered references to existing File Storage files. File visibility follows the current user’s access, and the settings editor supports saving, disabling and reloading instructions.

Task Definitions expose NumberPrefix, defaulting to TASK-, with a maximum of 32 characters and support for an explicit null value. Configuration reads aggregate the current definitions, queues and worker profiles while respecting configuration access and dependency changes. Policy dialogs remain open across refreshes of unchanged data.

Task-instance execution, assignment, completion and persistent number allocation remain outside the supported production runtime in this version. The Tasks workbench is still a development prototype; its presence in source does not provide production task execution.

Entity configuration and tables

Form and Card saves capture the selected configuration before entering the save queue, preventing an earlier response from replacing a later edit and avoiding redundant autosaves. Large field-target catalogs are virtualized. Entity display settings wait for their definition to finish loading before accepting edits.

Definition and field changes update derived configuration after the owning transaction commits. Later metadata reads within a transaction use the saved definition state, including after a savepoint rollback. Default field controls and renderers use consistent capability policies while preserving explicit configured choices and ordering.

Administration tables with local sorting retain the user’s selected order. Navigation-scoped transfer dialogs close after successful navigation, and active editor labels and controls have corrected translations and presentation.

File uploads and Workflow

File-verification notifications are delivered asynchronously after upload state is committed. Broker failure or a notification timeout cannot hold an already durable upload request open; background recovery continues to discover persisted work.

Workflow adds an administrator settings page and lifecycle/readiness API, including a persisted reason when the module is disabled. Its public Engine and Package SDK assemblies are included. Process definitions and execution are not yet available.

Database and upgrade impact

Workspace databases gain Task Definition instruction settings and number prefixes. Existing definitions start with instructions disabled and the prefix TASK-. PortalDb has no schema change. Application data is retained during the upgrade, and existing Task instances are not created or converted by it.

This release replaces application runtimes and requires brief downtime per application. Take recovery points before migration. Rollback must use the matching previous runtime and database recovery point; removing the new instruction or prefix fields would discard values saved after the upgrade. Restoring a recovery point also loses later writes. Referenced file backups still require their retained Object Storage bodies and keys.

Deployment and operator actions

Deploy using ReplaceRuntime through release prepare, inspect readiness, then use its frozen runner for release promote. Preparation builds and inspects the exact runtime, Portal, documentation and Agent artifacts and checks every pending application’s extension compatibility before production changes. Promotion creates recovery points and activates the prepared artifacts.

The Runtime VM Agent version is allocated automatically and verified on every VM. Immediate local cache retention preserves current, previous and unfinished-operation references. Historical unsupported workstation preparation records no longer cause successful release finalization to report a cleanup failure.

To use configure-source, download the File Protection Agent bundle delivered with this release and follow the generated setup instructions. Runtime VM Agent replacement does not update an Agent installed on a customer’s computer. Source schedules, file paths and credentials are not changed automatically by runtime replacement.

After replacement, verify application health, the migrated configuration, active extension compatibility, File Protection downloads and ordinary scheduled file processing. Keep current customer source revisions unchanged throughout the transition.

Compatibility and breaking changes

Task Definition update requests must now include the NumberPrefix property; its value may be null. Update integrations that previously omitted this property. Task Definition detail and runtime models include required Instructions; C# integrations that construct these records must supply that argument. Rebuild affected extensions against the delivered SDK and pass the target-runtime compatibility check.

Existing field-type numeric identities and explicitly saved UI choices are preserved. Workflow foundation APIs and the File Protection configure-source command are additions. This release does not enable production Tasks workbench execution or Workflow process execution.