Card view vs. superform: when to choose each display for a connected record?

In Jestor, a connected record can be displayed in two ways: as a card, with a cover image, background color, and summarized information, or as a superform, an editable mini-form with full blocks and fields.

When the wrong view gets in the way of a decision

Teams that just want to quickly identify "who is this record" struggle with screens full of fields; teams that need to edit right there struggle when they only have a read-only card.

You can even view multiple layers: a card can contain a superform, which in turn brings in another connected record inside it.

How to choose between the two options

Use the card view when the goal is just to visually identify the connected record.
Use superform when the process requires frequently editing that record.
Combine color, cover, and label on the card to make visual recognition easier.
Turn on "can update parent record" carefully, only when it makes sense.
Block the record from opening on the card, if you want to keep it read-only.

Feature	Card	Superform
Visuals	Cover, background color, and customizable label	Full form blocks
Editing the record	No, you need to open the record	Yes, inline editing
Can block opening	Yes	Not applicable
Multi-level connected records	Yes	Yes

Why choose Jestor?

Jestor lets you navigate multiple layers of connected records — like a client inside an order item — without leaving the original card, whether in card or superform format.

Frequently Asked Questions

Does superform let me edit the connected record directly? Yes, unlike the card, superform lets you edit fields without needing to open the full record.

Can I block a record from opening in card format? Yes, you can configure it so clicking the card doesn't open the connected record.

Can I bring in information from multiple levels of connected records? Yes, you can view the connected record of a connected record, layer after layer, in both card and superform.

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