@nocobase/plugin-ai 2.1.0-alpha.45 → 2.1.0-alpha.47

package/dist/ai/docs/nocobase/solution/crm/changelog.md

@@ -8,7 +8,6 @@ This page documents the update history for the CRM solution. New entries are add
 
 **Backup files**:
 - [nocobase_crm_v2_backup_260406.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260406.nbdata)
-- [nocobase_crm_v2_sql_260406.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260406.zip)
 
 **Changes**:
 - Fixed table Summary aggregation display issue
@@ -24,7 +23,6 @@ This page documents the update history for the CRM solution. New entries are add
 
 **Backup files**:
 - [nocobase_crm_v2_backup_260327.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260327.nbdata)
-- [nocobase_crm_v2_sql_260327.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260327.zip)
 
 **Changes**:
 
@@ -52,7 +50,6 @@ This page documents the update history for the CRM solution. New entries are add
 
 **Backup files**:
 - nocobase_crm_v2_backup_260223.nbdata
-- nocobase_crm_v2_sql_260223.zip
 
 **Changes**:
 - Initial release of CRM 2.0

package/dist/ai/docs/nocobase/solution/crm/installation.md

@@ -2,15 +2,13 @@
 
 > The current version is deployed via **backup and restore**. In future versions, we may switch to **incremental migration** to make it easier to integrate the solution into your existing systems.
 
-To help you deploy the CRM 2.0 solution smoothly to your own NocoBase environment, we provide two restoration methods. Please choose the one that best suits your edition and technical background.
+> **The Backup Manager plugin is now open-source**: The "[Backup Manager](https://docs-cn.nocobase.com/handbook/backups)" plugin needed to restore the solution is now open-source and available to all editions (including the Community Edition). We recommend restoring directly via this plugin.
 
 Before you begin, please ensure:
 
 - You have a basic NocoBase running environment. For main system installation, please refer to the [official installation documentation](https://docs-cn.nocobase.com/welcome/getting-started/installation).
 - NocoBase version **v2.1.0-beta.2 or above**.
-- You have downloaded the corresponding CRM system files:
-  - **Backup file**: [nocobase_crm_v2_backup_260523.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260523.nbdata) - For Method 1
-  - **SQL file**: [nocobase_crm_v2_sql_260523.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260523.zip) - For Method 2
+- You have downloaded the CRM system backup file: [nocobase_crm_v2_backup_260523.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260523.nbdata)
 
 **Important Notes**:
 - This solution is built on **PostgreSQL 16**. Please ensure your environment uses PostgreSQL 16.
@@ -18,9 +16,9 @@ Before you begin, please ensure:
 
 ---
 
-## Method 1: Restore Using Backup Manager (Recommended for Pro/Enterprise Users)
+## Restore Using Backup Manager
 
-This method uses NocoBase's built-in "[Backup Manager](https://docs-cn.nocobase.com/handbook/backups)" (Pro/Enterprise Edition) plugin for one-click restoration. It is the simplest operation but has certain requirements for the environment and edition.
+This method uses NocoBase's built-in "[Backup Manager](https://docs-cn.nocobase.com/handbook/backups)" plugin for one-click restoration. It is the simplest operation. This plugin is now open-source and available to all editions (including the Community Edition).
 
 ### Key Characteristics
 
@@ -28,9 +26,8 @@ This method uses NocoBase's built-in "[Backup Manager](https://docs-cn.nocobase.
   1. **Convenient operation**: Completed within the UI, allowing for full restoration of all configurations including plugins.
   2. **Complete restoration**: **Able to restore all system files**, including print template files and files uploaded via file fields in collections, ensuring full functional integrity.
 * **Limitations**:
-  1. **Pro/Enterprise Edition only**: "Backup Manager" is an enterprise-level plugin available only to Pro/Enterprise users.
-  2. **Strict environment requirements**: Requires your database environment (version, case sensitivity settings, etc.) to be highly compatible with the environment where the backup was created.
-  3. **Plugin dependency**: If the solution includes commercial plugins not present in your local environment, the restoration will fail.
+  1. **Strict environment requirements**: Requires your database environment (version, case sensitivity settings, etc.) to be highly compatible with the environment where the backup was created.
+  2. **Plugin dependency**: If the solution includes commercial plugins not present in your local environment, the restoration will fail.
 
 ### Steps
 
@@ -69,69 +66,6 @@ Then use this image to start your NocoBase service.
 
 ---
 
-## Method 2: Direct SQL File Import (Universal, Better for Community Edition)
-
-This method restores data by directly operating on the database, bypassing the "Backup Manager" plugin, and therefore has no Pro/Enterprise Edition restrictions.
-
-### Key Characteristics
-
-* **Advantages**:
-  1. **No edition restrictions**: Suitable for all NocoBase users, including Community Edition.
-  2. **High compatibility**: Does not rely on the `dump` tool within the application; as long as you can connect to the database, you can operate.
-  3. **High fault tolerance**: If the solution includes commercial plugins you do not have, the related features will not be enabled, but it will not affect the normal use of other features, and the application can start successfully.
-* **Limitations**:
-  1. **Requires database operation skills**: Users need basic database operation skills, such as how to execute a `.sql` file.
-  2. **System file loss**: **This method will lose all system files**, including print template files and files uploaded via file fields in collections.
-
-### Steps
-
-**Step 1: Prepare a clean database**
-
-Prepare a brand new, empty database for the data you are about to import.
-
-**Step 2: Import the `.sql` file into the database**
-
-Obtain the downloaded database file (usually in `.sql` format) and import its content into the database you prepared in the previous step. There are several ways to execute this, depending on your environment:
-
-* **Option A: Via server command line (using Docker as an example)**
-  If you use Docker to install NocoBase and the database, you can upload the `.sql` file to the server and then use the `docker exec` command to perform the import. Assuming your PostgreSQL container is named `my-nocobase-db` and the filename is `nocobase_crm_v2_sql_260523.sql`:
-
-  ```bash
-  # Copy the sql file into the container
-  docker cp nocobase_crm_v2_sql_260523.sql my-nocobase-db:/tmp/
-  # Enter the container and execute the import command
-  docker exec -it my-nocobase-db psql -U nocobase -d nocobase -f /tmp/nocobase_crm_v2_sql_260523.sql
-  ```
-* **Option B: Via a remote database client (Navicat, etc.)**
-  If your database port is exposed, you can use any graphical database client (such as Navicat, DBeaver, pgAdmin, etc.) to connect to the database, then:
-  1. Right-click the target database.
-  2. Select "Run SQL File" or "Execute SQL Script".
-  3. Select the downloaded `.sql` file and execute.
-
-**Step 3: Connect to the database and start the application**
-
-Configure your NocoBase startup parameters (such as environment variables `DB_HOST`, `DB_PORT`, `DB_DATABASE`, `DB_USER`, `DB_PASSWORD`, etc.) to point to the database where you just imported the data. Then, start the NocoBase service normally.
-
-### Notes
-
-* **Database permissions**: This method requires you to have an account and password that can directly operate on the database.
-* **Plugin status**: After a successful import, although the data for commercial plugins included in the system exists, if you have not installed and enabled the corresponding plugins locally, the related features will not be displayed or usable, but this will not cause the application to crash.
-
----
-
-## Summary and Comparison
-
-| Feature | Method 1: Backup Manager | Method 2: Direct SQL Import |
-| :-------------- | :--------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------- |
-| **Applicable Users** | **Pro/Enterprise Edition** users | **All users** (including Community Edition) |
-| **Ease of Use** | ⭐⭐⭐⭐⭐ (Very simple, UI operation) | ⭐⭐⭐ (Requires basic database knowledge) |
-| **Environment Requirements** | **Strict**, database and system versions must be highly compatible | **General**, requires database compatibility |
-| **Plugin Dependency** | **Strong dependency**, plugins are validated during restoration; missing any plugin will cause **restoration failure**. | **Features strongly depend on plugins**. Data can be imported independently, and the system will have basic functionality. However, if corresponding plugins are missing, related features will be **completely unusable**. |
-| **System Files** | **Fully preserved** (print templates, uploaded files, etc.) | **Will be lost** (print templates, uploaded files, etc.) |
-| **Recommended Scenarios** | Enterprise users with controlled, consistent environments needing full functionality | Missing some plugins, seeking high compatibility and flexibility, non-Pro/Enterprise users, or those who can accept the loss of file features |
-
----
-
 ## FAQ
 
 ### Can Pro Edition users install this? Will it cause errors?
@@ -146,10 +80,6 @@ We recommend the latest `beta-full` image (e.g., `nocobase/nocobase:beta-full`).
 
 The demo's logo is configured with a domain restriction and cannot load on local domains. Go to **System Settings** and re-upload your own logo.
 
-### File upload error (OSS Key error)?
-
-After SQL import, file uploads may fail with an OSS-related error. Solution: go to **Plugin Manager → File Manager**, set **Local Storage** as the default storage, and save. Uploads will work normally after this.
-
 ### What about incremental upgrades?
 
 Currently, version upgrades are full replacements — your custom modifications will be overwritten. Always back up before upgrading. An incremental migration solution is being planned and will prioritize Pro/Enterprise editions. Community edition support is more difficult due to the lack of the migration management plugin.

package/dist/ai/docs/nocobase/solution/crm/v1.md

@@ -21,13 +21,13 @@ The legacy CRM includes the following functional modules:
 
 > The current version is deployed via backup and restoration.
 
+> **The Backup Manager plugin is now open-source**: The "[Backup Manager](https://docs.nocobase.com/handbook/backups)" plugin needed to restore the solution is now open-source and available to all editions (including the Community Edition). We recommend restoring directly via this plugin.
+
 Before you begin, please ensure:
 
 - You have a basic NocoBase runtime environment. For main system installation, please refer to the detailed [Official Installation Documentation](https://docs.nocobase.com/welcome/getting-started/installation).
 - NocoBase version **v2.1.0-beta.2 or higher**.
-- You have downloaded the corresponding CRM v1 files:
-  - **Backup file**: [nocobase_crm_v1_backup_260224.nbdata](https://static-docs.nocobase.com/nocobase_crm_v1_backup_260224.nbdata) — Applicable to Method 1.
-  - **SQL file**: [nocobase_crm_v1_sql_260224.zip](https://static-docs.nocobase.com/nocobase_crm_v1_sql_260224.zip) — Applicable to Method 2.
+- You have downloaded the CRM v1 backup file: [nocobase_crm_v1_backup_260224.nbdata](https://static-docs.nocobase.com/nocobase_crm_v1_backup_260224.nbdata)
 
 **Important Notes**:
 - This solution is based on the **PostgreSQL 16** database. Please ensure your environment uses PostgreSQL 16.
@@ -35,9 +35,9 @@ Before you begin, please ensure:
 
 ---
 
-## Method 1: Restore using Backup Manager (Recommended for Pro/Enterprise users)
+## Restore using Backup Manager
 
-This method uses the built-in "**Backup Manager**" (Pro/Enterprise) plugin for one-click restoration, which is the simplest approach.
+This method uses the built-in "**Backup Manager**" plugin for one-click restoration, which is the simplest approach. This plugin is now open-source and available to all editions (including the Community Edition).
 
 ### Steps
 
@@ -57,42 +57,5 @@ This method uses the built-in "**Backup Manager**" (Pro/Enterprise) plugin for o
 
 ### Notes
 
-* **Pro/Enterprise Edition Only**: "Backup Manager" is an enterprise-level plugin and is only available to Pro/Enterprise users.
+* **Database Compatibility**: Your PostgreSQL version, character set, and case sensitivity settings must match the backup source file.
 * **Commercial Plugin Compatibility**: Please ensure you have obtained and enabled the commercial plugins required for this solution.
-
----
-
-## Method 2: Import SQL file directly (General)
-
-This method restores data by directly operating on the database and is applicable to all NocoBase users.
-
-### Steps
-
-**Step 1: Prepare a clean database**
-
-Prepare a brand new, empty database for the data you are about to import.
-
-**Step 2: Import the `.sql` file into the database**
-
-* **Via Command Line (Docker Example)**:
-
-  ```bash
-  # Copy the sql file into the container
-  docker cp nocobase_crm_v1_sql_260224.sql my-nocobase-db:/tmp/
-  # Enter the container and execute the import command
-  docker exec -it my-nocobase-db psql -U nocobase -d nocobase -f /tmp/nocobase_crm_v1_sql_260224.sql
-  ```
-
-* **Via Database Client**: Use tools like DBeaver, Navicat, or pgAdmin to connect to the database and execute the SQL file.
-
-**Step 3: Connect to the database and start the application**
-
-Configure NocoBase startup parameters to point to the database where the data was imported, then start the service.
-
-
-## CRM v2 archive
-
-> For unified maintenance, CRM 2.0 has been consolidated into the [All-in-One Business Suite](../all-in-one/installation.md). If you need the standalone CRM 2.0 (frozen snapshot dated 2026-05-23, no longer updated), use the archived files below:
-
-- [nocobase_crm_v2_backup_260523.nbdata](https://static-docs.nocobase.com/nocobase_crm_v2_backup_260523.nbdata)
-- [nocobase_crm_v2_sql_260523.zip](https://static-docs.nocobase.com/nocobase_crm_v2_sql_260523.zip)

package/dist/ai/docs/nocobase/solution/ticket-system/changelog.md

@@ -8,7 +8,6 @@ This page documents the update history for the Ticketing System solution. New en
 
 **Backup files**:
 - [nocobase_tickets_v2_backup_260324.nbdata](https://static-docs.nocobase.com/nocobase_tickets_v2_backup_260324.nbdata)
-- [nocobase_tickets_v2_sql_260324.zip](https://static-docs.nocobase.com/nocobase_tickets_v2_sql_260324.zip)
 
 **Changes**:
 - Fixed error "SLA Config not found" when marking a ticket as completed
@@ -21,7 +20,6 @@ This page documents the update history for the Ticketing System solution. New en
 
 **Backup files**:
 - nocobase_tts_v2_backup_260302.nbdata
-- nocobase_tts_v2_sql_260302.zip
 
 **Changes**:
 - Initial release of Ticketing System v2

package/dist/ai/docs/nocobase/solution/ticket-system/installation.md

@@ -2,15 +2,13 @@
 
 > The current version uses **backup and restoration** for deployment. In future versions, we may switch to **incremental migration** to facilitate the integration of the solution into your existing systems.
 
-To ensure you can deploy the ticketing solution to your own NocoBase environment quickly and smoothly, we provide two restoration methods. Please choose the one that best suits your user version and technical background.
+> **The Backup Manager plugin is now open-source**: The "[Backup Manager](https://docs.nocobase.com/handbook/backups)" plugin needed to restore the solution is now open-source and available to all editions (including the Community Edition). We recommend restoring directly via this plugin.
 
 Before you begin, please ensure:
 
 - You already have a basic NocoBase running environment. For main system installation, please refer to the detailed [official installation documentation](https://docs.nocobase.com/welcome/getting-started/installation).
 - NocoBase version **2.0.0-beta.5 and above**.
-- You have downloaded the corresponding files for the ticketing system:
-  - **Backup file**: [nocobase_tickets_v2_backup_260324.nbdata](https://static-docs.nocobase.com/nocobase_tickets_v2_backup_260324.nbdata) - For Method 1
-  - **SQL file**: [nocobase_tickets_v2_sql_260324.zip](https://static-docs.nocobase.com/nocobase_tickets_v2_sql_260324.zip) - For Method 2
+- You have downloaded the ticketing system backup file: [nocobase_tickets_v2_backup_260324.nbdata](https://static-docs.nocobase.com/nocobase_tickets_v2_backup_260324.nbdata)
 
 **Important Notes**:
 - This solution is built on **PostgreSQL 16**. Please ensure your environment uses PostgreSQL 16.
@@ -18,9 +16,9 @@ Before you begin, please ensure:
 
 ---
 
-## Method 1: Restore Using Backup Manager (Recommended for Pro/Enterprise Users)
+## Restore Using Backup Manager
 
-This method uses the built-in "[Backup Manager](https://docs.nocobase.com/handbook/backups)" (Pro/Enterprise) plugin for one-click restoration, which is the simplest operation. However, it has certain requirements for the environment and user version.
+This method uses the built-in "[Backup Manager](https://docs.nocobase.com/handbook/backups)" plugin for one-click restoration, which is the simplest operation. This plugin is now open-source and available to all editions (including the Community Edition).
 
 ### Core Features
 
@@ -28,9 +26,8 @@ This method uses the built-in "[Backup Manager](https://docs.nocobase.com/handbo
   1. **Convenient Operation**: Can be completed via the UI, allowing for full restoration of all configurations, including plugins.
   2. **Complete Restoration**: **Able to restore all system files**, including print templates, files uploaded to attachment fields, etc., ensuring full functionality.
 * **Limitations**:
-  1. **Pro/Enterprise Only**: "Backup Manager" is an enterprise-level plugin, available only to Pro/Enterprise users.
-  2. **Strict Environment Requirements**: Requires your database environment (version, case sensitivity, etc.) to be highly compatible with the environment where the backup was created.
-  3. **Plugin Dependencies**: If the solution includes commercial plugins not present in your local environment, the restoration will fail.
+  1. **Strict Environment Requirements**: Requires your database environment (version, case sensitivity, etc.) to be highly compatible with the environment where the backup was created.
+  2. **Plugin Dependencies**: If the solution includes commercial plugins not present in your local environment, the restoration will fail.
 
 ### Steps
 
@@ -67,66 +64,6 @@ Then use this image to start your NocoBase service.
 * **Database Compatibility**: This is the most critical point for this method. Your PostgreSQL database **version, character set, and case sensitivity settings** must match the backup source file. In particular, the `schema` name must be consistent.
 * **Commercial Plugin Matching**: Please ensure you have and have enabled all commercial plugins required by the solution, otherwise the restoration will be interrupted.
 
----
-
-## Method 2: Direct SQL File Import (Universal, More Suitable for Community Edition)
-
-This method restores data by directly operating the database, bypassing the "Backup Manager" plugin, and therefore has no Pro/Enterprise plugin restrictions.
-
-### Core Features
-
-* **Advantages**:
-  1. **No Version Restrictions**: Applicable to all NocoBase users, including the Community Edition.
-  2. **High Compatibility**: Does not depend on the application's `dump` tool; it works as long as you can connect to the database.
-  3. **High Fault Tolerance**: If the solution contains commercial plugins you do not have, the related features will not be enabled, but this will not affect other functions, and the application can start successfully.
-* **Limitations**:
-  1. **Requires Database Operation Skills**: Users need basic database operation skills, such as how to execute a `.sql` file.
-  2. **System Files Lost**: **This method will lose all system files**, including print templates, files uploaded to attachment fields, etc.
-
-### Steps
-
-**Step 1: Prepare a clean database**
-
-Prepare a brand new, empty database for the data you are about to import.
-
-**Step 2: Import the `.sql` file into the database**
-
-Get the downloaded database file (usually in `.sql` format) and import its contents into the database prepared in the previous step. There are several ways to do this, depending on your environment:
-
-* **Option A: Via server command line (Docker example)**
-  If you use Docker to install NocoBase and the database, you can upload the `.sql` file to the server and use the `docker exec` command to perform the import. Assuming your PostgreSQL container is named `my-nocobase-db` and the file is named `ticket_system.sql`:
-
-  ```bash
-  # Copy the sql file into the container
-  docker cp ticket_system.sql my-nocobase-db:/tmp/
-  # Enter the container and execute the import command
-  docker exec -it my-nocobase-db psql -U your_username -d your_database_name -f /tmp/ticket_system.sql
-  ```
-* **Option B: Via remote database client**
-  If your database port is exposed, you can use any graphical database client (such as DBeaver, Navicat, pgAdmin, etc.) to connect to the database, open a new query window, paste the entire contents of the `.sql` file, and execute it.
-
-**Step 3: Connect to the database and start the application**
-
-Configure your NocoBase startup parameters (such as environment variables `DB_HOST`, `DB_PORT`, `DB_DATABASE`, `DB_USER`, `DB_PASSWORD`, etc.) to point to the database where you just imported the data. Then, start the NocoBase service normally.
-
-### Notes
-
-* **Database Permissions**: This method requires an account and password with permissions to directly operate the database.
-* **Plugin Status**: After a successful import, although the commercial plugin data exists in the system, if you have not installed and enabled the corresponding plugins locally, the related features will not be displayed or usable, but this will not cause the application to crash.
-
----
-
-## Summary and Comparison
-
-| Feature | Method 1: Backup Manager | Method 2: Direct SQL Import |
-| :-------------- | :--------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------- |
-| **Target Users** | **Pro/Enterprise** users | **All users** (including Community Edition) |
-| **Ease of Use** | ⭐⭐⭐⭐⭐ (Very simple, UI operation) | ⭐⭐⭐ (Requires basic database knowledge) |
-| **Environment Requirements** | **Strict**, database and system versions must be highly compatible | **General**, requires database compatibility |
-| **Plugin Dependencies** | **Strong dependency**, plugins are verified during restoration; missing any plugin will cause **restoration failure**. | **Features depend on plugins**. Data can be imported independently, and the system will have basic functionality. However, if corresponding plugins are missing, related features will be **completely unusable**. |
-| **System Files** | **Fully preserved** (print templates, uploaded files, etc.) | **Will be lost** (print templates, uploaded files, etc.) |
-| **Recommended Scenarios** | Enterprise users with a controlled, consistent environment who need complete functionality | Missing some plugins, seeking high compatibility and flexibility, non-Pro/Enterprise users, can accept the loss of file-related functions |
-
 We hope this tutorial helps you successfully deploy the ticketing system. If you encounter any issues during the process, please feel free to contact us!
 ---
 

package/dist/ai/docs/nocobase/workflow/advanced/options.md

@@ -1,5 +1,49 @@
 # Advanced Configuration
 
+## Timeout Settings
+
+Starting from version `2.1.0`, workflows support timeout settings to limit the maximum duration of a single execution from the time it starts processing until it ends. Timeout settings are useful for preventing workflows from occupying execution resources indefinitely because of long-running operations, manual processing, or waiting for external callbacks.
+
+In the workflow creation or editing dialog, expand "Advanced options" to configure "Timeout settings":
+
+![20260604212454](https://static-docs.nocobase.com/20260604212454.png)
+
+The available options are:
+
+- Enter `0` to set no timeout limit (default).
+- Enter a value greater than `0` to enable the timeout limit. The interface supports seconds, minutes, hours, and days as units.
+- The maximum timeout is 180 days.
+
+### Timing Rules
+
+The timeout starts counting when the workflow first enters a processor. After a workflow is triggered, time spent waiting in the queue for scheduling, or stored for delayed start, does not count toward the timeout.
+
+After entering a processor, the timeout continues to count, including actual node execution time and time spent by nodes that have entered a waiting state, such as manual processing, approval, delay, or waiting for an external callback. The timeout does not pause when the workflow is waiting for user action.
+
+The timeout deadline is determined when the execution starts. Changing a workflow's timeout settings only affects executions that start processing afterward; it does not recalculate executions that have already started.
+
+### Timeout Handling
+
+If the execution has not ended when the timeout is reached, the system terminates it:
+
+- The execution history status changes to "Aborted", and the termination reason is shown as "Timed out".
+- Node jobs that are currently running or waiting are marked as "Aborted".
+- Subsequent nodes will not continue to execute.
+- If this execution has running subflow executions, those subflows are also aborted together with the parent execution.
+
+Examples:
+
+- If a loop node runs an extremely long loop and the processing inside the loop is time-consuming, causing the whole loop node to exceed the configured timeout, the currently running loop node and its internal nodes are forcibly terminated, and subsequent nodes will not continue to execute.
+- If a manual processing or approval node waits for a long time and exceeds the configured timeout, the currently waiting manual processing node is forcibly terminated, subsequent nodes will not continue to execute, and the related tasks are canceled.
+
+:::info{title=Note}
+Timeout settings are a global limit for the entire workflow execution, not a timeout for an individual node. If you only need to limit the waiting time of a specific node, such as an HTTP Request or JavaScript Script node, use that node's own timeout settings.
+:::
+
+:::info{title=Note}
+If you need to implement business-level time-limited handling, such as "mark a work order as timed out if nobody processes it within 10 minutes", usually use the [Delay node](../nodes/delay.md) together with parallel branches to arrange the follow-up handling. The global timeout directly terminates the current execution, so it is suitable as a fallback protection mechanism, not for carrying subsequent business branches.
+:::
+
 ## Execution Mode
 
 Workflows are executed either asynchronously or synchronously, based on a trigger type selected during creation. Asynchronous mode means that after a specific event is triggered, the workflow enters a queue and is executed one by one by background scheduling. Synchronous mode, on the other hand, does not enter the scheduling queue after being triggered; it starts executing directly and provides immediate feedback upon completion.
@@ -30,4 +74,4 @@ It is recommended not to enable auto-deletion of execution history when debuggin
 
 :::info{title=Note}
 Deleting a workflow's history does not reduce its execution count.
-:::
+:::

package/dist/ai/docs/nocobase/workflow/nodes/javascript.md

@@ -64,7 +64,9 @@ This is the recommended default mode, suitable for pure computation and data pro
 When `WORKFLOW_SCRIPT_MODULES` **is configured**, scripts switch to the Node.js built-in `vm` engine to enable `require` capability.
 
 :::warning{title="Security Warning"}
-In unsafe mode, although scripts run in a `vm` sandbox with a restricted module whitelist, the Node.js `vm` module is not a secure sandbox mechanism. Enabling this mode implies trusting all users who have permission to edit workflow scripts. Administrators should assess the security risks independently and strictly control the module whitelist and workflow editing permissions.
+Unsafe mode uses Node.js `vm` only to provide CommonJS `require` support. The Node.js `vm` module is not a secure sandbox mechanism. Enabling this mode means trusting every user who can edit, test, or run workflow scripts as someone who can execute code with the NocoBase server's privileges.
+
+`WORKFLOW_SCRIPT_MODULES` is not a security boundary or a permission model. It only controls which module names are accepted by `require()` before script code runs.
 :::
 
 Modules can be used in the script consistent with CommonJS, using the `require()` directive to import modules.
@@ -76,7 +78,7 @@ WORKFLOW_SCRIPT_MODULES=crypto,timers,lodash,dayjs
 ```
 
 :::info{title="Note"}
-Modules not declared in the `WORKFLOW_SCRIPT_MODULES` environment variable **cannot** be used in the script, even if they are native to Node.js or already installed in `node_modules`. This policy can be used at the operational level to control the list of modules available to users, preventing scripts from having excessive permissions in some scenarios.
+Modules not declared in the `WORKFLOW_SCRIPT_MODULES` environment variable **cannot** be imported directly with `require()`, even if they are native to Node.js or already installed in `node_modules`. This list is intended only to configure supported imports. Do not rely on it to reduce script permissions or to safely delegate script editing to less-trusted users.
 :::
 
 When in a non-source-deployed environment, if a module is not installed in `node_modules`, you can manually install the required package into the `storage` directory. For example, to use the `exceljs` package, you can perform the following steps: