Classic view or superform: what's the difference for connected tables inside a form

Classic view displays connected records in the traditional block format, already used in Jestor for a long time. Superform presents those same connected records as a form within a form, with fields arranged side by side and support for its own conditionals.

Why do two different formats exist?

Every process has different visualization needs. Some teams prefer the classic format, already familiar and straightforward. Others need more control — like showing or hiding fields based on a condition — something only superform allows within connected records.

Having both options avoids forcing everyone to migrate to a new standard when the old format already suits the process well.

How to choose between the two formats

In the connected table block's edit view, find the view option.
Select "classic" to keep the traditional block format.
Select "superform" to get a form within a form, with customizable fields and conditions.
Adjust color, layout, and buttons based on the format you chose.

Format	Key difference
Classic	Traditional, already familiar format
Superform	Organized fields and its own conditionals

Why choose Jestor

Flexibility to choose the view format that best fits each process.
Conditionals applicable directly inside connected records in superform mode.
Color and layout customization available in both models.

FAQ

Can I switch from classic to superform after it's already set up?

Yes, you can switch between the two formats at any time in the block's edit view.

Does superform work on public forms?

Yes, the same feature is available both on creation forms and on public forms.

Do conditionals work in both formats?

The specific conditionals inside the connected record are a superform feature. Learn more at jestor.com.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How Do You Set a Different Homepage for Each Role as Soon as the User Logs In?

In Jestor, when editing a role, you can paste the link to a specific page (like a dashboard) into the homepage field, so that every user with that role lands directly there as soon as they log in. Why this improves the user experience Without this setting, everyone would land

What's the Access Difference Between a Member-Type User and a Builder-Type User?

In Jestor, a member-type user is meant for anyone who just uses already-configured processes, while a builder has access to create and edit tables, apps, automations, and the account's structure. Why separate these two access levels Not everyone on the team should be able to change

Why Does Grouping Tables and Apps for the Same Process Into the Same Folder Make Maintenance Easier?

In Jestor, grouping tables and applications for the same process into a single folder makes it quick to find everything related to a specific Kanban or flow, saving you from wasting time hunting for scattered pieces across the platform. Why folder organization avoids clutter Just like an unorganized computer desktop,

Can You Duplicate an Entire Application, With All Its Elements, Right From the Action Bar?

Yes. In Jestor, the action bar (opened with Ctrl+K or Cmd+K) lets you clone an entire application, with every element it contains, just by choosing the source app and giving the copy a new name. Why cloning from the action bar is faster Manually rebuilding an app from