What's the difference between classic view and superform for connected tables inside a form?

In Jestor, when setting up a connected table inside a form, there are two view options: "classic," which keeps the traditional box-style layout, and "superform," which displays the connected record as an editable mini-form, with blocks, colors, and customizable fields.

The problem of packing too much information into one card

Companies dealing with many connected records — orders with items, projects with stages, clients with contracts — struggle to display everything in an organized way inside a single card. Each layer of information gets lost in generic tables.

The problem gets worse when the team needs to edit that connected record without leaving the main form, jumping between screens just to update a single field.

How to choose between classic and superform

Open the connected table block inside the superform editor.
Choose "classic" when you only need a simple listing, with no advanced styling.
Choose "superform" when you want a richer layout, with organized fields and colors.
In superform, add conditionals to display fields only in certain scenarios.
Style the record's action buttons, if you're using superform.

Feature	Classic	Superform
Visual customization	Standard, no advanced styling	Colors, blocks, and customizable buttons
Editing the record	Requires opening the full record	Inline editing, right in the form
Conditionals	Not available	Available, field by field
Best for	Simple listings	Rich layout with few essential fields

Why choose Jestor?

Jestor applies the same conditional, permission, and block-organization features already used in main forms to the superform, so the learning curve is close to zero for anyone who already builds forms on the platform.

Frequently Asked Questions

Does superform fully replace the classic view? No, both remain available; the choice depends on how much visual customization the process requires.

Can I add conditionals inside the superform? Yes, you can display fields conditionally, such as showing a piece of information only when another field reaches a certain value.

Does superform work in both public and creation forms? Yes, the feature is available in both the public form and the record-creation form.

Reference Video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and see how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize