@nocobase/plugin-ai 2.2.0-beta.9 → 3.0.0-alpha.1

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/email.md

@@ -1,13 +1,113 @@
+---
+title: "Email"
+description: "The Email field stores email addresses and provides email-format validation."
+keywords: "Email,email,field,Field interface,NocoBase"
+---
+
 # Email
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Email** field stores email addresses.
+
+It is suitable for customer, employee, and supplier email addresses. Compared with a normal Input field, it provides clearer email semantics and format validation. Use [Input](./input.md) when the content is not an email address.
+
+## Use cases
+
+Email fields are suitable for these business scenarios:
+
+- Customer and contact email addresses
+- Employee and sign-in contact email addresses
+- Supplier and service email addresses
+- Notification recipient addresses
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Email** to create this field.
+
+![Configure a Email field](https://static-docs.nocobase.com/20240512175609.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Email uses `email`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Customer email`, `Contact email`, or `Recipient email`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Email uses `string` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports email-format and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Email field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `email`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Uses an Input component with email-format validation in edit mode. |
+| Filtering | Supports text filters such as contains, equals, is empty, and is not empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports email-format and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Email field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Email field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Email fields are suitable for forms, details, and notification flows.
 
+![Use a Email field in a page](https://static-docs.nocobase.com/20260709224700.png)
 
-![20240512175609](https://static-docs.nocobase.com/20240512175609.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter an email address. |
+| Details block | Display an email address. |
+| Filter block | Filter records by email address. |
+| Workflows and notifications | Use the value as an email-notification recipient. |
 
-## Example
+## Related links
 
-To be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Input](./input.md) - Store ordinary short text.
+- [Phone](./phone.md) - Store phone numbers.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/icon.md

@@ -1,13 +1,111 @@
+---
+title: "Icon"
+description: "The Icon field stores icon identifiers for menus, categories, statuses, and other interface elements."
+keywords: "Icon,icon,field,Field interface,NocoBase"
+---
+
 # Icon
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Icon** field stores icon identifiers.
+
+It is suitable for menu icons, category icons, status icons, and other visual labels. Use a normal Input field when you need to store an arbitrary text value instead of an icon.
+
+## Use cases
+
+Icon fields are suitable for these business scenarios:
+
+- Menu and navigation icons
+- Category and classification icons
+- Status and label icons
+- Visual identification for business records
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Icon** to create this field.
+
+![Configure a Icon field](https://static-docs.nocobase.com/20240512180027.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Icon uses `icon`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Menu icon`, `Category icon`, or `Status icon`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Icon uses `string` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Icon field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `icon`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Uses an icon selector in edit mode. |
+| Filtering | Supports text-value filters such as equals, is empty, and is not empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Icon field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Icon field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Icon fields are suitable for visual configuration and record identification.
 
+![Use a Icon field in a page](https://static-docs.nocobase.com/20260709225630.png)
 
-![20240512180027](https://static-docs.nocobase.com/20240512180027.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Select an icon. |
+| Details block | Display the selected icon. |
+| Table block | Display icon values in a list. |
+| Interface configuration | Use the icon as a visual identifier. |
 
-## Example
+## Related links
 
-To be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/input.md

@@ -1,22 +1,126 @@
-# Single Line Text
+---
+title: "Single line text"
+description: "The Single line text field stores short text such as names, codes, titles, and contacts. It uses the string type and Input interface by default."
+keywords: "Single line text,input,text field,string,Field interface,NocoBase"
+---
+
+# Single line text
 
 ## Introduction
 
-## Field Configuration
+In NocoBase, **Single line text** is the most common text field. It is suitable for short text that fits on one line, such as customer names, order numbers, contacts, address summaries, and external-system identifiers.
+
+Single line text uses the `Input` interface and the `string` Field type by default. It can be used as a title field and can participate in filters, sorting, permission rules, workflow conditions, and API queries.
+
+When content might contain line breaks or be long, use [Textarea](./textarea.md) by default. When content has a fixed format, such as an email address, phone number, or URL, use the corresponding specialized field first.
+
+## Use cases
+
+Single line text is suitable for these business scenarios:
+
+- Customer names, company names, and contact names
+- Order numbers, contract numbers, and project numbers
+- Task titles, work-order titles, and article titles
+- External-system IDs, synchronization numbers, and business codes
+- Short text such as cities, address summaries, and store names
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Single line text** to create the field.
+
+![Create a Single line text field](https://static-docs.nocobase.com/20240512163555.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Single line text uses `input` and an Input component for entry and display. |
+| Field display name | The name displayed for the field, such as `Customer name`, `Order number`, or `Task title`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Single line text uses `string` by default and can also use `uid`. Use `string` for ordinary short text. |
+| Automatically remove heading and tailing spaces | Removes leading and trailing spaces automatically. Suitable for names, codes, and titles where leading or trailing spaces should not be retained. |
+| Default value | The default value. When a new record has no value, NocoBase can fill the default text automatically. |
+| Primary | Makes the field a primary key. Available only when creating a field in the main database; ordinary business text is not recommended as a primary key. |
+| Unique | A unique constraint. Suitable for text values that cannot repeat, such as order numbers, contract numbers, and external-system IDs. |
+| Validation rules | Validation rules. You can limit minimum length, maximum length, fixed length, or a regular expression. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Single line text field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `input`. |
+| Default Field type | `string`. |
+| Available Field types | `string`, `uid`. |
+| Page component | Uses an `Input` component in edit mode. |
+| Title field | Can be used as a collection title field. It is suitable to set fields such as `Customer name`, `Order number`, or `Task title` as the title field. |
+| Sorting | Supports sorting in Table blocks. |
+| Filtering | Supports text filters such as contains, does not contain, equals, does not equal, is empty, and is not empty. |
+| Validation | Supports minimum length, maximum length, fixed length, regular-expression, and other validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they display and are used in NocoBase, such as the display name, description, default value, validation rules, or automatic removal of leading and trailing spaces.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface. For example, short-text database columns such as `varchar` and `char` can be mapped to a Single line text field.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Automatically remove heading and tailing spaces | Yes | Controls whether leading and trailing spaces are removed when saving. |
+| Default value | Yes | Adjusts the default text for new records. |
+| Unique | Conditional | Available when creating a field in the main database. Adding it can fail if existing data already contains duplicate values. |
+| Validation rules | Yes | Adjusts length, format, or regular-expression validation. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Single line text field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Single line text field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
 
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
 
-![20240512163555](https://static-docs.nocobase.com/20240512163555.png)
+:::
 
+## Use in pages
 
-## Interface Configuration
+Single line text fields can be used in most data blocks and form scenarios.
 
-### Edit Mode
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter or edit short text such as a customer name, order number, or task title. |
+| Table block | Display, sort, and filter short text. Long values are truncated in tables according to interface configuration. |
+| Details block | Display text information for one record. |
+| Filter block | Use the field as a query condition, such as filtering by customer name, code, or title. |
+| Relation field display | When a Single line text field is a title field, relation fields preferentially display this text when selecting a record. |
+| Workflows and permissions | Use it in conditions, such as whether an order number is empty or a customer name contains a keyword. |
 
+### Edit mode
 
-![20240512164001](https://static-docs.nocobase.com/20240512164001.png)
+In edit mode, Single line text uses an Input component.
 
+![Single line text edit mode](https://static-docs.nocobase.com/20240512164001.png)
 
-### Read-only Mode
+### Read mode
 
+In read mode, Single line text is displayed as ordinary text.
 
-![20240512164138](https://static-docs.nocobase.com/20240512164138.png)
+![Single line text read mode](https://static-docs.nocobase.com/20240512164138.png)

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/integer.md

@@ -1,13 +1,112 @@
+---
+title: "Integer"
+description: "The Integer field stores whole-number values such as quantities, headcounts, and days."
+keywords: "Integer,integer,field,Field interface,NocoBase"
+---
+
 # Integer
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Integer** field stores whole-number values.
+
+It is suitable for quantities, headcounts, delay days, and other values without decimal places. Use Number when the business value needs decimals.
+
+## Use cases
+
+Integer fields are suitable for these business scenarios:
+
+- Inventory quantity and order quantity
+- Headcount and number of participants
+- Delay days and service duration
+- Sequence numbers and counting values
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Integer** to create this field.
+
+![Configure a Integer field](https://static-docs.nocobase.com/20240512175723.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Integer uses `integer`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Quantity`, `Headcount`, or `Delay days`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Integer uses `integer` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports minimum, maximum, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Integer field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `integer`. |
+| Default Field type | `integer`. |
+| Available Field types | `integer`, `bigInt`. |
+| Page component | Uses a number input in edit mode. |
+| Filtering | Supports numerical filters such as greater than, less than, equals, and is empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports minimum, maximum, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Integer field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Integer field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Integer fields are suitable for numerical entry, statistics, filters, and conditions.
 
+![Use a Integer field in a page](https://static-docs.nocobase.com/20260709224913.png)
 
-![20240512175723](https://static-docs.nocobase.com/20240512175723.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter a whole-number value. |
+| Table block | Display, sort, and filter numerical values. |
+| Details block | Display a whole-number value. |
+| Workflows and permissions | Use the value in numerical conditions. |
 
-## Example
+## Related links
 
-to be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Number](./number.md) - Store decimal numerical values.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/number.md

@@ -1,13 +1,112 @@
+---
+title: "Number"
+description: "The Number field stores decimal values such as amounts, scores, and weights."
+keywords: "Number,number,field,Field interface,NocoBase"
+---
+
 # Number
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Number** field stores numerical values that can include decimals.
+
+It is suitable for order amounts, scores, weights, and other decimal values. For monetary values that require exact decimal precision, use `decimal`.
+
+## Use cases
+
+Number fields are suitable for these business scenarios:
+
+- Order amounts and budgets
+- Scores and ratings
+- Weight, length, and other measurements
+- Statistical indicators and calculated values
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Number** to create this field.
+
+![Configure a Number field](https://static-docs.nocobase.com/20240512175752.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Number uses `number`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Order amount`, `Score`, or `Weight`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Number uses `double` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports minimum, maximum, precision, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Number field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `number`. |
+| Default Field type | `double`. |
+| Available Field types | `double`, `float`, `decimal`. |
+| Page component | Uses a number input in edit mode. |
+| Filtering | Supports numerical filters such as greater than, less than, equals, and is empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports minimum, maximum, precision, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Number field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Number field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Number fields are suitable for numerical entry, calculation, statistics, and conditions.
 
+![Use a Number field in a page](https://static-docs.nocobase.com/20260709225103.png)
 
-![20240512175752](https://static-docs.nocobase.com/20240512175752.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter a numerical value. |
+| Table block | Display, sort, and filter numerical values. |
+| Details block | Display a numerical value. |
+| Workflows and permissions | Use the value in numerical conditions and calculations. |
 
-## Example
+## Related links
 
-To be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Percent](./percent.md) - Store percentage values.