Lex App v2.0.0rc57
Lex App v2.0.0rc57
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 hardens identity, token, and permission handling across backend request paths.
Changelog
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.
- Token, session, and permission context handling is more consistent across backend request types.
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 authentication edge cases around Keycloak, API tokens, role/group lookup, and user-context enrichment.
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.
- Verify Keycloak, token, group, and role configuration in each environment after deployment.
