Required Fields

Description

Problems

Users need to enforce mandatory fields to ensure data consistency and integrity when creating or updating entities.

Implement a "Required Fields" feature that allows users to designate specific fields as mandatory across all entity creation and update processes.

NOTE: It is not possible to create Required Fields for Highlight database so far

Add Required switcher to the following field types:

Basic Text, URL, Email, Phone (blank string is a no value like null)
Number
Date
Single Select
Parent relation (many-to-one) for some cases and permissions:
- Example: Tasks must be created within shared projects (no orphan tasks). The current system allows users with entity creation capabilities to associate an entity with anything if they have update rights on at least one side. Anton proposes tightening the rule by requiring the user to have read permissions on the related entity as well, ensuring stricter control over entity associations Require capabilities on both ends to link/unlink entities
- Example: For Estimations, four Fields should be required: Name, Discipline (to-one relation), Quantity (number), Duration (number).
- Imitate State DB: there shouldn't be any cards without a state
- People: single user
🦄 OUT OF SCOPE: Support to-many relation Fields as required (tags, etc)
- People: multiple users
  - Example: make Owner required when feature is added
- Multi-select field
- Location field
❌ Formulas and Lookups CAN'T be required
❌ Required fields can not be selected for Highlight database

What to do if I am adding new entity on View and filter of Required field is set? Haha! → Set selected value in the filter

There are many places where we can create a new entity, so we should cover them all

If at least one required field in database, ALWAYS show New Quick Add popup on entity creation. Invoke New Quick Add modal popup for entity creation with required fields

New Quick Add
Invoke New Quick Add modal popup:
- Select text and create a new entity (not relevant for entities with names generated)
- Reference Selector
- Smart Folder in left menu
- Board View Axis, Timeline View groups
ALL VIEWS → ? we can pass context to form and set some values, like column/row/filter, etc.
Search

We can edit fields in many places, like Entity View, Views via inline edit, batch actions.

Views. When a user tries to remove a value for a required field, it shows red border and if new value is not provided, old value is still set if a user leaves a view

What about "create" API calls?
- Return some error with a message "Some required fields values are missing, here are required fields list: [field1, field2]"
- Handle required field errors

What to do if we import from CSV and some values for required fields are empty?
- ??? fail and show some error? → Send error to Inbox

:viktar-zhuk: Creating such fields for large databases will timeout. We need some minor tweaks for field-creator svc along the way.
- Set Required Fields Backend

Design for all cases

https://www.figma.com/design/JRmd7B9p7MPXFojD2fZuD1/PA---Views-%26-Search?node-id=12519-37592&t=dmC2T1GeK9KIpna6-1

The solution should work across all kinds of Views. One way to this is to use Form View (experimental) :

Perhaps, if a DB has required Fields, we should Force/push users add entities via Forms.

Another solution would be borrowing a technique from indirect context Views: