Changelog

Lex App v2.0.0rc165

Lex App v2.0.0rc165

Release Notes

This release improves the reliability of Lex App calculation execution, especially around asynchronous work, worker lifecycle, and calculation state transitions.

The practical result is a more trustworthy calculation pipeline for long-running business models where users need clear outcomes rather than ambiguous pending or failed states.

This release improves the audit and calculation-log path so operational records are easier to trust during calculations, imports, and background processing.

This release hardens identity, token, and permission handling across backend request paths.

Changelog

Added

  • Backend support for more explicit calculation execution and recovery flows where applicable.
  • Additional setup and initialization support for project bootstrap and environment-specific configuration.

Changed

  • Calculation state transitions are handled more consistently across synchronous, asynchronous, and nested execution paths.
  • Audit and calculation-log records are finalized more consistently around initial data, calculations, and background work.
  • Token, session, and permission context handling is more consistent across backend request types.

Fixed

  • Reduced ambiguous calculation outcomes caused by worker shutdown, callback handling, deadlocks, or dispatch timing.
  • Reduced cases where logs or audit statuses could be missing, premature, or hard to interpret.
  • Reduced authentication edge cases around Keycloak, API tokens, role/group lookup, and user-context enrichment.

Improved

  • Long-running calculations are easier to supervise and recover after runtime interruption.
  • 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.
  • Restart application workers and schedulers so calculation execution, cancellation, and recovery behavior use the new backend code.
  • Verify Keycloak, token, group, and role configuration in each environment after deployment.
  • Regenerate or review generated project setup files if the project relies on Lex App initialization commands.