Lex App v2.0.0rc48
Lex App v2.0.0rc48
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 hardens identity, token, and permission handling across backend request paths.
This release reduces setup and initialization friction for Lex App projects.
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.
- Token, session, and permission context handling is more consistent across backend request types.
- Initialization behavior is more tolerant of project-specific client names, deployment targets, and generated run configuration.
Fixed
- Reduced ambiguous calculation outcomes caused by worker shutdown, callback handling, deadlocks, or dispatch timing.
- Reduced authentication edge cases around Keycloak, API tokens, role/group lookup, and user-context enrichment.
- Reduced setup failures caused by missing generated files, client naming differences, or incomplete environment assumptions.
Improved
- Long-running calculations are easier to supervise and recover after runtime interruption.
- Permission-aware behavior is more predictable for role-based business applications.
Maintenance
- Kept the distributable backend package aligned with the current v2 runtime expectations.
Upgrade Impact
- 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.
- Rebuild application images or virtual environments so dependency and packaging changes are actually used.
