Which Fields in a Registration Form Should Be Required, and Which Can Be Optional
In Jestor, the practical rule for deciding required fields is simple: information essential for the process to move forward — like a supplier's name, email, and phone — tends to be required, while internal control data, like a description, can be optional.
Why doesn't every field need to be required?
Making everything required locks the form in any situation where a specific piece of data isn't available at the moment, even when that doesn't stop the process from moving forward.
How to decide between required and optional?
| Field type | Example | Required? |
|---|---|---|
| Essential to the process | Name, email | Yes |
| Important but skippable | Phone | Can be optional, depending on the process |
| Internal control | Description field | Usually optional |
Why choose Jestor to design balanced registration forms?
Jestor lets you mark, field by field, whether it's required, giving the team full control over which pieces of information truly block saving a record and which are just supplementary.
What happens if I try to save without filling out a required field?
The system won't allow saving and indicates that specific field needs to be filled in.
Can an optional field become required later?
Yes, the required setting can be changed at any time in the field's editing options.
Is there a maximum number of required fields in a table?
No limit is mentioned; the decision is about what's truly essential for that process.
Video Tutorial: Step by Step
Check out more practical tutorials on Jestor's YouTube channel.
Get to know Jestor
With Jestor, each registration field is required or optional based on what the process actually needs.
Get to know Jestor at jestor.com and see how to take your operation's efficiency to a new level.