Lex App v2.0.0rc104
Lex App v2.0.0rc104
Release Notes
This release refines how Lex App records lifecycle and bitemporal history around model changes.
That matters for audit-heavy applications because history should describe meaningful business changes, not framework side effects created while calculations or setup routines are running.
This release improves the audit and calculation-log path so operational records are easier to trust during calculations, imports, and background processing.
This release strengthens the bridge from older Lex/generic-app projects into the v2 backend model.
Changelog
Added
- Compatibility support for older project structures or legacy data where applicable.
Changed
- History and lifecycle timestamps are aligned more closely with business-relevant model changes.
- Audit and calculation-log records are finalized more consistently around initial data, calculations, and background work.
- Migration behavior is better aligned with the v2 project structure and ETL model conventions.
Fixed
- Reduced noise in history caused by framework-driven calculation or setup activity.
- Reduced cases where logs or audit statuses could be missing, premature, or hard to interpret.
- Reduced environment-specific packaging failures around generated files, package contents, or dependency resolution.
Improved
- Bitemporal records are more dependable for audit, reporting, and as-of analysis.
- Operational traceability is stronger for administrators investigating calculation and data-change outcomes.
Maintenance
- Kept the distributable backend package aligned with the current v2 runtime expectations.
Upgrade Impact
- Apply database migrations before running history, audit, or calculation-heavy workflows after upgrading.
- Rebuild application images or virtual environments so dependency and packaging changes are actually used.
