ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
UIProduct Release1 min read

Forms that query, subscribe to several parents, run server events, fill the page

A tab may observe several parent tabs and join their selections, render query fields inside the form, dispatch named events that run server-side scripts, size itself to the screen, and fill the remaining height.

A form in an enterprise application is rarely one table. It is a tab that depends on two others, a filter the user types into, and a server-side rule that runs when something changes. These releases, spread over two years, gave the form definition those powers without code in the client.

Relationships

  • Several parents A tab can observe any number of parent tabs. Only subscriptions with a selected row contribute, and their conditions are joined with AND.
  • Query fields A tab can render filter inputs inside the form, so the user queries where they work.
  • Events to the server A client-side script dispatches a named event that runs server-side JavaScript in the cursor's own context, with its security and its transaction.

Layout

  • Screen size A form declares automatic, small, medium or large at 400, 800 and 1,200 pixels; sidebar row-link modes and a two-column aside style follow.
  • Fill the height A tab height of minus one fills the remaining band; one grid measured 705 pixels where its container had given it 53.
  • Hotkeys and scripts Keyboard navigation across tabs, box resizes batched in one transaction, and script tabs that render JSON, Python, Groovy and 4GL.

Each of these is one attribute in the form definition. The alternative is a page of client code per screen, which is what they replace.

On the platformFormsPlatform

All posts