Ladies and Gentlemen,
Lowcoder v2.7.6 is released!
This is a stability-and-polish release that also delivers a meaningful upgrade to Navigation (especially Mobile Nav Apps), plus several Table enhancements and platform improvements.
Highlights
-
Navigation upgrades (biggest theme of this release): new modes, richer styling, icons, and improved Mobile Nav App behavior.
It includes -
Tables get more capable: Better & more styling, new column controls, and a new password column type.
-
Enterprise identity: SCIM + SSO JIT provisioning support for Entra ID.
(Thank you very much @Sanjai1994 for this contribution!) -
Request-size configuration cleaned up for Node-Service: targeted fixes around max request sizing (Nginx / Node-Service), plus dependency updates to reduce deployment friction. Should now work fine with abbreviations like 50m 50mb or byte values.
New features
Navigation & Mobile Nav Apps
- Finally vertical and horizontal Multi-Level Navigation Components
- Improved mobile navigation
- floating hamburger-style mobile navigation
Navigation “Map mode” added (addresses #2021).
Disabled state support for navigation items (including submenu items).
Hamburger (drawer) mode for Mobile Nav App, including:
- Customizable hamburger/burger icon
- Close icon in the drawer + close icon customization
- Style customization for hamburger mode
Mode-aware property UI + segmented control for switching modes
Nav item icons (for items and submenus), submenu styling, extended nav item styles, and desktop nav positioning options.
Navigation component refactors and control consistency improvements (drawer placement controls, mode-based configuration UI).
Tables & data UX
Programmatic column visibility controls: exposed hideColumns / showColumns methods.
Button column styling support.
Custom CSS hooks: class/id identifiers for Table and TableLite.
Pagination styling improvements for tables.
Table download support.
Columns GUI/query: added search, filtering, and sorting to make large schemas easier to work with.
Password column type added.
Components & eventing
Markdown + tooltip support on events (issues #1827, #1937).
Added click/double-click events for the “lottie” component.
Tree component: added double-click event support.
runQuery custom component: added parameter support.
Identity & enterprise
SCIM + SSO Just‑In‑Time provisioning support for Entra ID.
Bug fixes
Navigation & layout
#2021: added Navigation map mode (delivered as a fix for the #2021 nav workstream).
#2021: fixed importing nav app data issues.
#2021: fixed disabled state handling for submenu items.
#2070: fixed an error while listing mobile nav apps.
#2076: fixed Mobile Nav App not passing params.
Fixed drawer rendering inside preview/app canvas.
Fixed drawer styles customization behavior.
#2086: fixed nav desktop app layout issues in publish mode.
Tables & data rendering
#1837: fixed table header border styling issues.
#1811: fixed table column alignment issues.
Fixed table header rendering across different table sizes.
#1840: fixed table theme sort color behavior.
Fixed column width behavior when adjusted by user.
#1795: removed unnecessary code (cleanup tied to the table download work).
Charts
Fixed PieChart default x-axis behavior.
Fixed chart theme handling.
Builder UX & general runtime behavior
#1065: fixed duplicates in continuous mode.
#1060: fixed URL opening to use the correct exposed .value.
#2039: fixed copyToClipboard utility content.
#2041: fixed form content default values behavior.
#1290: fixed stacking issues by adding a zIndex property where needed.
#1945: fixed handling to allow null values where previously blocked.
Fixed app header dropdown warning.
Fixed input blur event behavior.
Fixed tutorial modal reappearing unexpectedly.
Fixed UI of the select component inside the permission dialog.
Marketplace, configuration & deployment
#1732: fixed typos in secrets.yaml files.
#1968: added null checks when retrieving marketplace info.
Normalized max request size configuration for Nginx.
Updated Node-Service dependencies and MAX_REQUEST_SIZE behavior to resolve issues introduced by earlier request-size changes (now treated consistently and more predictably).