@nocobase/plugin-ai 2.2.0-alpha.1 → 2.2.0-alpha.11

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/advanced/nano-id.md

@@ -1,13 +1,113 @@
+---
+title: "Nano ID"
+description: "The Nano ID field generates short random unique identifiers."
+keywords: "Nano ID,nanoId,field,Field interface,NocoBase"
+---
+
 # Nano ID
 
 ## Introduction
 
-## Field configuration
+In NocoBase, **Nano ID** generates a short random unique identifier.
+
+It is suitable for short links, public codes, and external reference IDs that need a shorter string identifier. Use Snowflake ID for an ordinary internal primary key, or Sequence for readable business codes.
+
+## Use cases
+
+Nano ID fields are suitable for these business scenarios:
+
+- Short links
+- Public codes
+- External reference IDs
+- Short random record identifiers
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Nano ID** to create this field.
+
+![Configure a Nano ID field](https://static-docs.nocobase.com/20240512173225.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Nano ID uses `nanoId`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Share ID`, `Public ID`, or `Short identifier`. 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. Nano ID 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. It is normally generated by the system and does not need manual 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 Nano ID field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `nanoId`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Displays a generated Nano ID value in pages. |
+| Filtering | Supports text and identifier filters where supported by the data source. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | It is normally generated by the system and does not need manual 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 Nano ID field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Nano ID 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
+
+Nano ID fields are suitable for short public and external identifiers.
 
+![Use a Nano ID field in a page](https://static-docs.nocobase.com/20260710151321.png)
 
-![20240512173225](https://static-docs.nocobase.com/20240512173225.png)
 
+| Scenario | Use |
+| --- | --- |
+| Details block | Display a short identifier. |
+| Table block | Display and filter identifiers. |
+| APIs | Use Nano ID values in public URLs or references. |
+| Workflows | Pass short identifiers to external systems. |
 
-## 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.
+- [UUID](./uuid.md) - Generate UUID identifiers.
+- [Sequence](../../../field-sequence/index.md) - Generate readable sequence numbers.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/advanced/snowflake-id.md

@@ -1,9 +1,113 @@
-# Snowflake ID (53-bit)
+---
+title: "Snowflake ID"
+description: "The Snowflake ID field generates unique identifiers and is commonly used as the default primary key for NocoBase general collections."
+keywords: "Snowflake ID,snowflakeId,field,Field interface,NocoBase"
+---
+
+# Snowflake ID
 
 ## Introduction
 
-https://github.com/nocobase/nocobase/tree/main/packages/core/snowflake-id
+In NocoBase, **Snowflake ID** generates a unique identifier.
+
+Snowflake ID is a common primary-key type for the default ID field in NocoBase general collections. It is suitable as an internal record unique identifier. Use Sequence or a business-code field when an external system needs a readable number.
+
+## Use cases
+
+Snowflake ID fields are suitable for these business scenarios:
+
+- Internal record primary keys
+- Default IDs for general collections
+- Stable record unique identifiers
+- High-volume internal identifiers
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Snowflake ID** to create this field.
+
+![Configure a Snowflake ID field](https://static-docs.nocobase.com/20251209204217.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Snowflake ID uses `snowflakeId`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `ID`, `Record ID`, or `Internal ID`. 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. Snowflake ID uses `bigInt` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. It is normally generated by the system and does not need manual 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 Snowflake ID field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `snowflakeId`. |
+| Default Field type | `bigInt`. |
+| Available Field types | `bigInt`. |
+| Page component | Displays a generated Snowflake ID value in pages. |
+| Filtering | Supports identifier and numerical filters where supported by the data source. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | It is normally generated by the system and does not need manual 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 Snowflake ID field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Snowflake ID 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
+
+Snowflake ID fields are suitable for internal record identification and primary keys.
+
+![Use a Snowflake ID field in a page](https://static-docs.nocobase.com/20260710145423.png)
+
+
+| Scenario | Use |
+| --- | --- |
+| Details block | Display an internal record ID. |
+| Table block | Display and filter IDs. |
+| APIs | Use stable internal identifiers. |
+| Workflows | Locate records reliably in business logic. |
 
-## Field configuration
+## Related links
 
-![20251209204217](https://static-docs.nocobase.com/20251209204217.png)
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [UUID](./uuid.md) - Generate UUID identifiers.
+- [Sequence](../../../field-sequence/index.md) - Generate readable sequence numbers.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/advanced/sort.md

@@ -1,21 +1,5 @@
 ---
-title: Collection selector
+title: "Sort field"
+description: "Sort field type configuration for recording the order of records."
+keywords: "Sort field,sort,field type,record ordering,NocoBase"
 ---
-
-# Collection selector
-
-The Collection selector field is a special field type that allows users to select one or more collections from a predefined list. This field type is very useful in scenarios where you need to dynamically reference different collections, such as building configurable reports, dashboards, or complex applications that need to change data sources based on user selection.
-
-## Use Cases
-
-### Dynamic Report Generation
-
-In a report generation module, users may need to select a collection from multiple collections as the data source for the report. By using the Collection selector, users can easily select the desired collection, and the system will dynamically generate the report based on the user's selection.
-
-### Configurable Dashboards
-
-In a dashboard application, users can customize the data displayed on the dashboard. The Collection selector allows users to choose the collections they are interested in, thereby displaying charts and statistical data from different data sources on the dashboard.
-
-### Flexible Data Import/Export Tools
-
-When developing a generic data import or export tool, you can use the Collection selector to let users specify the collection to operate on. This way, the same tool can be used to process data from any collection in the system, greatly improving the tool's reusability.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/advanced/uuid.md

@@ -1,13 +1,113 @@
+---
+title: "UUID"
+description: "The UUID field generates UUID unique identifiers for cross-system and public references."
+keywords: "UUID,uuid,field,Field interface,NocoBase"
+---
+
 # UUID
 
 ## Introduction
 
-## Field configuration
+In NocoBase, **UUID** generates a UUID unique identifier.
+
+It is suitable for cross-system synchronization, public API identifiers, and import or export. It exposes data scale less readily than an auto-incrementing ID. Use Snowflake ID for ordinary internal primary keys, or Nano ID and Sequence when you need shorter or readable identifiers.
+
+## Use cases
+
+UUID fields are suitable for these business scenarios:
+
+- Cross-system synchronization IDs
+- Public API identifiers
+- Import and export identifiers
+- Non-sequential public record IDs
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **UUID** to create this field.
+
+![Configure a UUID field](https://static-docs.nocobase.com/20240512173354.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. UUID uses `uuid`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `UUID`, `External identifier`, or `Public ID`. 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. UUID uses `uuid` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. It is normally generated by the system and does not need manual 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 UUID field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `uuid`. |
+| Default Field type | `uuid`. |
+| Available Field types | `uuid`. |
+| Page component | Displays a generated UUID value in pages. |
+| Filtering | Supports text and identifier filters where supported by the data source. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | It is normally generated by the system and does not need manual 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 UUID field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a UUID 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
+
+UUID fields are suitable for system integration and public record identification.
 
+![Use a UUID field in a page](https://static-docs.nocobase.com/20260710145759.png)
 
-![20240512173354](https://static-docs.nocobase.com/20240512173354.png)
 
+| Scenario | Use |
+| --- | --- |
+| Details block | Display a record UUID. |
+| Table block | Display and filter identifiers. |
+| APIs | Use UUID values as external identifiers. |
+| Workflows | Pass stable identifiers to external systems. |
 
-## 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.
+- [Nano ID](./nano-id.md) - Generate short random identifiers.
+- [Sequence](../../../field-sequence/index.md) - Generate readable sequence numbers.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/associations/index.md

@@ -1,12 +1,48 @@
-# Relationship Fields
+---
+title: "Relation fields"
+description: "Relation fields create connections between collections. They support one-to-one, one-to-many, many-to-one, many-to-many, and many-to-many array relations."
+keywords: "relation field,BelongsTo,HasMany,O2O,O2M,M2O,M2M,association field,NocoBase"
+---
 
-In NocoBase, relationship fields are not actual fields but are used to establish connections between collections. This concept is equivalent to relationships in relational databases.
+# Relation fields
 
-In relational databases, the most common types of relationships include the following:
+In NocoBase, **relation fields** create connections between different collections. They let one record refer to records in another collection, such as an order related to a customer, a task related to an owner, or a student related to courses.
 
-- [One-to-One](./o2o/index.md): Each entity in two collections corresponds to only one entity in the other collection. This type of relationship is usually used to store different aspects of an entity in separate collections to reduce redundancy and improve data consistency.
-- [One-to-Many](./o2m/index.md): Each entity in one collection can be associated with multiple entities in another collection. This is one of the most common relationship types. For example, one author can write multiple articles, but each article can have only one author.
-- [Many-to-One](./m2o/index.md): Multiple entities in one collection can be associated with one entity in another collection. This type of relationship is also common in data modeling. For instance, multiple students can belong to the same class.
-- [Many-to-Many](./m2m/index.md): Multiple entities in two collections can be associated with each other. This type of relationship typically requires an intermediary collection to record the associations between the entities. For example, the relationship between students and courses—a student can enroll in multiple courses, and a course can have multiple students.
+Relation fields differ from ordinary fields. Ordinary fields usually correspond to actual database columns and store values such as text, numbers, and dates. Relation fields store collection-connection configuration and the keys used to locate related records. In the main database, creating a relation field can create the necessary relation configuration. In external databases, relations are usually based on existing primary keys, foreign keys, or unique fields and do not automatically modify the external database schema.
 
-These types of relationships play an important role in database design and data modeling, helping to describe complex real-world relationships and data structures.
+## Choose a relation type
+
+Common relation types are as follows:
+
+| Relation type | Use cases |
+| --- | --- |
+| [One-to-one](./o2o/index.md) | One record is related to only one record in another collection, such as an employee related to one onboarding profile. |
+| [One-to-many](./o2m/index.md) | One record is related to multiple records in another collection, such as a customer related to multiple orders. |
+| [Many-to-one](./m2o/index.md) | Multiple records are related to the same target record, such as multiple orders related to the same customer. |
+| [Many-to-many](./m2m/index.md) | Multiple records in both collections can be related to each other, such as students and courses. |
+| [Many-to-many (array)](../../../field-m2m-array/index.md) | Stores multiple target-record identifiers in an array field. Suitable when an existing schema already stores relation values in an array. |
+
+Use business semantics as the default decision rule: use many-to-one when the current record belongs to only one target record; use one-to-many when the current record needs to show multiple records in the target collection; use many-to-many when both sides can relate to multiple records.
+
+## Configuration points
+
+When configuring a relation field, confirm the following:
+
+- Target collection: the collection to relate to
+- Relation type: one-to-one, one-to-many, many-to-one, many-to-many, or many-to-many array
+- Relation keys: the fields that locate records on both sides, usually primary keys, foreign keys, or unique fields
+- Title field: the field displayed by default for related records in selectors and blocks
+
+:::warning Note
+
+Relation fields in external databases are primarily relation metadata stored by NocoBase. Adding a relation field does not automatically create actual foreign keys, indexes, or join tables in the external database. If you need database-level foreign-key constraints, create them in the database first, then synchronize and configure fields in NocoBase.
+
+:::
+
+## Related links
+
+- [One-to-one](./o2o/index.md) - Configure a one-to-one relation field.
+- [One-to-many](./o2m/index.md) - Configure a one-to-many relation field.
+- [Many-to-one](./m2o/index.md) - Configure a many-to-one relation field.
+- [Many-to-many](./m2m/index.md) - Configure a many-to-many relation field.
+- [Many-to-many (array)](../../../field-m2m-array/index.md) - Configure an array-based many-to-many relation.

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

@@ -1,13 +1,111 @@
+---
+title: "Color"
+description: "The Color field stores color values for interface display and configuration."
+keywords: "Color,color,field,Field interface,NocoBase"
+---
+
 # Color
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Color** field stores a color value.
+
+It is suitable for status colors, tag colors, chart colors, and other display configuration. Use a normal Input field when you need to store an arbitrary short text value instead of a color.
+
+## Use cases
+
+Color fields are suitable for these business scenarios:
+
+- Status colors and tag colors
+- Chart and dashboard colors
+- Category and menu colors
+- Brand or theme configuration values
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Color** to create this field.
+
+![Configure a Color field](https://static-docs.nocobase.com/20240512175956.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Color uses `color`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Status color`, `Tag color`, or `Chart color`. 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. Color 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 Color field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `color`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Uses a color picker 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 Color field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Color 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
+
+Color fields are suitable for display configuration and visual indicators.
 
+![Use a Color field in a page](https://static-docs.nocobase.com/20260709225444.png)
 
-![20240512175956](https://static-docs.nocobase.com/20240512175956.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Select a color value. |
+| Details block | Display the configured color. |
+| Table block | Display and sort color values. |
+| Charts and interface configuration | Use a color value for visual presentation. |
 
-## 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.