@nocobase/plugin-ai 2.3.0-alpha.1 → 3.0.0-alpha.2

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/choices/select.md

@@ -1,13 +1,111 @@
-# Single select
+---
+title: "Select"
+description: "The Select field stores one value from a fixed option set, such as status, level, or priority."
+keywords: "Select,select,field,Field interface,NocoBase"
+---
+
+# Select
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Select** field stores one selected option value.
+
+It is suitable for order statuses, customer levels, priorities, and other values from a fixed range. Use Multiple select when a record can contain more than one option.
+
+## Use cases
+
+Select fields are suitable for these business scenarios:
+
+- Order status
+- Customer level
+- Priority
+- Type and category values
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Select** to create this field.
+
+![Configure a Select field](https://static-docs.nocobase.com/20240512180203.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Select uses `select`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Order status`, `Customer level`, or `Priority`. 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. Select 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 and configured option values. |
+| 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 Select field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `select`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Uses a Select component in edit mode. |
+| Filtering | Supports option filters such as equals, does not equal, is empty, and is not empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports required validation and configured option values. |
+
+## 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 Select field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Select 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
+
+Select fields are suitable for fixed business states and single-choice data entry.
 
+![Use a Select field in a page](https://static-docs.nocobase.com/20260709225912.png)
 
-![20240512180203](https://static-docs.nocobase.com/20240512180203.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Select one option. |
+| Table block | Display, sort, and filter option values. |
+| Details block | Display the selected option. |
+| Workflows and permissions | Use the selected value in business 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.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/datetime/date.md

@@ -1,13 +1,111 @@
+---
+title: "Date"
+description: "The Date field stores a calendar date without requiring a time value."
+keywords: "Date,dateOnly,field,Field interface,NocoBase"
+---
+
 # Date
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Date** field stores a calendar date.
+
+It is suitable for signing dates, birthdays, due dates, and other values where only the date matters. Use DateTime when the time of day is also required.
+
+## Use cases
+
+Date fields are suitable for these business scenarios:
+
+- Signing dates and effective dates
+- Birthdays and anniversary dates
+- Due dates and planned dates
+- Business dates without a time of day
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Date** to create this field.
+
+![Configure a Date field](https://static-docs.nocobase.com/20260709232951.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Date uses `dateOnly`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Signing date`, `Due date`, or `Birthday`. 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. Date uses `dateOnly` 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 date-range 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 Date field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `dateOnly`. |
+| Default Field type | `dateOnly`. |
+| Available Field types | `dateOnly`, `date`. |
+| Page component | Uses a date picker in edit mode. |
+| Filtering | Supports date filters such as before, after, range, is empty, and is not empty. |
+| Sorting | Supports chronological sorting in Table blocks. |
+| Validation | Supports date-range 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 Date field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Date 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
+
+Date fields are suitable for date-only entry, display, and business conditions.
 
+![Use a Date field in a page](https://static-docs.nocobase.com/20260709232644.png)
 
-![20240512181142](https://static-docs.nocobase.com/20240512181142.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Select a date. |
+| Table block | Display, sort, and filter dates. |
+| Details block | Display a date value. |
+| Workflows and permissions | Use the date in business 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.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/datetime/datetime-without-tz.md

@@ -1,13 +1,111 @@
-# Datetime (without time zone)
+---
+title: "DateTime (without time zone)"
+description: "The DateTime (without time zone) field stores a local date and time without time-zone conversion."
+keywords: "DateTime (without time zone),datetimeNoTz,field,Field interface,NocoBase"
+---
+
+# DateTime (without time zone)
 
 ## Introduction
 
-## Field configuration
+In NocoBase, **DateTime (without time zone)** stores a local date and time without time-zone conversion.
+
+It is suitable for local schedules, business hours, and values that must remain unchanged as entered. Use DateTime when the same instant must be interpreted consistently across time zones.
+
+## Use cases
+
+DateTime (without time zone) fields are suitable for these business scenarios:
+
+- Local schedules and business hours
+- Local appointment times
+- Store opening and closing times with a date
+- Time values imported without time-zone data
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **DateTime (without time zone)** to create this field.
+
+![Configure a DateTime (without time zone) field](https://static-docs.nocobase.com/20260709232834.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. DateTime (without time zone) uses `datetimeNoTz`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Local schedule`, `Business time`, or `Appointment time`. 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. DateTime (without time zone) uses `datetimeNoTz` 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 date-range 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 DateTime (without time zone) field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `datetimeNoTz`. |
+| Default Field type | `datetimeNoTz`. |
+| Available Field types | `datetimeNoTz`. |
+| Page component | Uses a date-time picker in edit mode. |
+| Filtering | Supports date-time filters such as before, after, range, is empty, and is not empty. |
+| Sorting | Supports chronological sorting in Table blocks. |
+| Validation | Supports date-range 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 DateTime (without time zone) field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a DateTime (without time zone) 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
+
+DateTime (without time zone) fields are suitable for local schedules and business time values.
 
+![Use a DateTime (without time zone) field in a page](https://static-docs.nocobase.com/20260709232511.png)
 
-![20240512181142](https://static-docs.nocobase.com/20240512181142.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Select a local date and time. |
+| Table block | Display, sort, and filter local date-time values. |
+| Details block | Display a local time value. |
+| Workflows and permissions | Use the value in time-based 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.

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

@@ -1,13 +1,111 @@
-# Datetime (with time zone)
+---
+title: "DateTime"
+description: "The DateTime field stores date and time values with time-zone information."
+keywords: "DateTime,datetime,field,Field interface,NocoBase"
+---
+
+# DateTime
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **DateTime** field stores a date and time with time-zone information.
+
+It is suitable for event times, submission times, appointment times, and other time points that need consistent time-zone handling. Use DateTime (without time zone) when the value must remain a local time without conversion.
+
+## Use cases
+
+DateTime fields are suitable for these business scenarios:
+
+- Meeting and appointment times
+- Order submission and payment times
+- System event and operation times
+- Time points shared across time zones
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **DateTime** to create this field.
+
+![Configure a DateTime field](https://static-docs.nocobase.com/20240512181142.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. DateTime uses `datetime`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Meeting time`, `Submission time`, or `Appointment time`. 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. DateTime uses `datetimeTz` 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 date-range 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 DateTime field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `datetime`. |
+| Default Field type | `datetimeTz`. |
+| Available Field types | `datetimeTz`, `date`. |
+| Page component | Uses a date-time picker in edit mode. |
+| Filtering | Supports date-time filters such as before, after, range, is empty, and is not empty. |
+| Sorting | Supports chronological sorting in Table blocks. |
+| Validation | Supports date-range 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 DateTime field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a DateTime 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
+
+DateTime fields are suitable for event records, schedules, and time-based business conditions.
 
+![Use a DateTime field in a page](https://static-docs.nocobase.com/20260709232355.png)
 
-![20240512181142](https://static-docs.nocobase.com/20240512181142.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Select a date and time. |
+| Table block | Display, sort, and filter date-time values. |
+| Details block | Display the time of one record. |
+| Workflows and permissions | Use the value in time-based 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.

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

@@ -1,72 +1,78 @@
-# DateTime Field Types
+---
+title: "Overview"
+description: "Date and time field types: with and without time zone, date, time, and Unix timestamp, including NocoBase, MySQL, and PostgreSQL type mappings."
+keywords: "date and time,DateTime,time field,with time zone,without time zone,Unix timestamp,NocoBase"
+---
 
-DateTime field types can be categorized as follows:
+# Overview
 
-- **DateTime (with Time Zone):** These values are standardized to UTC (Coordinated Universal Time) and are subject to time zone adjustments when necessary.
-- **DateTime (without Time Zone):** This type stores date and time data without incorporating any time zone information.
-- **Date (without Time):** This format exclusively stores date information, omitting any time component.
-- **Time:** Stores only time information, excluding the date.
-- **Unix Timestamp:** This type represents the number of seconds that have elapsed since January 1, 1970, and is stored as a Unix timestamp.
+## Date and time field types
 
-Here are examples for each DateTime-related field type:
+Date and time field types include:
 
-| **Field Type**               | **Example Value**            | **Description**                                       |
-|------------------------------|------------------------------|-------------------------------------------------------|
-| DateTime (with Time Zone)     | 2024-08-24T07:30:00.000Z     | Converted to UTC and can be adjusted for time zones    |
-| DateTime (without Time Zone)  | 2024-08-24 15:30:00          | Stores date and time without time zone considerations  |
-| Date (without Time)           | 2024-08-24                   | Captures only the date, with no time information       |
-| Time                          | 15:30:00                     | Captures only the time, excluding any date details     |
-| Unix Timestamp                | 1724437800                   | Represents seconds since 1970-01-01 00:00:00 UTC       |
+- **DateTime (with time zone)** - Date-time values are normalized to Coordinated Universal Time (UTC) and converted between time zones when needed
+- **DateTime (without time zone)** - Stores a date and time without time-zone information
+- **Date (without time)** - Stores only the date, without a time component
+- **Time** - Stores only the time, without a date component
+- **Unix timestamp** - Stores a Unix timestamp, usually the number of seconds since January 1, 1970
 
-## Data Source Comparisons
+Examples of date-related field types:
 
-Below is a comparison table for NocoBase, MySQL, and PostgreSQL:
+| Field type | Example value | Description |
+| --- | --- | --- |
+| DateTime (with time zone) | 2024-08-24T07:30:00.000Z | A date-time value normalized to UTC. |
+| DateTime (without time zone) | 2024-08-24 15:30:00 | A date-time value without time-zone information. |
+| Date (without time) | 2024-08-24 | Stores only date information. |
+| Time | 15:30:00 | Stores only time information. |
+| Unix timestamp | 1724437800 | Seconds elapsed since 00:00:00 UTC on January 1, 1970. |
 
-| **Field Type**                | **NocoBase**               | **MySQL**                  | **PostgreSQL**                         |
-|-------------------------------|----------------------------|----------------------------|----------------------------------------|
-| DateTime (with Time Zone)      | Datetime with timezone     | TIMESTAMP<br/> DATETIME    | TIMESTAMP WITH TIME ZONE               |
-| DateTime (without Time Zone)   | Datetime without timezone  | DATETIME                   | TIMESTAMP WITHOUT TIME ZONE            |
-| Date (without Time)            | Date                       | DATE                       | DATE                                   |
-| Time                           | Time                       | TIME                       | TIME WITHOUT TIME ZONE                 |
-| Unix Timestamp                 | Unix timestamp             | INTEGER<br/>BIGINT         | INTEGER<br/>BIGINT                     |
-| Time (with Time Zone)          | -                          | -                          | TIME WITH TIME ZONE                    |
+## Data-source mapping
 
-**Note:**
-- MySQL’s TIMESTAMP type covers a range between `1970-01-01 00:00:01 UTC` and `2038-01-19 03:14:07 UTC`. For dates and times outside this range, it is recommended to use DATETIME or BIGINT to store Unix timestamps.
+The following table compares NocoBase, MySQL, and PostgreSQL types:
 
-## DateTime Storage Processing Workflow
+| Field type | NocoBase | MySQL | PostgreSQL |
+| --- | --- | --- | --- |
+| DateTime (with time zone) | Datetime with timezone | TIMESTAMP<br/>DATETIME | TIMESTAMP WITH TIME ZONE |
+| DateTime (without time zone) | Datetime without timezone | DATETIME | TIMESTAMP WITHOUT TIME ZONE |
+| Date (without time) | Date | DATE | DATE |
+| Time | Time | TIME | TIME WITHOUT TIME ZONE |
+| Unix timestamp | Unix timestamp | INTEGER<br/>BIGINT | INTEGER<br/>BIGINT |
+| Time (with time zone) | - | - | TIME WITH TIME ZONE |
 
-### With Time Zone
+Notes:
 
-This includes `DateTime (with Time Zone)` and `Unix Timestamp`.
+- MySQL `TIMESTAMP` supports values from UTC `1970-01-01 00:00:01` through `2038-01-19 03:14:07`. Outside this range, use DATETIME or BIGINT to store a Unix timestamp.
 
+## Date and time storage flow
 
-![20240824191933](https://static-docs.nocobase.com/20240824191933.png)
+### With time zone
 
+This flow includes DateTime (without time zone) and Unix timestamp handling.
 
-**Note:**
-- To accommodate a broader range of dates, NocoBase uses the DATETIME type in MySQL for DateTime (with Time Zone) fields. The date value stored is converted based on the server's TZ environment variable, meaning that if the TZ environment variable changes, the stored DateTime value will also change.
-- Since there is a time zone difference between UTC and local time, directly displaying the raw UTC value could lead to user confusion.
+![Date and time storage flow](https://static-docs.nocobase.com/20240824191933.png)
 
-### Without Time Zone
+Notes:
 
+- To support a wider range of values, the NocoBase DateTime (with time zone) field uses DATETIME in MySQL. The stored date value is converted according to the server `TZ` environment variable. If the `TZ` environment variable changes, stored date-time values can change.
+- UTC and local time differ by time zone. Displaying a raw UTC value directly can confuse users.
 
-![20240824185600](https://static-docs.nocobase.com/20240824185600.png)
+### Without time zone
 
+![DateTime without time zone storage flow](https://static-docs.nocobase.com/20240824185600.png)
 
 ## UTC
 
-UTC (Coordinated Universal Time) is the global time standard used to coordinate and synchronize time worldwide. It is a highly precise time standard, maintained by atomic clocks, and synchronized with the Earth's rotation.
+UTC (Coordinated Universal Time) is the global time standard used to coordinate and unify time around the world. It is a high-precision time standard based on atomic clocks and synchronized with the time of the Earth's rotation.
 
-The difference between UTC and local time can cause confusion when displaying raw UTC values. For example:
+UTC and local time differ by time zone. Displaying a raw UTC value directly can confuse users. For example:
 
-| **Time Zone**   | **DateTime**                    |
-|-----------------|---------------------------------|
-| UTC             | 2024-08-24T07:30:00.000Z        |
-| UTC+8           | 2024-08-24 15:30:00             |
-| UTC+5           | 2024-08-24 12:30:00             |
-| UTC-5           | 2024-08-24 02:30:00             |
-| UTC+0           | 2024-08-24 07:30:00             |
-| UTC-6           | 2024-08-23 01:30:00             |
+| Time zone | Date and time |
+| --- | --- |
+| UTC | 2024-08-24T07:30:00.000Z |
+| China Standard Time (UTC+8) | 2024-08-24 15:30:00 |
+| UTC+5 | 2024-08-24 12:30:00 |
+| UTC-5 | 2024-08-24 02:30:00 |
+| UK time (UTC+0) | 2024-08-24 07:30:00 |
+| Central Time (UTC-6) | 2024-08-23 01:30:00 |
 
-These different times all correspond to the same moment, merely expressed in various time zones.
+These values represent the same moment in time; only the time zone differs.