Repository navigation
FU — EmuFramework v1.4.0
FU — EmuFramework v1.4.0
Summary
Draft-based record creation, audit field aliases, UTC datetimes, image input for Functions, configurable branding and collapsible deployment previews.
Improvements
- New records open as encrypted, user-bound drafts:
initValueresults (including read-only document numbers) are shown without inserting a row, and saving is atomic, retry-safe and survives a restart. Expired drafts, other users' drafts and drafts created before a metadata change are rejected; failed saves roll back and keep the draft usable. - Read-only virtual audit fields
sys_createdBy,sys_createdAt,sys_modifiedByandsys_modifiedAtcan be listed, filtered, sorted and used in Views. Updates preserve the original creation audit and ignore forged audit values. - Datetimes are stored and returned in UTC and shown in the browser time zone. Numbers are displayed with grouping; IDs, references and strings are not reformatted.
- Functions can declare
imageInputto receive JPEG, PNG or WebP images attached to a record, selected from files or the camera. Uploads are deduplicated, signature-checked, permission-checked and retried per file. WebP attachments can be previewed. EMU_APP_TITLEbrands the browser title, login and setup pages. Deployment previews start collapsed with counts and show where moved or deleted artifacts came from.
Breaking changes and migration
Lifecycle hooks (initValue, validateWrite, validateDelete) and data event handlers must be synchronous; async functions or returned Promises now raise an error instead of running outside the transaction. Move awaited work into an async Function. System field names are reserved case-insensitively, and schema sync stops without changes if a stored column collides with an audit alias. Datetime values without an offset are interpreted as UTC and returned with Z. Table metadata from /api/metadata now includes the system fields.
Upgrade notes
Back up the data and designer databases together. Update application and updater images together to 1.4.0. Draft storage is created automatically; no data migration is required. Review scripts for async lifecycle handlers before upgrading. Read Record lifecycle, audit fields and Function images for details.
Validation
Version consistency, type checking, production builds and automated tests pass on Node 24 (135 core, 45 client, 162 server and 6 release-policy tests; one optional legacy-backup fixture test is skipped). The 1.3.0-to-1.4.0 persistent-database upgrade check passed for existing login, business/audit/datetime data, CUS extension fields, existing initValue scripts, Recent/Favorites, legacy package preview, and an encrypted draft saved after restart. This branch is not published.
Known issues
Drafts invalidated by a metadata change must be reopened; entered values stay in the open page but are not transferred automatically. Uploaded images remain attached when the Function fails. External side effects cannot be rolled back. New long-tail administration/Designer labels remain English.