Repository navigation
FU — EmuFramework v1.1.0
FU — EmuFramework v1.1.0
Summary
This framework update adds localized metadata labels, personal navigation, record attachments, document-level Data Entity exchange, governed business-data archiving, storage monitoring, and a substantially expanded Report Designer.
Improvements
- Adds BCP-47 metadata translations with per-user locale and exact-locale, base-language, and default-label fallback.
- Adds server-backed Favorites and the ten most recent authorized navigation items per user.
- Adds file, note, and URL attachments to saved header and line records with opaque storage keys, SHA-256 integrity, streaming upload/download, configurable limits, and parent-record permissions.
- Adds separate
/filesand/archiveDocker volumes while retaining shared/datafallbacks with administrator warnings. - Adds Header/Line Data Entities with XLSX sheets or manifest-based CSV ZIP packages, durable staging, per-document atomic upsert, and downloadable error files.
- Adds opt-in archive policies for explicitly eligible Data Entities, immutable checksummed payloads and blobs, scheduled batches, read-only search, collision-safe restore, and job history.
- Adds a Storage & Archive dashboard with filesystem capacity, database/WAL, backup, font, live-file, archive, and per-App database usage.
- Expands Report Designer with A3, A4, A5, Letter, Legal, and custom paper; orientation; four margins; cm, inch, and pixel display units; strict layout validation; text/field borders; and PNG/JPEG images from bundled assets or record attachments.
- Extends backup schema version 4 with live files and archive data, streaming backup downloads, and backward-compatible restore validation.
Breaking changes and migration
No existing metadata or API contract is removed. New metadata kinds and fields are additive. Official Docker deployments should add the emu-files:/files and emu-archive:/archive named volumes and set EMU_FILE_STORAGE_PATH=/files and EMU_ARCHIVE_STORAGE_PATH=/archive. Existing deployments continue to boot with /data/files and /data/archive, but the administration page warns that shared fallback storage is in use.
Reports remain compatible as layout version 1. Existing overflowing reports can still preview with warnings. A report saved from the updated designer becomes layout version 2 and must pass the printable-area validator.
Upgrade notes
Create a full backup, preserve .emu-secret.key, and update the application and updater images together to 1.1.0. Before stopping the application, the updater verifies that the application and updater see the same separate file and archive mounts. After restart, verify Settings → System Maintenance → Storage & Archive, configure archive policies only for declared Data Entities, and confirm attachment upload/download permissions.
Plan SSD capacity for databases, WAL, backups, live attachments, archive payloads, and rollback headroom. A practical baseline is 200 GB for a 4-vCPU/8-GB server; use 100 GB only for light deployments without material attachment growth, and 500 GB or more for file-heavy workloads.
Validation
The candidate is required to pass version consistency, release-policy tests, core/server/client type checking, all automated tests, production builds, and the isolated local Docker acceptance gate without dependency installation or network pulls. Docker acceptance covers fresh install, upgrade, failed-health rollback, interrupted maintenance recovery, restore rollback, byte equality, mount-continuity rejection, and attachment backup/restore.
Known issues
Archive data is retained indefinitely in this release; automatic archive purge is intentionally not provided. Legacy .xls files are not accepted by Data Entities. Attachment versioning and check-in/check-out are not included. Framework UI strings, runtime error messages, and business record values are not translated by metadata translation resources.