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

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

@@ -1,13 +1,111 @@
+---
+title: "Polygon"
+description: "The Polygon field stores a geographic area such as a sales territory, delivery area, or risk area."
+keywords: "Polygon,polygon,field,Field interface,NocoBase"
+---
+
 # Polygon
 
 ## Introduction
 
-## Field Configuration
+In NocoBase, the **Polygon** field stores a geographic area.
+
+It is suitable for sales territories, delivery areas, risk areas, and other polygonal geographic data.
+
+## Use cases
+
+Polygon fields are suitable for these business scenarios:
+
+- Sales territories
+- Delivery areas
+- Risk areas
+- Other polygonal geographic data
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Polygon** to create this field.
+
+![Configure a Polygon field](https://static-docs.nocobase.com/20240512181547.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Polygon uses `polygon`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Sales territory`, `Delivery area`, or `Risk area`. 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. Polygon uses `polygon` 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 base validation such as required. |
+| 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 Polygon field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `polygon`. |
+| Default Field type | `polygon`. |
+| Available Field types | `polygon`. |
+| Page component | Uses a map-drawing component in edit mode. |
+| Filtering | Spatial filtering depends on map-plugin and data-source capabilities. |
+| Sorting | It is usually not used for sorting. |
+| Validation | Supports base validation such as required. |
+
+## 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 Polygon field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Polygon 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
+
+Polygon fields are suitable for map display and area-based geographic data.
 
+![Use a Polygon field in a page](https://static-docs.nocobase.com/20260710145218.png)
 
-![20240512181547](https://static-docs.nocobase.com/20240512181547.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Draw or edit a polygon on a map. |
+| Details block | Display a geographic area. |
+| Map and geographic blocks | Show an area in a map context. |
+| Workflows and APIs | Pass polygon data to business logic. |
 
-## 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/index.md

@@ -1,36 +1,82 @@
-# Collection Fields
+---
+title: "Fields"
+description: "Learn the purpose of NocoBase fields, how to create and manage them, field-type use cases, creating fields from pages, and field mapping for main and external data sources."
+keywords: "field,Field type,Field interface,field mapping,title field,unique constraint,relation field,NocoBase"
+---
 
-## Interface Types of Fields
+# Fields
 
-NocoBase classifies fields into the following categories from the Interface perspective:
+## Introduction
 
+In NocoBase, a **Field** is a business attribute in a [Collection](../collection.md). It describes the information that can be stored in a record and how that information is entered, displayed, filtered, and used in business logic.
 
-![20240512110352](https://static-docs.nocobase.com/20240512110352.png)
+| Definition | Description |
+| --- | --- |
+| Data it stores | For example, text, numbers, dates, files, statuses, relations, or JSON. |
+| How pages use it | For example, Input, DatePicker, Select, attachment upload, or a relation selector for data entry and display. |
+| How it participates in business capabilities | Fields are used by blocks, filters, sorting, permissions, workflows, APIs, and data import and export. |
 
+A Field can correspond to:
 
-## Field Data Types
+- An actual database column in the main database
+- An existing database column in an external database
+- A field in a database view
+- A field returned by an SQL query
+- A field in a REST API response
+- A relation field, system field, or virtual field in a collection
 
-Each Field Interface has a default data type. For instance, for fields with the Interface as a Number, the default data type is double, but it can also be float, decimal, etc. The data types currently supported are:
+Think of a Field as one attribute of a business object. For example:
 
+| Business object | Fields |
+| --- | --- |
+| Customer | Customer name, mobile number, customer level, and owner |
+| Order | Order number, order amount, order status, and customer |
+| Contract | Contract name, signing date, contract attachments, and approval status |
+| Task | Task title, due date, priority, and assignee |
+| File | File name, size, MIME type, and URL |
 
-![20240512103733](https://static-docs.nocobase.com/20240512103733.png)
+## Use cases
 
+The following field categories help you decide which kind of field to choose. Open the relevant field documentation for configuration, type mapping, and cautions.
 
-## Field Type Mapping
+| Field category | Use cases |
+| --- | --- |
+| [Text fields](./basic/input.md) | Store names, numbers, descriptions, contact information, links, and similar content. |
+| [Rich text fields](./media/rich-text.md) | Store longer content such as article bodies, documentation, processing plans, and code snippets. |
+| [Number fields](./basic/number.md) | Store quantities, amounts, scores, percentages, and other numerical values. |
+| [Date and time fields](./datetime/index.md) | Store timestamps, dates, times, and timestamps from external systems. |
+| [Status and option fields](./choices/select.md) | Store values from a fixed range, such as enabled state, order status, customer level, and customer tags. |
+| [Attachment fields](./media/field-attachment.md) | Upload files or store external-file addresses. |
+| [Relation fields](./associations/index.md) | Express connections between collections, such as an order belonging to a customer, a customer having orders, or a user being related to roles. |
+| [Identifier and code fields](./advanced/uuid.md) | Store internal primary keys, synchronized external IDs, public-access identifiers, and business codes. |
+| [Geometric fields](./geometric/point.md) | Store spatial or geographic information, such as store locations, delivery routes, and service areas. |
+| [System fields](./system-info/created-at.md) | Store system information maintained by NocoBase or the database, such as IDs, creation time, creator, and update time. |
+| [Other fields](./advanced/json.md) | Handle field needs that do not directly belong to other categories, such as sorting, formulas, and JSON. |
 
-The process for adding new fields to the main database is as follows:
+## Field interface types
 
-1. Select the Interface type
-2. Configure the optional data type for the current Interface
+NocoBase groups fields into the following categories from the Field interface perspective:
 
+![Field interface types](https://static-docs.nocobase.com/20240512110352.png)
 
-![20240512172416](https://static-docs.nocobase.com/20240512172416.png)
+## Field data types
 
+Each Field interface has a default data type. For example, a field with the Number interface uses `double` by default, but it can also use `float`, `decimal`, and other data types. The currently supported data types are:
 
-The process for field mapping from external data sources is:
+![Field data types](https://static-docs.nocobase.com/20240512103733.png)
 
-1. Automatically map the corresponding data type (Field type) and UI type (Field Interface) based on the field type of the external database.
-2. Modify to a more suitable data type and Interface type as needed
+## Field type mapping
 
+The process for adding a field to a main data source is:
 
-![20240512172759](https://static-docs.nocobase.com/20240512172759.png)
+1. Select a Field interface type.
+2. Configure a data type available for the selected interface.
+
+![Create a field in a main data source](https://static-docs.nocobase.com/20240512172416.png)
+
+The field-mapping process for an external data source is:
+
+1. Map the external database column type automatically to the corresponding Field type and UI type (Field interface).
+2. Change to a more suitable data type and interface type when needed.
+
+![Map a field from an external data source](https://static-docs.nocobase.com/20240512172759.png)

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

@@ -1,13 +1,113 @@
+---
+title: "Markdown"
+description: "The Markdown field stores Markdown-formatted content such as documentation, processing plans, and knowledge-base articles."
+keywords: "Markdown,markdown,field,Field interface,NocoBase"
+---
+
 # Markdown
 
 ## Introduction
 
-## Field configuration
+In NocoBase, **Markdown** stores Markdown-formatted content.
+
+It is suitable for documentation, processing plans, knowledge-base content, and change records. It stores text and renders it as Markdown in pages. For a WYSIWYG editing experience, use Rich text or Markdown Vditor.
+
+## Use cases
+
+Markdown fields are suitable for these business scenarios:
+
+- Documentation
+- Processing plans
+- Knowledge-base content
+- Change records
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Markdown** to create this field.
+
+![Configure a Markdown field](https://static-docs.nocobase.com/20240512172236.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Markdown uses `markdown`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Documentation`, `Processing plan`, or `Body`. 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. Markdown uses `text` 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 length 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 Markdown field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `markdown`. |
+| Default Field type | `text`. |
+| Available Field types | `text`. |
+| Page component | Uses a Markdown editor or text input in edit mode and renders Markdown in read mode. |
+| Filtering | Supports text filters where supported by the data source. |
+| Sorting | Supports sorting in Table blocks where supported by the data source. |
+| Validation | Supports length 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 Markdown field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Markdown 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
+
+Markdown fields are suitable for formatted textual content in forms and details.
 
+![Use a Markdown field in a page](https://static-docs.nocobase.com/20260710152021.png)
 
-![20240512181311](https://static-docs.nocobase.com/20240512181311.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter or edit Markdown content. |
+| Details block | Render Markdown content. |
+| Table block | Display a shortened Markdown value. |
+| Workflows and APIs | Pass Markdown text to business logic. |
 
-## 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.
+- [Rich text](./rich-text.md) - Store WYSIWYG formatted content.
+- [Markdown Vditor](../../../field-markdown-vditor/index.md) - Use a Vditor Markdown editor.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/media/rich-text.md

@@ -1,13 +1,113 @@
-# Rich Text
+---
+title: "Rich text"
+description: "The Rich text field stores formatted content such as announcements, articles, email templates, and documentation."
+keywords: "Rich text,richText,field,Field interface,NocoBase"
+---
+
+# Rich text
 
 ## Introduction
 
-## Field configuration
+In NocoBase, **Rich text** stores formatted content.
+
+It is suitable for announcement bodies, article bodies, email templates, and documentation. It provides an editing experience closer to WYSIWYG. Use Markdown or Markdown Vditor when the team prefers controllable plain-text formatting.
+
+## Use cases
+
+Rich text fields are suitable for these business scenarios:
+
+- Announcement bodies
+- Article bodies
+- Email templates
+- Product and help documentation
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Rich text** to create this field.
+
+![Configure a Rich text field](https://static-docs.nocobase.com/20240512172307.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Rich text uses `richText`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Announcement body`, `Email template`, or `Product description`. 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. Rich text uses `text` 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 length 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 Rich text field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `richText`. |
+| Default Field type | `text`. |
+| Available Field types | `text`. |
+| Page component | Uses a rich-text editor in edit mode and renders formatted content in read mode. |
+| Filtering | Supports text filters where supported by the data source. |
+| Sorting | Supports sorting in Table blocks where supported by the data source. |
+| Validation | Supports length 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 Rich text field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Rich 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.
+
+:::
+
+## Use in pages
+
+Rich text fields are suitable for WYSIWYG formatted content in forms and details.
 
+![Use a Rich text field in a page](https://static-docs.nocobase.com/20260710152106.png)
 
-![20240512181002](https://static-docs.nocobase.com/20240512181002.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter or edit formatted content. |
+| Details block | Render rich-text content. |
+| Table block | Display a shortened rich-text value. |
+| Workflows and APIs | Pass formatted content to business logic. |
 
-## 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.
+- [Markdown](./markdown.md) - Store Markdown-formatted content.
+- [Markdown Vditor](../../../field-markdown-vditor/index.md) - Use a Vditor Markdown editor.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/system-info/created-at.md

@@ -1,13 +1,113 @@
-# Created At
+---
+title: "Created at"
+description: "The Created at field automatically records when a record was created."
+keywords: "Created at,createdAt,field,Field interface,NocoBase"
+---
+
+# Created at
 
 ## Introduction
 
-## Field configuration
+In NocoBase, **Created at** automatically records the time when a record was created.
+
+It is usually generated by preset fields and is suitable for sorting, filtering, auditing, workflow conditions, and data statistics. For a manually entered business date, such as a signing or expiry date, use Date or DateTime.
+
+## Use cases
+
+Created at fields are suitable for these business scenarios:
+
+- Audit and creation-time tracking
+- Sorting and filtering by creation time
+- Workflow conditions
+- Data statistics
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Created at** to create this field.
+
+![Configure a Created at field](https://static-docs.nocobase.com/20240512174347.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Created at uses `createdAt`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Created at` or `Creation 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. Created at uses `date` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Is maintained automatically and normally does not require 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 Created at field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `createdAt`. |
+| Default Field type | `date`. |
+| Available Field types | `date`. |
+| Page component | Is maintained automatically by the system. |
+| Filtering | Supports date-time filtering. |
+| Sorting | Supports chronological sorting in Table blocks. |
+| Validation | Is maintained automatically and normally does not require 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 Created at field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Created at 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
+
+Created at fields are suitable for audit, filters, and workflow conditions.
 
+![Use a Created at field in a page](https://static-docs.nocobase.com/20260710153223.png)
 
-![20240512174347](https://static-docs.nocobase.com/20240512174347.png)
 
+| Scenario | Use |
+| --- | --- |
+| Table block | Display, sort, and filter records by creation time. |
+| Details block | Display the record creation time. |
+| Filter block | Filter records by creation date. |
+| Workflows and permissions | Use the creation time in 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.
+- [Date](../datetime/date.md) - Store a manually entered business date.
+- [DateTime](../datetime/datetime.md) - Store a manually entered business date and time.