Changelog

LEX App v2.1.3

Note added retrospectively: the redesigned interface described below shipped in this release
and was rolled back in v2.1.4. If you are running v2.1.4 or later, the appearance
described here is not what you have. See v2.1.4 for what was kept.

Main changes

A redesigned interface

  • New design and theme. A refreshed look throughout — cleaner tables, forms and navigation, in both light and dark mode.
  • New sidebar. A full-height side navigation with a consolidated header bar: more room for your data, and models are easier to find.
  • Settings panel. Each user can tune how a grid looks and behaves — row density, which columns are pinned, the column layout, and whether the column filter toggle is shown. Your choices are remembered.
  • Less cluttered tables. Columns fit themselves to their content, date columns show the date only with the full timestamp on hover, and the toolbar is tidier — more data, less noise.
  • Number formatting per column. Choose how a numeric column displays — a plain number, a currency (€, $, £, CHF, ¥) or a percentage — and how many decimals to show. Set it once and it stays.
  • Linked records as chips. A column pointing at another record shows that record's name as a compact chip rather than a bare number, and the text can be customised.
  • Colour-coded calculation status, pinned left. Calculation status appears as a coloured pill — in progress, success, error — pinned to the left of the grid so it stays visible while you scroll sideways.
  • Actions pinned right. The per-row actions column is pinned to the right, so the controls stay put however wide the table gets. Calculate moved in beside them, keeping calculation controls together.
  • Optional selection column. The row-selection checkboxes can be shown or hidden, so they only appear when you actually need them.
  • Quick-edit panel. Editing opens a sliding panel that is part of the grid surface — quicker than a separate page, and you keep your place in the data.
  • Current / As-of / History. One control switches a table between its live values, a point-in-time view of the data as it was at any past moment, and the full history of changes.
  • Calculation logs that read like a document. The log view lists every section in a left-hand pane so you can jump straight to one, and sections fold away so you can focus on a single phase. Severity badges and a copy button round it out.

Elsewhere

  • Linked records show names, not numbers, everywhere. Rows served by the API now carry a display name alongside each link to another record, taken from the model's own description. This is what lets the grid show a name where it previously showed an identifier, and it is additive — the underlying identifier is untouched, so filtering and editing on it are unaffected.

Optimizations

  • Live-updating tables. Open grids refresh themselves when the underlying data changes, with no manual refresh.
  • Faithful PDF export. Downloading a calculation log as PDF now renders as the on-screen view does — headings, tables and code blocks intact. Reported by a customer; the previous export lost markdown structure.
  • Lower memory on heavy operations. Data-heavy calculations use noticeably less memory per record, and large fan-out calculations stream their work instead of assembling everything up front, so big runs stay inside a bounded memory budget rather than exhausting the instance.

Bug fixes

  • Timezone shifts. Edit times, calculation-log times, history and the point-in-time view could appear shifted by a couple of hours. Times display correctly in your local timezone and time-travel lands on the right moment. (Partly addressed here; fully resolved in v2.1.4 — see its upgrade note.)
  • A removed file stays removed. Clearing a file field and saving no longer brings the old file back.
  • Duplicate records on save. Double-clicking Save could create two copies of a record. Save is guarded, so a record is created once.
  • Validation errors are shown. When a save was rejected by a validation rule the form could fail without saying why. The message now appears on the field it belongs to.
  • Number and yes/no column filters. Filtering a numeric or true/false column could fail to load the list. These filters work correctly.
  • Exports respect your sort order. A spreadsheet export comes out in the same order as the grid on screen.
  • Exports respect field permissions. Columns you are not permitted to see are no longer included in exports.
  • New table views open immediately. A list view you just created opens straight away instead of staying inactive.
  • Safer content rendering. Process-flow output is sanitised before display, closing a path where crafted content could run in the browser.
  • History stays intact. Historical records can no longer be deleted, protecting the audit trail.

Upgrade note: no migrations and no configuration changes.

Correction (added retrospectively). This note originally said the release added a nullable column for the calculation-log sections. That column shipped in v2.1.1; there is no migration in this release.