Skip to main content

Field Basic Properties

After selecting the appropriate control based on the data type, you need to configure the basic properties of the field.
Each field includes the following properties:

  • Name
  • Required
  • Prevent duplicate input
  • Default value
  • Read-only
  • Hiden
  • Hide on create
  • Width
  • Color and style
  • Placeholder text
  • Field description
  • Field alias
  • Developer notes

Field Name and Name Visibility​

A clear field name helps users better understand the data.

In some cases, you may want to display only the field value without the label. You can hide the field name.

Default Value​

When creating a record, default values can automatically populate fields.
Supports both static and dynamic default values.
Learn more about field default values

Required​

If a field is marked as required, the record cannot be saved if the field is empty when editing, and a prompt will be shown.

However, required validation is not enforced when editing in table view, writing data via workflow or API, or importing from Excel.

Mandatory Validation on Write​

If only Required is selected, validation applies only in the record editing page.

If Mandatory Validation on Write is also enabled, validation applies to:

  • workflow writes
  • API writes
  • Excel imports

When the field is empty:

  • Workflow: execution stops with an error
  • Excel import: invalid rows are skipped; valid rows are imported
  • API: write fails and returns an error
  • Data integration: invalid data is skipped; valid data continues syncing (skipped data is not counted)

Prevent Duplicate Input​

For fields like employee ID or codes that must be unique:

If duplicate values are entered, the system will prompt and prevent saving.

This validation only applies to manual input. It does not apply to Excel imports or API writes. To enforce strict uniqueness, use Unique Index.

For member and relationship field types, if duplicate input is not allowed, already selected members or records cannot be selected again in other records.

Read-only​

Read-only fields cannot be edited when creating or editing records.
However, they can still be updated via workflow or modified to editable via business rules.

Hide​

Hidden fields are not visible when creating or editing records.
They can be used as intermediate fields for calculations without being shown to users.

Hide on Create​

When enabled, the field is hidden during record creation but visible when viewing or editing.

Example:
In an employee worksheet, the “Termination Date” field is not needed when creating a new employee, so it can be hidden on create.

Width​

Up to 4 fields can be displayed per row in a form.
Field width ranges from 1/4 width to full width.

Color and Style​

Field labels and values support customization of color, font size, and style.

Example:

To display field styles in views, enable Display on PC under
Configure View > Color.

When fields appear in relationship field, subform, or query records fields, all styles except label font size will apply.

Placeholder Text and Field Description​

These help users understand what information should be entered.

Example:

Field Description Display Modes

  • Auto
    Shown below the field when creating a record; hidden behind an icon when viewing

  • Icon
    Always hidden behind an icon; displayed on hover

  • Below
    Always displayed below the field

Field Alias​

Each field has a system-generated field ID (24-character alphanumeric), used in API integration and Word/Excel template printing.

Since field IDs are not human-readable and may change after duplicating an application, using a field alias improves usability.

Field aliases are auto-generated when a field is created and can be edited.

Auto-generation Rules for Field Alias

  • If the field name has ≤ 3 characters:
    Chinese characters are converted to full Pinyin

  • If > 3 characters:
    Chinese characters are converted to initials

  • Letters and numbers remain unchanged

  • If the name is purely numeric:
    Converted to the field type in English

  • Duplicate aliases will automatically get a suffix

Other Locations to Configure Field Alias

  • Form setting

  • API documentation

Reserved Field Aliases​

Field aliases must be unique. The following are system-reserved:

  • ownerid
  • autoid
  • caid
  • ctime
  • utime
  • uaid
  • daid
  • rowid
  • wfstatus
  • wfname
  • wfcuaids
  • wfrtime
  • wfftime
  • wfcaid
  • wfctime
  • wsid
  • status
  • sharerange
  • discussunreads
  • relations
  • unreads
  • keywords
  • users
  • owners
  • portal_status
  • portal_mobile
  • portal_email
  • portal_name
  • portal_avatar
  • portal_role
  • partal_regtime
  • portal_openid
  • partal_id

Field Notes​

Similar to code comments, fields notes are used for maintenance and are not visible when creating or viewing records.

Bulk Operations on Fields​

After selecting multiple fields, you can:

  • Delete or duplicate fields
  • Move fields to tabs
  • Reorder fields
  • Set properties such as Required, Read-only, Hiden, Hide on Create

Select fields individually, then apply bulk settings.
Click Save to apply changes.
Click Cancel to exit bulk mode before saving.

Why are some properties unavailable in bulk operations?​

Certain fields are inherently read-only and cannot be edited.
Therefore, some options like Required or Read-only may be unavailable in bulk selection and must be configured individually.

Was this document helpful?