Changelog

Lex App v2.0.0rc59

Lex App v2.0.0rc59

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 reduces setup and initialization friction for Lex App projects.

Changelog

Added

  • Additional setup and initialization support for project bootstrap and environment-specific configuration.
  • Backend API/export support where the release introduces a new endpoint or field behavior.

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.
  • Initialization behavior is more tolerant of project-specific client names, deployment targets, and generated run configuration.

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 setup failures caused by missing generated files, client naming differences, or incomplete environment assumptions.

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.

Upgrade Impact

  • Apply database migrations before running history, audit, or calculation-heavy workflows after upgrading.
  • Regenerate or review generated project setup files if the project relies on Lex App initialization commands.