Lex App v2.0.0rc195
Lex App v2.0.0rc195
Release Notes
This release improves the audit and calculation-log path so operational records are easier to trust during calculations, imports, and background processing.
Users and administrators get a clearer explanation trail when a calculation, data change, or background process changes application state.
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
- Additional setup and initialization support for project bootstrap and environment-specific configuration.
Changed
- 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.
- Initialization behavior is more tolerant of project-specific client names, deployment targets, and generated run configuration.
Fixed
- 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.
- Reduced setup failures caused by missing generated files, client naming differences, or incomplete environment assumptions.
Improved
- Operational traceability is stronger for administrators investigating calculation and data-change outcomes.
- Permission-aware behavior is more predictable for role-based business applications.
Upgrade Impact
- Apply database migrations before running history, audit, or calculation-heavy workflows after upgrading.
- 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.
