Changelog

LEX App v2.2.0

You can try the new design and the new Streamlit features locally. To use them on a
production instance you also need the latest frontend image — the latest lex-app on its
own is not enough. Contact us if you want it set up for you.

Two things define this release: the interface is the redesigned one, and Streamlit
dashboards can use LEX's own controls instead of imitating them.

The redesigned interface shipped briefly in v2.1.3 and was withdrawn in v2.1.4. It
returns here, with the problems reported against it resolved. Every release from v2.1.4
to v2.1.11 ran the previous design, so if you are upgrading from one of those,
everything below is new to you.


Main changes

A redesigned interface

  • One design system. Navy surfaces, teal for anything actionable, ocean for links —
    one set of design tokens, not per-screen styling. Dashboards are generated from the same
    tokens and fonts, so they match exactly.
  • A full-height side navigation. It owns the left edge, and the page controls move into
    one header row above your data instead of a separate top bar. Models sit in folders that
    expand in place, the one you are in marked with a teal pill. It opens collapsed,
    remembers which folders you left open, and can be searched by name or by where a model
    sits.
  • Less chrome around the data. Fewer boxes, borders that carry information rather than
    decorate, a tighter toolbar, and the breadcrumb folded into the row it belongs to.
  • Light and dark reach every window. A theme change applies across every LEX tab and
    window, and into any embedded dashboard, without a reload.
  • Creating and editing open over your list. Both open in a drawer on the same layout,
    so you keep your place and your filters instead of navigating to a full page and back.
  • A record leads its own page. The record's own content is at the top. Id,
    Created At, Edited At, Created By and Edited By — previously the first five rows,
    because that is the order the metadata arrives in — are collapsed into a
    Record details section.

Tables

  • A settings panel per table, saved per user. A gear controls row density; the status
    bar, header wrapping and whether date columns show the time; and the column filter
    button, row-index column, and pinning of the selection and calculation-status columns.
    Changes are kept as you make them, on that table, with no Save step.
  • Column formats, chosen in the browser. Any numeric column can be shown as a number,
    a currency or a percentage, with a currency and decimal count of your choosing. Where the
    application declares a format, the dropdown names it — Default (currency) — and your
    choice sits on top. Reset to backend defaults hands the column back.
  • Linked records read as cards. A column pointing at another record shows its name as a
    compact card, and hovering previews the record behind it. Which fields appear is the
    application's decision, through a preview serializer, and the preview honours the same
    read permissions as the record.
  • Actions and status stay put. The actions column is pinned right and the calculation
    status pill pinned left, however wide the table gets.
  • Select a range, like a spreadsheet. Drag across cells; the status bar shows the live
    sum, average and count of the selection.
  • Export from the toolbar. Export used to live only in the right-click menu. There is
    now a button above every table, and selection is the contract: nothing selected exports
    the table as shown, with filters, sort, grouping and pivot carried in; rows selected
    exports exactly those. The tooltip names which.
  • The column filter control is on the header by default — filtering was previously
    reachable only from the column menu.

Before

Now

Filtering an amount

Text matching — 100 also matched 1000 and 2100, and no range could be expressed

Greater than, less than, between

Filtering a date-and-time column

A date meant midnight exactly, so a day returned almost nothing

A date means that whole day; tick Match a specific time for an instant

Filtering a yes/no column

Failed

Works

Grouping with a total

Group names appeared, totals were blank

The totals appear

Exporting

Right-click, and know the menu is there

A button above every table

A field with fixed values

A free-text box that accepted anything

A dropdown of the values it allows

A rejected save

"Update failed"

The reason it was rejected

Calculation logs

  • A log reads like a document. Sections are listed in a pane you can jump from, and
    fold away so you can hold one phase of a run on screen.
  • Export a step, or a step and everything under it. Two downloads, one PDF each: what
    this step did, or what happened underneath it. The header states the scope, so a
    partial export cannot be mistaken for a whole run.
  • A traceback you can work with. Search inside it, and copy all of it in one action.
  • An empty table says which kind of empty it is — nothing here yet, or nothing matching
    your filters.

Dashboards

Before. A dashboard could embed a whole LEX view with lex_view, and no less than that.
Anything narrower — a button to run one calculation, its status, its log — you rebuilt in
Streamlit against the API, or sent people into LEX to do it.

Now. The controls themselves are available, one call each:

lex_calculation("quarter", pk)            # the Calculate button, its status, its log
lex_calculation_log("quarter", pk)        # the log, streaming live
lex_calculation_log_tree("quarter", pk)   # the execution tree of a finished run

lex_view still embeds a whole view, and lex_widgets() groups several controls into one
frame. A flat lex_* call embeds one thing; lex_widgets() embeds several. Nothing
existing was renamed.

Because these are the real controls and not copies:

  • Status is live. A calculation started in a dashboard reports progress and completion
    as it happens, and the record refreshes when it finishes.
  • The log streams, rather than being something you open once the run has ended.
  • The dashboard looks like LEX — your logo, identity and log out in the sidebar, the
    same palette and fonts, and no duplicated navigation when LEX frames the page.
  • Light and dark stay in step, in both directions, without a reload.
  • A dashboard left open keeps working. Sessions renew in the background.

Optimizations

  • Loading is dramatically cheaper. The interface was served with instructions
    forbidding the browser to keep any copy of it, so every reload re-downloaded all of it
    and every embedded frame downloaded its own — about 24 MB per load for a page with three
    dashboard widgets, 86 MB with thirteen. Assets are now cached for a year and shared
    between a page and its frames.
  • Dashboard widgets load a fraction of what they did. A widget frame no longer pulls in
    the whole application to draw one control — 6.3 MB down to 1.6 MB — and several widgets
    share one runtime instead of starting one each. Frames also load without waiting to be
    scrolled into view.

Bug fixes

  • Amount columns filter as numbers. Numeric columns were reported to the interface as
    text, so filtering matched characters — 100 also matched 1000 and 2100 — and
    greater than, less than and between were not offered.
  • A date filter matches the day you picked. Filtering a date-and-time column by a date
    sent midnight exactly, so a day's records returned almost nothing. A date now means the
    whole day, with an explicit option for an exact time.
  • Yes/no column filters work. Filtering one used to fail outright.
  • Group totals appear. Grouping with a total showed the group names and blank totals,
    while an export of the same view rendered them.
  • Fields with a fixed set of values get a dropdown, instead of a free-text box that
    accepted anything.
  • Required fields are marked. Whether a field was reported as required depended on its
    type, so a required text field could look optional and fail only on Save.
  • A rejected save says why. A save refused for a bad value reported "Update failed",
    leaving you to find which field among twenty it meant. It now carries the reason.
  • Saved views stop losing each other. Creating a second view could silently delete the
    first. default and application-defined views are now read-only: they cannot be
    overwritten, deleted, or shadowed by a preset of the same name.
  • Creating a view is discoverable. The view dropdown says how, before you have to
    guess.
  • Times you type are stored as the time you meant, and exports agree with the screen.
    This completes the timezone work announced in v2.1.4, whose interface half had not
    shipped.

Security

User records no longer carry the stored password. Any signed-in account could read any
other account's stored password data through the API, including an administrator's —
verified on a clean instance, with the least-privileged account reading the most-privileged
one. The user record now serves an explicit list of display fields rather than everything
the model holds.

Passwords are stored in a form that is not directly reversible, so this was not an
immediate compromise, but it should not have been readable and we recommend upgrading
rather than deferring. To be thorough, have administrators change their passwords after
upgrading.


Upgrade note

There is no migration in this release, and no configuration or dependency changes. Two
things decide whether you should take it:

  • The new design and Streamlit features need the latest frontend image. They work
    locally as soon as you upgrade. A production instance needs that image too — the latest
    lex-app on its own is not enough. Contact us if you want it set up.
  • Streamlit 1.58 or later is required for light/dark sync. Below that, dashboards run
    normally but cannot follow the app's theme. lex streamlit says so at launch instead of
    leaving it looking like a bug.

If your administrators' passwords have not changed recently, see the security note above.