Moltaro 0.0.47-beta

Release date: 2026-09-08

Workspace C# integrations can upload governed catalogue files for File and Table fields without treating them as record attachments. File Retention also gains clearer Source details, independent version previews and download access management, with more reliable keyboard navigation and live history.

Highlights

Upload files from C# functions and Jobs into an existing catalogue folder through the supported IFileCatalogService.
Browse retained versions without replacing the Source history grid, and manage download access in a separate Source dialog.
Navigate Source actions and CRON editors reliably with the keyboard.

Detailed changes

Governed catalogue uploads from the .NET SDK

IFileCatalogService exposes managed stream uploads, upload capabilities, status and cancellation for an explicitly selected existing UserDefined catalogue folder. Published files belong to the workspace Vault and can be assigned to File and Table fields through the ordinary governed entity mutation APIs. Uploading bytes does not itself assign a field.

The service retains managed upload integrity inspection, quotas, idempotent retry and publication controls. Folder access is checked for ordinary callers; trusted Job invocation context is supplied by the runtime rather than a caller-selected administrative flag. Existing attachment uploads continue to use IAttachmentService and retain their record attachment ownership.

The installed developer surface and file-transfer guide describe the new service. Integrations must check that their installed runtime exposes it before publishing project source that depends on it. Existing files are not moved or reassigned automatically by the runtime upgrade.

Source lists separate preview and details from additional actions. Source details use independent information cards, with focused configuration and schedule editing. History remains visible while a retained version opens in its own preview, and closing the preview preserves the selected history page. Download access is managed through a separate paginated Source dialog.

Live views retain the selected version and loaded content while refreshing. Expired versions stop offering download even when a refresh request fails. Restricted operation or schedule details are distinguished from an empty history or a disabled schedule, and permission loss clears protected content. Download guidance distinguishes the portable utility, access file and command. These changes include all five supported interface languages.

Keyboard interaction

Grid action menus close when an enabled action opens a dialog or another view, and do not remain underneath the new surface. Keyboard-opened CRON editors place focus after the opening transition; Enter on Apply commits the draft instead of merely closing the editor. Schedule validation and execution semantics are unchanged.

Database and upgrade impact

No database schema or business-data migration is introduced. Delivery uses full runtime replacement with a short interruption for each Managed App. Existing records, file bodies, storage bindings, retained versions and schedule settings remain in place. No file-body storage copy is required.

The release creates fresh control-plane and workspace recovery points before activation. Retain them together with the previous runtime. Binary rollback does not undo later integration writes or file-reference changes. Once a workspace project depends on the new SDK, rollback must also coordinate a compatible project revision and any required data recovery; do not resume an older importer against newly reassigned file fields.

Deployment and operator actions

Use the two-phase Deployctl ReplaceRuntime workflow for all three Managed Apps; this is not an update-package or Portal-only publication.
Keep the existing compatible workspace C# source fixed during prepare and promote. The upgrade checks and rebuilds that exact revision with the target runtime; do not upload a new project draft during the release.
Keep synchronization schedules disabled during the integration rollout. Publish the new importer separately only after the installed developer surface exposes IFileCatalogService.
Preserve the active Workspace UI project and its source/artifact history. Verify compatibility after replacement; this release does not activate a different custom UI artifact.
After installation, verify the new SDK surface, application health and File Retention navigation. Complete the bounded importer assignment, download and replay scenario before resuming bulk synchronization. An installed SDK alone does not prove customer migration acceptance.
No new credentials, buckets, permissions, or runtime-agent version are required. Runtime VM agent 0.1.45 remains the declared version.

Compatibility and breaking changes

The catalogue API is additive. Existing workspace project sources and ordinary attachment integrations remain supported. New project source using IFileCatalogService requires this runtime or later and is not compatible with an older SDK. File Retention changes do not alter its HTTP DTOs, storage policy, portable download protocol or schedule semantics.