DEV Community: NocoBase

Weekly Updates: Improvements and Bug Fixes

NocoBase — Fri, 16 Oct 2026 14:15:07 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.25

Release date: 2026-10-14

🐛 Bug Fixes

[client-v2] Fixed attachment previews and editor popover visibility in v2 approval form subtables. (#10586) by mytharcher

v2.2.24

Release date: 2026-10-13

🐛 Bug Fixes

[server] Fix validation and scoping of the application name resolved from a request in the gateway. (#10548) by 2013xile
[AI employees] AI conversations now send a stable conversation-specific prompt cache key in both OpenAI API modes, allowing compatible gateways to maintain channel affinity. (#10788) by cgyrock

v2.2.23

Release date: 2026-10-11

🚀 Improvements

[undefined]
- V3 workflow entry filenames now use a consistent v3- prefix with documented cross-branch synchronization rules. (#10590) by Molunerfinn
- Added manual Actions entry points for the workflows on NocoBase 3’s isolated branches. (#10587) by Molunerfinn

🐛 Bug Fixes

[database] Fixed a GROUP BY error on PostgreSQL when filtering by a to-many relation field and sorting by a root field on tables without a primary key constraint (#10582) by cgyrock
[client] Fix the issue where block settings disappear in UI Editor mode after the browser window is narrowed and then widened again (#10583) by zhangzhonghe
[undefined] Preserved nightly PostgreSQL and MySQL checks after moving NocoBase 3 to its dedicated branches. (#10589) by Molunerfinn
[Workflow: Aggregate node] Fixed aggregate fields disappearing when reopening workflow Aggregate nodes with associated collections, and reduced unnecessary relation traversal when restoring saved field selections. (#10578) by mytharcher
[Collection field: Many to many (array)] Fix the issue where relation fields created in the v2 data source manager could not be configured in blocks (#10581) by zhangzhonghe
[File manager] Fixed attachment uploads falling back to default storage by preserving direct-upload field parameters in main and sub-applications and honoring field storage for custom file collections. (#10577) by mytharcher

v2.2.22

Release date: 2026-10-08

🐛 Bug Fixes

[client-v2] Fixed empty JS action items becoming inaccessible in the UI editor. (#10573) by gchust
[UI layout] Fixed missing popup template options in action settings in the new client. (#10574) by gchust

v2.2.21

Release date: 2026-10-06

🐛 Bug Fixes

[client-v2] Fixed empty JS blocks becoming inaccessible in the UI Editor after disabling the block card. (#10563) by gchust
[Notification: Email] Upgraded nodemailer, hono and moment to patched versions. (#10569) by 2013xile
[UI templates] Fixed the internal template collection appearing in block collection choices after deleting a UI template. (#10561) by gchust

v2.3.0-beta.15

Release date: 2026-10-15

🐛 Bug Fixes

[client-v2] Fixed attachment previews and editor popover visibility in v2 approval form subtables. (#10586) by mytharcher
[server] Fix validation and scoping of the application name resolved from a request in the gateway. (#10548) by 2013xile
[AI employees] AI conversations now send a stable conversation-specific prompt cache key in both OpenAI API modes, allowing compatible gateways to maintain channel affinity. (#10788) by cgyrock

v2.3.0-beta.14

Release date: 2026-10-12

🚀 Improvements

[undefined]
- V3 workflow entry filenames now use a consistent v3- prefix with documented cross-branch synchronization rules. (#10590) by Molunerfinn
- Added manual Actions entry points for the workflows on NocoBase 3’s isolated branches. (#10587) by Molunerfinn

🐛 Bug Fixes

[client-v2]
- Fixed empty JS action items becoming inaccessible in the UI editor. (#10573) by gchust
- Fixed empty JS blocks becoming inaccessible in the UI Editor after disabling the block card. (#10563) by gchust
[database] Fixed a GROUP BY error on PostgreSQL when filtering by a to-many relation field and sorting by a root field on tables without a primary key constraint (#10582) by cgyrock
[undefined] Preserved nightly PostgreSQL and MySQL checks after moving NocoBase 3 to its dedicated branches. (#10589) by Molunerfinn
[client] Fix the issue where block settings disappear in UI Editor mode after the browser window is narrowed and then widened again (#10583) by zhangzhonghe
[sdk] Upgraded axios to 1.20.0 (#10566) by 2013xile
[File manager] Fixed attachment uploads falling back to default storage by preserving direct-upload field parameters in main and sub-applications and honoring field storage for custom file collections. (#10577) by mytharcher
[Workflow: Aggregate node] Fixed aggregate fields disappearing when reopening workflow Aggregate nodes with associated collections, and reduced unnecessary relation traversal when restoring saved field selections. (#10578) by mytharcher
[Collection field: Many to many (array)] Fix the issue where relation fields created in the v2 data source manager could not be configured in blocks (#10581) by zhangzhonghe
[UI layout] Fixed missing popup template options in action settings in the new client. (#10574) by gchust
[UI templates] Fixed the internal template collection appearing in block collection choices after deleting a UI template. (#10561) by gchust
[Notification: Email] Upgraded nodemailer, hono and moment to patched versions. (#10569) by 2013xile
[Block: Kanban] Fixed Kanban layout flicker when adding an AI employee action. (#10553) by jiannx
[Data source: External NocoBase] Fixed the type build failure caused by the axios 1.20.0 upgrade by 2013xile
[Workflow: Approval] Fix the issue where hidden field labels reappear and field values are empty in submitted approval details by zhangzhonghe
[Data source: External Oracle] Fixed a type error surfaced by the axios 1.20.0 upgrade by 2013xile

develop

v2.4.0-alpha.10

Release date: 2026-10-12

🚀 Improvements

[undefined]
- V3 workflow entry filenames now use a consistent v3- prefix with documented cross-branch synchronization rules. (#10590) by Molunerfinn
- Added manual Actions entry points for the workflows on NocoBase 3’s isolated branches. (#10587) by Molunerfinn

🐛 Bug Fixes

[database] Fixed a GROUP BY error on PostgreSQL when filtering by a to-many relation field and sorting by a root field on tables without a primary key constraint (#10582) by cgyrock
[client] Fix the issue where block settings disappear in UI Editor mode after the browser window is narrowed and then widened again (#10583) by zhangzhonghe
[client-v2]
- Fixed empty JS blocks becoming inaccessible in the UI Editor after disabling the block card. (#10563) by gchust
- Fixed empty JS action items becoming inaccessible in the UI editor. (#10573) by gchust
[undefined] Preserved nightly PostgreSQL and MySQL checks after moving NocoBase 3 to its dedicated branches. (#10589) by Molunerfinn
[File manager] Fixed attachment uploads falling back to default storage by preserving direct-upload field parameters in main and sub-applications and honoring field storage for custom file collections. (#10577) by mytharcher
[Workflow: Aggregate node] Fixed aggregate fields disappearing when reopening workflow Aggregate nodes with associated collections, and reduced unnecessary relation traversal when restoring saved field selections. (#10578) by mytharcher
[UI templates] Fixed the internal template collection appearing in block collection choices after deleting a UI template. (#10561) by gchust
[Collection field: Many to many (array)] Fix the issue where relation fields created in the v2 data source manager could not be configured in blocks (#10581) by zhangzhonghe
[UI layout] Fixed missing popup template options in action settings in the new client. (#10574) by gchust
[Notification: Email] Upgraded nodemailer, hono and moment to patched versions. (#10569) by 2013xile

How to Use AI for Business Analysis: Sales, Inventory, and Profit Analysis

NocoBase — Wed, 14 Oct 2026 07:53:06 +0000

Originally published at https://www.nocobase.com/en/blog/ai-business-analysis-with-nocobase

In previous articles, we introduced how to build a CRM with AI and NocoBase, IT asset management, and a ticketing system, showing how AI can turn business requirements described in natural language into enterprise applications that can actually be used.

Recently, in Reddit's r/AI_Agents, a developer shared a project they were working on: helping a small factory organize attendance and payroll data, with plans to connect an AI Agent so the owner could query employee attendance, overtime, and exception data directly through WhatsApp.

But they also had questions: once the Agent is connected, which features will the client actually need? Which ones only look good in a demo? And when the system is used in real operations, what challenges will data quality, query accuracy, and user habits create?

💬 Hey, you're reading the NocoBase blog. NocoBase is the most extensible AI-powered no-code/low-code development platform for building enterprise applications, internal tools, and all kinds of systems. It’s fully self-hosted, plugin-based, and developer-friendly. → Explore NocoBase on GitHub

The same questions apply to business analysis. When business data spans sales, inventory, procurement, and finance, looking at only one type of data is often not enough to support a complete management decision. If data sources are inconsistent or records are incomplete, AI analysis can also be affected.

In this article, we use a company that sells multiple categories of electronic devices and office supplies as an example. It built an All-in-one business system with AI and NocoBase, covering sales, inventory, procurement, finance, and other modules.

Using the business data accumulated in the system, we will show step by step how AI can support business analysis and combine information across different business functions to provide input for decision-making.

01 | Define the Business Question and Understand the Available Data

Business decisions often involve multiple departments. Sales teams focus on customer demand and order growth, procurement teams need to plan replenishment in advance, and finance teams are more concerned with costs, collections, and the use of working capital.

Sometimes sales opportunities keep increasing while inventory is already building up. In other cases, the order outlook may look positive while the company still faces cash pressure.

We want to use AI to analyze a common business question:

As sales opportunities increase, should the company keep expanding procurement, or should it prioritize controlling inventory and working-capital usage?

To answer this question, we need to understand how many orders may be coming, whether current inventory can support the expected demand, how much procurement has already been arranged, and whether the company's current financial position can support additional investment.

The NocoBase All-in-one system used in this example includes sales, inventory, procurement, and finance modules. It records information ranging from customer opportunities and product inventory to purchase orders and accounts receivable.

These modules provide the following data for this analysis:

Business module	Data in the system	Role in business decisions
Sales management	Customers, sales opportunities, opportunity stages, revenue forecasts	Understand potential orders and future sales demand
Inventory management	Products, inventory quantities, inventory movements, reorder points	Review current inventory and possible stockout risks
Procurement management	Purchase orders, suppliers, purchase amounts, order status	Understand current procurement plans and funding requirements
Finance management	Invoices, accounts receivable, expenses, budgets	Review collections and operating cash pressure

However, simply having data in the system does not mean AI can immediately produce a reliable conclusion.

💡 Further reading: Top 3 Open Source ERP with AI on GitHub: NocoBase vs Odoo vs ERPNext

For example, the expected deal value of a sales opportunity represents potential revenue, but there is still uncertainty about whether the deal will close. Current inventory needs to be assessed together with actual demand and purchase orders that have already been placed. Invoice amounts in the finance module also cannot be treated as cash already collected.

This information needs to be analyzed together with the underlying business records before it can provide a reliable basis for later decisions.

02 | Start with Sales Opportunities to Understand Future Demand

An increase in sales opportunities is usually a positive signal, but the company also needs to understand how likely those opportunities are to become actual orders and how much business demand they may generate.

In NocoBase's sales management module, users can review customer opportunities, expected deal values, opportunity stages, and expected closing dates.

Opportunities at different stages have different value for procurement planning.

For example, one customer may have only just expressed purchase intent, while another is already in quotation or contract negotiation. Both count as potential sales opportunities, but they are at different distances from an actual order.

For opportunities expected to close soon, the company can start monitoring the relevant products' inventory and fulfillment capacity in advance. For customers still in early-stage discussions, actual demand needs to be evaluated more cautiously to avoid arranging large purchases too early.

In addition to opportunity progress, NocoBase's revenue forecast page can be used to see how potential revenue is distributed across different time periods.

Revenue forecasts can inform procurement planning, but final deal values, order quantities, and delivery dates may still change. Specific purchase quantities therefore still need to be determined using actual orders and product demand.

Next, we continue with inventory and procurement data to see whether current stock and planned purchases can support this potential demand.

03 | Combine Inventory and Procurement to Evaluate Replenishment Needs

3.1 Let AI Help Identify Inventory Risks

In NocoBase's inventory management module, users can review inventory quantities, reorder points, and historical inventory movement records for different products.

The product list provides an initial view of which products are approaching their reorder points and which still have relatively high inventory. For products with low inventory, recent sales demand and supplier lead times also need to be considered before deciding whether to replenish early.

Historical movements also matter. By reviewing receipts, issues, and inventory adjustments, the company can better understand inventory trends. A product may still have plenty of inventory, for example, but if outbound volume has been very low recently, there may be a risk of overstock.

When there are many products and inventory records, reviewing them one by one can be time-consuming. We therefore tried asking AI directly from the NocoBase business page to analyze the inventory records and help identify products that may face stockout or overstock risks.

During the actual query, AI found that the system contained different inventory data sources and first needed to determine which data should be used before continuing the analysis.

Even within inventory data, some records represent current inventory quantities while others store historical receipts, issues, and inventory adjustments. Using the wrong data source can mix up current inventory with historical movements and affect the analysis that follows.

Inventory data is also only one part of deciding whether more stock needs to be purchased. The company may already have purchase orders with suppliers even if the products have not yet arrived. We therefore also need to review existing procurement arrangements to understand which needs are already covered and how much funding may be required.

3.2 Review Procurement Plans and Future Funding Requirements

In NocoBase's procurement management module, users can review suppliers, purchase amounts, and order status for existing purchase orders, along with purchase commitments and supplier spending.

These records help the company understand which requirements already have procurement arranged.

For example, a product may currently have low inventory, but if a corresponding purchase order is already being processed, the company should first check the ordered quantity and expected arrival time before placing another order. This helps avoid duplicate purchasing and unnecessary inventory buildup.

The funding involved in procurement also needs attention. Existing purchase orders reflect the company's current procurement arrangements, but order amounts, purchase commitments, and actual payments may differ. To understand how much more funding will be required, payment records and supplier payment terms should also be considered.

Combining current inventory, purchase orders, and the sales demand identified earlier helps the company assess whether additional procurement is necessary, avoiding unnecessary stock increases while existing purchases are still pending.

Procurement decisions are also affected by customer collections and overall working-capital conditions. Next, we turn to the finance data.

04 | Review Financial Data to Understand Revenue and Profitability

From a finance perspective, there are three main questions: How has recent revenue performed? What is the status of accounts receivable and collections? And is the available data sufficient to evaluate profitability?

4.1 Review Invoices and Accounts Receivable

We first open NocoBase's finance management module and review customer invoices and related accounts-receivable records to understand invoicing, outstanding amounts, and collection progress.

These records are closely related to day-to-day cash planning.

For example, a sales order may already have been fulfilled and invoiced, but the customer may not pay until later. If the company needs to pay suppliers at the same time, procurement cash outflows may occur before customer collections.

That is why financial analysis needs to distinguish between invoice amounts, recognized revenue, accounts receivable, and cash actually collected. For a company considering additional procurement, understanding outstanding receivables and expected collection dates helps evaluate whether more purchasing will create additional cash pressure.

4.2 Let AI Analyze Revenue and Profitability

Next, we ask AI to analyze the company's revenue and profitability in more depth.

On the NocoBase finance page, we asked AI to analyze revenue growth and profitability using the financial data already available in the system, with the goal of understanding recent revenue changes and whether profitability had improved.

AI queried the data it could currently access and generated a revenue-growth and profitability analysis report.

The report provided analysis related to revenue, but when it tried to evaluate profitability further, AI identified a data limitation: the available data was not sufficient to calculate profit completely, so it could not confirm whether revenue growth had actually improved profitability.

Accurate profit calculation requires not only revenue but also the actual costs associated with the relevant products or orders. Procurement costs, transportation, warehousing, and other related expenses can all affect the final result.

Even if the procurement module already records purchase-order amounts, those amounts cannot simply be treated as the cost of goods sold. The company still needs to identify which costs correspond to realized sales revenue and how related expenses should be allocated.

If the company wants to analyze profitability by product or order in more detail, it needs to add the corresponding cost and expense records, define a clear profit-calculation method, and then combine those records with sales data.

05 | Combine Business Data and Let AI Support Management Decisions

After the previous analysis, we now have separate views of potential sales demand, inventory, procurement arrangements, revenue, and collections.

We then ask AI to combine these data points and help identify which business issues should receive the most attention in the next stage.

💡 Further reading: Build an Interactive Operations Dashboard with NocoBase

In NocoBase, we asked AI to perform an integrated business analysis using sales opportunities, purchase orders, purchase commitments, accounts receivable, and other available data to evaluate the relationship between future demand and funding arrangements.

AI generated an integrated business analysis report based on the data it could access. Combining sales opportunities, procurement arrangements, and accounts receivable, the report produced three main recommendations:

Prioritize customer collections. Verify outstanding customer payments and expected collection dates, identify the receivables that need priority follow-up, and improve cash recovery.
Plan additional procurement cautiously. Compare potential sales demand with current inventory and purchase orders already submitted to determine which products actually need early replenishment, avoiding duplicate purchasing or premature inventory buildup.
Manage working capital carefully. Combine existing purchase commitments, upcoming payment plans, and expected collection dates to evaluate the working capital tied up by new purchases and plan the use of funds more reasonably.

These recommendations provide a reference for the next round of business planning, but the relevant data still needs to be verified before action is taken. When adjusting procurement plans, for example, the company needs to confirm inventory quantities, inbound orders, and expected sales demand. When following up on customer collections, it needs to confirm receivable amounts, due dates, and current collection progress.

In NocoBase, companies can also configure corresponding business processes as needed. Outstanding customer collections can be assigned to responsible staff, with communication and collection progress recorded. New purchase requests can use approval workflows, while role permissions define what different users are allowed to do. This allows verified analysis recommendations to be translated into concrete business actions that are then confirmed and executed by the responsible people.

Conclusion

Many business questions cannot be answered with a single metric. Whether sales growth justifies more procurement also depends on inventory, costs, collections, and working-capital planning. Individual indicators can reveal changes in the business, while relationships across different data sources often help teams identify the opportunities and risks that deserve more attention.

With NocoBase, companies can connect and relate data distributed across different business systems, giving AI a more complete basis for analysis. As business data continues to update, AI can participate in new analyses over time, helping teams detect changes earlier and make better use of existing data in day-to-day management and decision-making.

💡 Bring AI into existing business systems: Read How to Add AI to Existing Enterprise Systems with NocoBase to learn how to reuse existing data and expand AI applications gradually.

🚀 Try it yourself: Visit the NocoBase online demo to explore how AI, business data, and workflows can work together in the same system.

Related reading:

How to Start Using AI Without Replacing Existing Business Systems

NocoBase — Wed, 07 Oct 2026 08:18:18 +0000

Originally published at https://www.nocobase.com/en/blog/add-ai-to-existing-enterprise-systems-with-nocobase

AI capabilities are entering every part of enterprise software, from code generation and data analysis to Agents, automation, and business assistance. We previously reviewed 10 Open-Source AI Agent Platforms for Business, covering automation, Agent building, and internal applications. Enterprises now have more options than ever.

But for companies that already rely on CRM, ERP, MES, SaaS, or custom-built systems, actually adopting AI is not that simple. Existing systems often have years of operational history, accumulated data, established processes, permission models, integrations, and user habits. Even when a company wants to add AI capabilities, migrating or rebuilding the entire system is rarely easy.

Recently, in Reddit's r/CRMSoftware, a small-business owner shared a similar experience.

Their company started using Salesforce in 2019 with only one account and has since grown to a team of 12. Over the past seven years, they have built extensive customizations around their business, and Salesforce has gradually become a core operational system.

As the business continued to grow, they needed more automation, cross-platform integrations, call logging, financial synchronization, LLM integrations, and forms. They also wanted to explore AI Agents, intelligent analytics, and AI-driven business automation. Continuing with Salesforce would require a plan upgrade and additional budget for APIs, Agentforce, and other third-party tools. Migrating, on the other hand, would mean dealing with custom objects, non-standard workflows, historical data, and the time and cost of the entire transition.

This situation is common in many companies: there are new, relatively independent requirements, but the business still needs to keep using data from existing systems. A full migration is expensive, while rebuilding everything from scratch creates additional maintenance pressure.

A more flexible approach is to use AI with NocoBase to turn the new requirement into a separate internal application first. Compared with relying on AI to build everything from scratch, enterprise applications still need stable data relationships, permissions, workflows, and long-term maintainability. NocoBase already provides these foundational capabilities, while AI can help build the new application on top of them and continue using data from the existing system.

This means the company does not need to solve a full-system migration at the beginning. As the new application matures, more data and business processes can be moved over gradually based on actual needs.

For example, imagine a manufacturing company that already has an Inventory Management System but wants to add a mobile inventory counting app. Warehouse staff need to scan items, enter actual quantities, and handle discrepancies on site, while continuing to use the existing product, SKU, warehouse, and inventory data. A requirement with a clear scope that still needs to reuse existing data is a good fit for building a separate application with AI and NocoBase, then expanding it gradually based on real usage.

Next, we will use this scenario to show how AI and NocoBase can turn a relatively independent new requirement into a new internal application, while gradually adding AI analysis and automation capabilities.

01 | Choose a Business Scenario That Can Be Piloted Independently

Start with a business requirement that has a clear scope, measurable value, and can be piloted independently.

Clear scope: the business objects, operating process, and users are relatively well defined, and changing this scenario does not affect multiple core systems at once.
Measurable value: after the application is introduced, the team can directly observe metrics such as processing time, manual work, exception volume, and operational efficiency.
Independent pilot: the application can first be used by one department, one group of users, or one business process while continuing to reuse data from the existing system.

This manufacturing company already has an Inventory Management System that manages products, SKUs, warehouses, current inventory, and inventory movements.

The new requirement is to let warehouse staff complete inventory counting on site, including claiming tasks, scanning items, entering actual quantities, recording inventory discrepancies, and reviewing exceptions.

The division of responsibilities between the old system and the new application can therefore be defined first:

	Application	Responsibilities
Existing system	Inventory Management System	Products, SKUs, warehouses, current inventory, inventory movements
New requirement	Mobile inventory counting app	Counting tasks, scanning, actual quantities, inventory discrepancies, discrepancy reasons, review status

The mobile inventory counting process mainly covers task claiming, scanning, quantity entry, and discrepancy review, while continuing to use product and inventory data from the existing Inventory Management System. During the pilot, the company can start with one warehouse, one group of operators, or one inventory-counting cycle, while continuing to call the foundational data from the existing system. After launch, the team can evaluate the pilot using metrics such as counting efficiency, manual workload, and discrepancy-handling time.

02 | Use AI and NocoBase to Turn the New Requirement into an Internal Application

Once the business scope is clear, the team can organize the existing system, business rules, and new requirements, then use AI to complete the initial application build.

For example:

We already have an Inventory Management System for products, SKUs, warehouses, and current inventory. We now need a mobile inventory counting app that allows warehouse staff to view counting tasks, scan items, enter actual quantities, record inventory discrepancies, and review exception data.

The Coding Agent can use these requirements to organize the application structure and configure the data model, pages, role permissions, and workflows in NocoBase. Business users are responsible for confirming the specific rules, such as who can claim tasks, how inventory discrepancies should be handled, and who is responsible for review.

The core mobile inventory counting process can be represented as:

Counting task → Product / SKU → System inventory → Actual quantity → Inventory discrepancy → Discrepancy reason → Processing status

After warehouse staff claim a task, they scan an item to locate the corresponding product and enter the actual quantity. If there is an inventory discrepancy, the record enters a pending-review state, and the responsible person confirms the reason and result. Operators and reviewers have their own pages and permissions, while reminders, pending tasks, and other follow-up actions can be handled through NocoBase workflows.

After the application is generated, fields, pages, layouts, and later functional changes can continue to be modified in NocoBase through the Coding Agent.

03 | Continue Using Data from the Existing System

Products, SKUs, warehouses, current inventory, and inventory movements continue to be maintained by the original Inventory Management System. NocoBase can read this data through an external database or API and use it directly inside the mobile inventory counting app.

📃 Data Sources - NocoBase

For example, when warehouse staff count a “brake pad set,” they can see the current inventory, safety stock, and recent inventory movements from the original system while entering the actual quantity, inventory discrepancy, discrepancy reason, and processing result in the mobile inventory counting app.

Data source	Information used during counting
Inventory Management System	Current inventory, safety stock, recent inventory movements
Mobile inventory counting app	Actual quantity, inventory discrepancy, discrepancy reason, processing status

To avoid inventory changes during counting from affecting the result, the application can record the system inventory and corresponding timestamp at the start of the task as the baseline for that count. Daily inventory continues to be maintained by the existing Inventory Management System.

If an inventory discrepancy is ultimately confirmed, the team can first complete the reason recording and review in the mobile inventory counting app, then handle the inventory adjustment according to the existing process. Whether the new application writes directly back to the original system depends on the APIs and permissions exposed by that system.

In this way, the new application only adds inventory-counting data and processes. Foundational data such as products, SKUs, warehouses, and inventory continues to come from the existing system, reducing duplicate maintenance.

04 | After Launch, Let AI Participate Further in Inventory Counting

Once the mobile inventory counting app is in use, counting tasks, actual quantities, discrepancy reasons, and review results will continue to create new business data. Beyond checking individual records, managers also need to understand overall counting progress, long-unprocessed tasks, and which SKUs repeatedly show inventory discrepancies.

During the application-building stage, the Coding Agent mainly helps build and adjust the application. After launch, NocoBase AI Employees can use the accumulated data to participate in day-to-day inventory analysis and related work.

📃 AI Employees - NocoBase Documentation

For example, an AI Employee can generate an inventory-counting overview that summarizes completion rate, accuracy, and inventory discrepancies, while highlighting tasks and products that need priority attention:

These results come from actual records in the application, and managers can always return to the corresponding tasks to verify the details.

For SKUs that repeatedly show discrepancies, AI Employees can also combine actual counting results, discrepancy reasons, and recent inventory movements to organize issues that need further investigation.

For example, if a “brake pad set” shows discrepancies across several consecutive counts, the team can prioritize checking recent receipts, issues, and transfers, and confirm whether duplicate counting, timing differences, or data-entry errors are involved. Cases where the cause cannot yet be confirmed can remain pending for further review by the responsible person.

On this basis, AI Employees can also be configured with appropriate skills and workflows to create review tasks, send reminders to responsible users, and generate inventory-counting reports. What data an AI Employee can access and which actions it can perform can also be configured according to actual roles and permissions.

This allows the company to start by using AI for summaries and analysis, then gradually expand it into more day-to-day operational work once the business rules and usage patterns become stable.

05 | Validate the Pilot Results

After the mobile inventory counting app has been used for a period of time, the company can evaluate whether the approach is worth continuing and decide whether to expand the scope, migrate selected modules from the old system, or keep the existing division of responsibilities.

Has manual recording and repeated data organization decreased?
Has the time required for each inventory count been reduced?
Are inventory discrepancies easier to identify and handle?
Can the existing inventory data be used reliably?
Can AI Employees already participate in day-to-day business processing?
Can the new application reliably handle routine inventory-counting work?

If these indicators generally meet expectations, the approach is ready for real business use, and the company can continue in two directions.

Extend the Same Approach to New Business Requirements

If the company has other relatively independent requirements that also need to use data from existing systems, it can reuse the same approach: define a clear scenario, build a new internal application with AI and NocoBase, then test and use it.

Handling one specific requirement at a time keeps the application scope and validation goals clear and makes it easier to judge whether further investment is worthwhile.

Evaluate Whether to Migrate Selected Modules from the Existing System

As the new application continues to be used, it will gradually accumulate its own data and business processes. If some functions can already reliably take over work from the existing system, the company can further evaluate whether the corresponding modules still need to remain in the old system.

If the mobile inventory counting app can reliably cover task assignment, counting, discrepancy handling, and review, the company can further assess whether the inventory-counting data and processes in the original Inventory Management System should be moved to NocoBase.

Conclusion

In the past, when a new business requirement appeared, teams typically had to choose between purchasing SaaS, modifying an existing system, or scheduling custom development. All of these approaches require cost evaluation, resource coordination, and often a waiting period before results can be validated.

If your company already uses CRM, supply chain management, project management SaaS, or similar systems and has a new requirement that the existing tools do not handle well, AI and NocoBase make it possible to start with a smaller, clearly scoped, confirmed requirement and test it in a more lightweight way.

Try the NocoBase + AI Demo: Request an online demo
Build it yourself: View the AI Builder documentation

Related reading:

Weekly Updates: AI Employees Now Support Knowledge Base Citations

NocoBase — Sat, 03 Oct 2026 09:48:47 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.20

Release date: 2026-09-30

🎉 New Features

[AI employees] AI employee chat responses expose the referenced knowledge base documents (#10560) by @cgyrock
[AI: Knowledge base] Resolve referenced knowledge base documents for AI employee chat responses by @cgyrock

🐛 Bug Fixes

[create-nocobase-app] Upgrade js-yaml and uuid (#10555) by @2013xile
[sdk] Upgraded axios to 1.20.0 (#10566) by @2013xile
[client-v2] Fix the issue where the "Current popup parent record" variable is missing in quick create popups of association fields in approval forms (#10554) by @zhangzhonghe
[Block: Kanban] Fixed Kanban layout flicker when adding an AI employee action. (#10553) by @jiannx
[Data source: External NocoBase] Fixed the type build failure caused by the axios 1.20.0 upgrade by @2013xile
[Data source: External Oracle] Fixed a type error surfaced by the axios 1.20.0 upgrade by @2013xile
[Workflow: Approval] Fix the issue where hidden field labels reappear and field values are empty in submitted approval details by @zhangzhonghe

v2.2.19

Release date: 2026-09-29

🎉 New Features

[AI employees] Added support for OpenCode Zen / Go as an LLM service by sending the required session headers; DeepSeek Flash models now accept image attachments, and web search is limited to DeepSeek V4 Pro because Flash models silently ignore it (#10551) by @cgyrock

🚀 Improvements

[client-v2] Table column quick edit: support setting a data scope for association fields (#10547) by @katherinehhh

🐛 Bug Fixes

[client-v2] Fix the issue where signing in with another account after signing out shows a 404 page (#10549) by @zhangzhonghe
[Action: Batch update] Prevent bulk update actions from submitting option values that no longer exist in the configured collection field. (#10540) by @jiannx
[Workflow] Fix creation of the jobs status and ID index during database sync. (#10552) by @mytharcher

v2.2.18

Release date: 2026-09-25

🐛 Bug Fixes

[client] Fixed workflow manual node form layouts failing when multiple fields are arranged in one row. (#10545) by @mytharcher
[client-v2] Fixed saving attachment and file relation changes inside approval form sub-tables. (#10544) by @mytharcher
[Block: GridCard] Fixed Grid Card pagination switching and aligned simple-pagination page sizes with the configured column count (#10541) by @jiannx
[Workflow: Aggregate node] Fix aggregate field selection for collections selected through to-many associations. (#10543) by @mytharcher
[Migration manager] Updated decompress to @xhmikosr/decompress 11.1.4 by @2013xile

v2.3.0-beta.13

Release date: 2026-09-30

🎉 New Features

[AI employees]
- AI employee chat responses expose the referenced knowledge base documents (#10560) by @cgyrock
- Added support for OpenCode Zen / Go as an LLM service by sending the required session headers; DeepSeek Flash models now accept image attachments, and web search is limited to DeepSeek V4 Pro because Flash models silently ignore it (#10551) by @cgyrock
[AI: Knowledge base] Resolve referenced knowledge base documents for AI employee chat responses by @cgyrock

🚀 Improvements

[client-v2] Table column quick edit: support setting a data scope for association fields (#10547) by @katherinehhh

🐛 Bug Fixes

[client-v2]
- Fix the issue where the "Current popup parent record" variable is missing in quick create popups of association fields in approval forms (#10554) by @zhangzhonghe
- Fix the issue where signing in with another account after signing out shows a 404 page (#10549) by @zhangzhonghe
- Fixed saving attachment and file relation changes inside approval form sub-tables. (#10544) by @mytharcher
[create-nocobase-app] Upgrade js-yaml and uuid (#10555) by @2013xile
[client] Fixed workflow manual node form layouts failing when multiple fields are arranged in one row. (#10545) by @mytharcher
[Workflow] Fix creation of the jobs status and ID index during database sync. (#10552) by @mytharcher
[Workflow: Aggregate node] Fix aggregate field selection for collections selected through to-many associations. (#10543) by @mytharcher
[Block: GridCard] Fixed Grid Card pagination switching and aligned simple-pagination page sizes with the configured column count (#10541) by @jiannx
[Action: Batch update] Prevent bulk update actions from submitting option values that no longer exist in the configured collection field. (#10540) by @jiannx
[Migration manager] Updated decompress to @xhmikosr/decompress 11.1.4 by @2013xile

develop

v2.4.0-alpha.9

Release date: 2026-09-30

🎉 New Features

[AI employees]
- AI employee chat responses expose the referenced knowledge base documents (#10560) by @cgyrock
- Added support for OpenCode Zen / Go as an LLM service by sending the required session headers; DeepSeek Flash models now accept image attachments, and web search is limited to DeepSeek V4 Pro because Flash models silently ignore it (#10551) by @cgyrock
[AI: Knowledge base] Resolve referenced knowledge base documents for AI employee chat responses by @cgyrock

🚀 Improvements

[client-v2] Table column quick edit: support setting a data scope for association fields (#10547) by @katherinehhh

🐛 Bug Fixes

[sdk] Upgraded axios to 1.20.0 (#10566) by @2013xile
[client-v2]
- Fix the issue where the "Current popup parent record" variable is missing in quick create popups of association fields in approval forms (#10554) by @zhangzhonghe
- Fixed saving attachment and file relation changes inside approval form sub-tables. (#10544) by @mytharcher
- Fix the issue where signing in with another account after signing out shows a 404 page (#10549) by @zhangzhonghe
[client] Fixed workflow manual node form layouts failing when multiple fields are arranged in one row. (#10545) by @mytharcher
[create-nocobase-app] Upgrade js-yaml and uuid (#10555) by @2013xile
[Workflow: Aggregate node] Fix aggregate field selection for collections selected through to-many associations. (#10543) by @mytharcher
[Block: GridCard] Fixed Grid Card pagination switching and aligned simple-pagination page sizes with the configured column count (#10541) by @jiannx
[Workflow] Fix creation of the jobs status and ID index during database sync. (#10552) by @mytharcher
[Action: Batch update] Prevent bulk update actions from submitting option values that no longer exist in the configured collection field. (#10540) by @jiannx
[Block: Kanban] Fixed Kanban layout flicker when adding an AI employee action. (#10553) by @jiannx
[Data source: External NocoBase] Fixed the type build failure caused by the axios 1.20.0 upgrade by @2013xile
[Migration manager] Updated decompress to @xhmikosr/decompress 11.1.4 by @2013xile
[Data source: External Oracle] Fixed a type error surfaced by the axios 1.20.0 upgrade by @2013xile
[Workflow: Approval] Fix the issue where hidden field labels reappear and field values are empty in submitted approval details by @zhangzhonghe

Weekly Updates: Improvements and Bug Fixes

NocoBase — Sat, 26 Sep 2026 16:10:03 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.17

Release date: 2026-09-24

🐛 Bug Fixes

[client-v2]
- Fix: sub-table fields were still editable after the field was set to disabled (#10532) by @katherinehhh
- Fixed quick edit popover closing when collapsing a multi-select dropdown, and dropdown options covering the Submit button. (#10536) by @katherinehhh
[Departments] Restricted department user directory access to authorized roles (#10539) by @2013xile
[Workflow] Fixed workflow user selection search to query the API instead of filtering only loaded users. (#10537) by @mytharcher
[Block: Kanban] Fixed modern kanban blocks not refreshing after adding records through the toolbar when no filters were active. (#10525) by @jiannx
[Email manager] Prevent circular email reply relationships from blocking mail synchronization by @jiannx

v2.2.16

Release date: 2026-09-21

🐛 Bug Fixes

[Access control] Fixed unintended permission changes when clicking the blank space beside system permission checkboxes in the modern client's role settings. (#10518) by @jiannx
[Block: Comment] Fixed comment-specific Edit, Delete, and Quote reply actions incorrectly appearing in the table row action configuration menu. (#10519) by @jiannx
[Workflow: Approval] Fixed data not being saved correctly after a before-save approval is returned, resubmitted, and approved. by @mytharcher

v2.2.15

Release date: 2026-09-19

🚀 Improvements

[Data source manager] In the v2 data source manager, the relation field's foreign key can be selected from the existing columns of the owning collection, like v1. (#10526) by @katherinehhh

🐛 Bug Fixes

[flow-engine] Fixed number precision validation in V2 forms accepting values with too many decimal places. (#10512) by @katherinehhh
[client-v2] Fixed inconsistent v2 subtable row heights before and after adding fields. (#10520) by @katherinehhh
[File manager] Enabled knowledge-base document downloads to use the same file download handling as file-manager. (#10513) by @cgyrock
[Data source manager]
- Fixed submission errors when editing relation fields with existing inverse fields in the v2 data source manager. (#10521) by @katherinehhh
- Fixed empty inverse relationship types when adding an inverse field to an existing relationship in the v2 data source editor. (#10511) by @katherinehhh
- Fixed incorrect duplicate-name validation when recreating deleted fields in v2 data source settings. (#10509) by @katherinehhh
[AI employees]
- Improved AI conversation prompt-cache reuse after frontend tools finish by keeping the conversation time context stable. (#10517) by @cgyrock
- Fixed AI employee settings not being saveable when the knowledge base was turned off but its retrieval fields were empty (#10507) by @cgyrock
[Workflow] Fixed disappearing to-many field assignments when reopening workflow update nodes in v2, and changed association selections to store keys and load record labels by key. (#10523) by @mytharcher
[AI: Knowledge base] Improved knowledge-base document deletion with a modal confirmation showing the filename and localized buttons, and unified document download handling with file-manager. by @cgyrock
[Workflow: Approval] Fixed approval tasks not opening from the Related approvals block on native V2 pages. by @mytharcher
[WeCom] Fix duplicate slashes in WeCom authorization and callback URLs when Origin has a trailing slash. by @chenzhizdt

v2.3.0-beta.12

Release date: 2026-09-24

🐛 Bug Fixes

[client-v2]
- Fixed quick edit popover closing when collapsing a multi-select dropdown, and dropdown options covering the Submit button. (#10536) by @katherinehhh
- Fix: sub-table fields were still editable after the field was set to disabled (#10532) by @katherinehhh
[Block: Kanban] Fixed modern kanban blocks not refreshing after adding records through the toolbar when no filters were active. (#10525) by @jiannx
[Workflow] Fixed workflow user selection search to query the API instead of filtering only loaded users. (#10537) by @mytharcher
[Departments] Restricted department user directory access to authorized roles (#10539) by @2013xile
[Email manager] Prevent circular email reply relationships from blocking mail synchronization by @jiannx

v2.3.0-beta.11

Release date: 2026-09-20

🚀 Improvements

[Data source manager] In the v2 data source manager, the relation field's foreign key can be selected from the existing columns of the owning collection, like v1. (#10526) by @katherinehhh
[WeCom] Support configurable WeCom sync email types and consistent email mapping for full and incremental synchronization. by @chenzhizdt

🐛 Bug Fixes

[client-v2] Fixed inconsistent v2 subtable row heights before and after adding fields. (#10520) by @katherinehhh
[flow-engine] Fixed number precision validation in V2 forms accepting values with too many decimal places. (#10512) by @katherinehhh
[server] Prevent secret environment variable exposure in custom request URLs (#10503) by @2013xile
[File manager]
- Enabled knowledge-base document downloads to use the same file download handling as file-manager. (#10513) by @cgyrock
- Move the delete button on v2 attachment and Attachment (URL) cards to the top-right corner to reduce accidental deletion during preview. (#10508) by @katherinehhh
[Workflow] Fixed disappearing to-many field assignments when reopening workflow update nodes in v2, and changed association selections to store keys and load record labels by key. (#10523) by @mytharcher
[Block: Comment] Fixed comment-specific Edit, Delete, and Quote reply actions incorrectly appearing in the table row action configuration menu. (#10519) by @jiannx
[Data source manager]
- Fixed submission errors when editing relation fields with existing inverse fields in the v2 data source manager. (#10521) by @katherinehhh
- Fixed empty inverse relationship types when adding an inverse field to an existing relationship in the v2 data source editor. (#10511) by @katherinehhh
- Fixed incorrect duplicate-name validation when recreating deleted fields in v2 data source settings. (#10509) by @katherinehhh
[AI employees]
- Fixed AI employee settings not being saveable when the knowledge base was turned off but its retrieval fields were empty (#10507) by @cgyrock
- Improved AI conversation prompt-cache reuse after frontend tools finish by keeping the conversation time context stable. (#10517) by @cgyrock
- Fixed AI employee data query tools returning no records when the collection's role permission uses a data scope based on the current user (#10501) by @cgyrock
[Collection field: Sequence] Fix sequence field validation for random character patterns configured with multiple character sets. (#10504) by @mytharcher
[Access control] Fixed unintended permission changes when clicking the blank space beside system permission checkboxes in the modern client's role settings. (#10518) by @jiannx
[AI: Knowledge base] Improved knowledge-base document deletion with a modal confirmation showing the filename and localized buttons, and unified document download handling with file-manager. by @cgyrock
[Workflow: Approval]
- Fixed data not being saved correctly after a before-save approval is returned, resubmitted, and approved. by @mytharcher
- Hide approval action buttons for queued sequential approvers and show a waiting hint. by @mytharcher
- Fixed approval tasks not opening from the Related approvals block on native V2 pages. by @mytharcher
[WeCom] Fix duplicate slashes in WeCom authorization and callback URLs when Origin has a trailing slash. by @chenzhizdt

develop

v2.4.0-alpha.8

Release date: 2026-09-24

🐛 Bug Fixes

[client-v2]
- Fix: sub-table fields were still editable after the field was set to disabled (#10532) by @katherinehhh
- Fixed quick edit popover closing when collapsing a multi-select dropdown, and dropdown options covering the Submit button. (#10536) by @katherinehhh
[Workflow] Fixed workflow user selection search to query the API instead of filtering only loaded users. (#10537) by @mytharcher
[Portal manager] Fix the issue where the workflow task center page is missing the top navigation bar (#10535) by @zhangzhonghe
[Departments] Restricted department user directory access to authorized roles (#10539) by @2013xile
[Block: Kanban] Fixed modern kanban blocks not refreshing after adding records through the toolbar when no filters were active. (#10525) by @jiannx
[Email manager] Prevent circular email reply relationships from blocking mail synchronization by @jiannx

v2.4.0-alpha.7

Release date: 2026-09-20

🚀 Improvements

[Data source manager] In the v2 data source manager, the relation field's foreign key can be selected from the existing columns of the owning collection, like v1. (#10526) by @katherinehhh
[WeCom] Support configurable WeCom sync email types and consistent email mapping for full and incremental synchronization. by @chenzhizdt

🐛 Bug Fixes

[client-v2] Fixed inconsistent v2 subtable row heights before and after adding fields. (#10520) by @katherinehhh
[flow-engine] Fixed number precision validation in V2 forms accepting values with too many decimal places. (#10512) by @katherinehhh
[Block: Comment] Fixed comment-specific Edit, Delete, and Quote reply actions incorrectly appearing in the table row action configuration menu. (#10519) by @jiannx
[Access control] Fixed unintended permission changes when clicking the blank space beside system permission checkboxes in the modern client's role settings. (#10518) by @jiannx
[Workflow] Fixed disappearing to-many field assignments when reopening workflow update nodes in v2, and changed association selections to store keys and load record labels by key. (#10523) by @mytharcher
[AI employees]
- Improved AI conversation prompt-cache reuse after frontend tools finish by keeping the conversation time context stable. (#10517) by @cgyrock
- Fixed AI employee settings not being saveable when the knowledge base was turned off but its retrieval fields were empty (#10507) by @cgyrock
[File manager]
- Enabled knowledge-base document downloads to use the same file download handling as file-manager. (#10513) by @cgyrock
- Move the delete button on v2 attachment and Attachment (URL) cards to the top-right corner to reduce accidental deletion during preview. (#10508) by @katherinehhh
[Data source manager]
- Fixed empty inverse relationship types when adding an inverse field to an existing relationship in the v2 data source editor. (#10511) by @katherinehhh
- Fixed submission errors when editing relation fields with existing inverse fields in the v2 data source manager. (#10521) by @katherinehhh
- Fixed incorrect duplicate-name validation when recreating deleted fields in v2 data source settings. (#10509) by @katherinehhh
[Collection field: Sequence] Fix sequence field validation for random character patterns configured with multiple character sets. (#10504) by @mytharcher
[AI: Knowledge base] Improved knowledge-base document deletion with a modal confirmation showing the filename and localized buttons, and unified document download handling with file-manager. by @cgyrock
[Workflow: Approval]
- Hide approval action buttons for queued sequential approvers and show a waiting hint. by @mytharcher
- Fixed approval tasks not opening from the Related approvals block on native V2 pages. by @mytharcher
- Fixed data not being saved correctly after a before-save approval is returned, resubmitted, and approved. by @mytharcher
[WeCom]
- Resolve the merge conflict between develop and next while preserving both URL handling changes. by @chenzhizdt
- Fix duplicate slashes in WeCom authorization and callback URLs when Origin has a trailing slash. by @chenzhizdt

How to Build a Real-World Business System with AI and NocoBase: A Car Rental Management Example

NocoBase — Sat, 19 Sep 2026 16:07:28 +0000

Originally published at https://www.nocobase.com/en/blog/build-car-rental-management-system-with-ai-and-nocobase

Recently, an iceberg chart titled “Vibe Coding vs. Production Reality” sparked discussion on X and Reddit. Above the waterline are today's AI Coding tools. Below it are permissions, payments, data consistency, logs, rollbacks, monitoring, and all the issues that only surface once a system goes live. The original poster noted that a PoC that once took a week can now be built in an afternoon, but a working demo is not the same as a system that can be delivered and maintained continuously.

Business processes and management rules vary significantly from company to company. Even when two businesses are both managing resources, the underlying logic for orders, scheduling, maintenance, settlement, and exceptions can be completely different. AI Coding lowers the cost of implementing these custom requirements, but it does not make the business itself simpler.

Take car rental as an example. An order does not simply get created and wait to be completed. It occupies vehicle availability, goes through handover, use, and return, and if the customer returns the vehicle late, it can affect later bookings and fleet scheduling.

Enterprise business systems like this need to maintain stable data relationships, permissions, and business rules over the long term. If a Coding Agent builds everything completely from scratch, these common capabilities also need to be implemented and maintained one by one. With an existing application foundation, the Coding Agent can focus more of its effort on modeling, implementing, and validating the specific business.

NocoBase is built around App Foundation, providing data models, permissions, workflows, UI, APIs, and runtime mechanisms. Coding Agents build and deliver applications on top of these capabilities, while people confirm business goals, make decisions on proposed solutions, accept results, and authorize releases.

Next, we will use a car rental system as an example. Starting from business modeling, we will see how a Coding Agent can turn a set of realistic, interconnected business requirements into an application that can keep running and evolving on NocoBase.

💡 Further reading: Building an Inventory Management System: Vibe Coding vs NocoBase + AI

1. Let the Coding Agent Build a Complete Business Model

Before development begins, you can give the core car-rental requirements to the Coding Agent and ask it to organize the data model, business processes, role permissions, and acceptance criteria.

📃 Related documentation: Data Modeling - NocoBase Documentation

For example:

We need to manage vehicles, customers, locations, employees, and rental orders. Vehicles involve insurance, maintenance, and traffic violations, while orders are linked to customers, vehicles, rental periods, and payment information. The rental process includes scheduling, vehicle handover, use, return, inspection, and settlement, while also handling cancellations, late returns, maintenance, violations, and outstanding payments. Please organize the core data relationships, business processes, role permissions, and key acceptance criteria.

Based on this, the Coding Agent can produce a complete system plan:

Establish relationships between vehicles and locations, orders, maintenance records, insurance, and other data;
Move orders through creation, scheduling, handover, rental, return, and settlement;
Define explicit handling rules for exceptions and turn them into verifiable conditions, such as preventing the same vehicle from being assigned to overlapping periods, preventing vehicles under maintenance from entering new schedules, and correctly generating receivables after an order is completed.

Once the plan is confirmed, the Coding Agent can use NocoBase App Foundation to turn these agreed business rules into a working application.

2. Let the Coding Agent Build the System on NocoBase

2.1 Turn the Business Model into Working Pages

These business models are then turned into different working pages. In this car rental system, the main pages include:

Rental desk: handle vehicle handover, return, cancellation, late return, and outstanding balances;
Fleet schedule: view current and future vehicle occupancy;
Vehicle dispatch: manage vehicle allocation between locations;
Expiry and compliance management: manage upcoming insurance, license, and maintenance deadlines;
Payment management: handle rent, deposits, refunds, and receivables;
Operations dashboard: view orders, vehicles, exceptions, and business metrics.

These pages all use the same business data and relationships. When an order changes, vehicle status, schedules, payments, and business metrics update accordingly.

📃 Related documentation: UI Builder - NocoBase Documentation

2.2 Follow One Order Through the Full Business Process

Once the application is built, you can use a single order to verify the main process, focusing on whether the vehicle schedule, vehicle status, and payment records update correctly as the order status changes.

After an order confirms the vehicle and rental period, the corresponding time slot needs to be added to the fleet schedule. A vehicle already occupied by an order cannot be assigned again during an overlapping period.

At handover time, staff complete the vehicle handover in the rental desk. The order enters the rental stage and the vehicle status updates at the same time. Return, cancellation, late return, and outstanding-balance handling continue from the same workspace.

When the vehicle is returned, the system needs to record the actual return time, mileage, and charges. If the return is late, the system calculates the relevant fees according to the defined rules. After vehicle inspection is completed, the vehicle status is updated based on the inspection result.

After the order is completed, rent, deposits, and other charges move into payment management, where the amount, payment type, payment method, and current status are retained.

At this point, one rental has completed the full process from order to settlement:

Order → Scheduling → Handover → Rental → Return → Settlement

2.3 Use Workflows for Automated Rules and Cross-Module Coordination

Some rules do not need to be handled manually each time. They can be executed automatically by workflows when the relevant conditions are met.

📃 Related documentation: Workflow Management - NocoBase Documentation

This system already includes workflows for late returns, insurance and driver's-license expiry, vehicle maintenance, receivable generation after order completion, and moving an order into the pickup process when the scheduled time arrives.

Take traffic violations as an example. After a violation record is created, the system looks up the rental order that corresponds to the vehicle and the time of the violation. If a match is found, the order is linked automatically, making it easier to identify the actual driver and determine responsibility later.

This rule can be expressed as:

New violation → Find corresponding rental order → Check for a match → Link the order automatically

Similar reminders, status updates, and cross-module operations can all be configured in workflows using a “trigger condition → business decision → action” structure, so agreed business rules continue to run consistently.

2.4 Handle Exceptions, Compliance, and Business Analysis

Once orders can move through the normal process, issues that require human attention also need clear handling paths.

For example, a late vehicle return can create a pending task; insurance, driver's-license, or maintenance deadlines can enter expiry and compliance management; and unpaid balances or overdue receivables can enter cash-flow and aging analysis.

As this business data accumulates, it can also be used for operational analysis. In vehicle profitability analysis, rental revenue can be combined with maintenance, insurance, and other costs to evaluate the actual return of different vehicles.

Order, vehicle, compliance, and financial data can also be summarized in the operations dashboard, making it easier for managers to see current pending items, exceptions, and key business metrics.

💡 Further reading: Build an Interactive Operations Dashboard with NocoBase

2.5 Test, Accept, and Release Against the Acceptance Criteria

Once the system is complete, it can be tested against the acceptance criteria confirmed earlier, checking whether key rules such as vehicle scheduling, status changes, receivable generation, and exception handling behave as expected.

The Coding Agent runs the tests and fixes the issues it finds, then revalidates the affected processes after each change. Once the key rules pass, people complete acceptance and authorize the release. The Coding Agent then performs the deployment and checks the runtime result.

📃 Related documentation: Version Control - NocoBase Documentation

Coding Agent implementation and testing → Human acceptance and release authorization → Coding Agent release and runtime verification

These acceptance criteria can also be retained. When the system changes later, the same checks can be rerun to confirm whether new functionality affects existing business rules.

3. Using and Iterating the System After Launch

After the system goes live, AI enters two different work scenarios:

Coding Agent continues to handle application changes, testing, and delivery;
AI Employees read business data, call tools, and handle specific tasks inside the running system.

They can use the same underlying models, but their identities, permissions, and scopes of work need to be managed separately.

3.1 Let AI Employees Handle Daily Tasks with Business Context

Once vehicle, order, scheduling, payment, and compliance data are in the system, AI Employees can directly use that business data within the permissions they have been granted.

💡 Further reading: Automating Company Background Research with Built-in Workflows and AI Employees - NocoBase

For example, from the operations dashboard, an AI Employee can query the orders that need attention today, vehicles with exceptions, or current revenue.

In vehicle dispatch, it can suggest how vehicles should be reallocated based on the vehicles available at each location and current orders, with business staff making the final decision.

Which data an AI Employee can read, which tools it can call, and whether it can perform a specific action are all determined by the corresponding business permissions and tool configuration.

📃 Related documentation: How AI Employees Control Usage and Data Access Permissions

3.2 Keep Iterating on the Existing System

Business rules continue to change after a system goes live. A company may add new locations, adjust pricing, change insurance inspection methods, connect new payment methods, or add new business metrics.

These requirements can be handed back to the Coding Agent, which can modify the existing data models, pages, permissions, and workflows directly.

For example, if the business wants to add “dynamic peak-period pricing,” it only needs to provide the applicable conditions, pricing rules, and expected results. The Coding Agent can propose changes based on the existing vehicle, order, and pricing structure, then implement and test them after confirmation, and deliver the update through the same acceptance and release process.

In this way, later iterations can focus mainly on the parts of the business that have changed, while confirmed data relationships and business rules remain in place.

Conclusion

The use cases for AI + NocoBase are not limited to large enterprise systems. Individuals, small teams, and business departments can also start with smaller requirements, such as an internal tool, approval application, asset register, or simple operations system, and let the Coding Agent build the data model, pages, and workflows on top of the existing application foundation.

If this article was helpful, feel free to share it with others who are interested in AI Coding, enterprise applications, or business-system development.

If you also want to build similar enterprise applications with AI and NocoBase, these complete examples may be useful:

👉 Build a CRM with AI + NocoBase

👉 Build an Enterprise IT Operations System with AI + NocoBase

Related reading:

Weekly Updates : Improvements and Bug Fixes

NocoBase — Fri, 18 Sep 2026 06:39:19 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.14

Release date: 2026-09-16

🚀 Improvements

[WeCom] Support configurable WeCom sync email types and consistent email mapping for full and incremental synchronization. by @chenzhizdt

🐛 Bug Fixes

[server] Prevent secret environment variable exposure in custom request URLs (#10503) by @2013xile
[Collection field: Sequence] Fix sequence field validation for random character patterns configured with multiple character sets. (#10504) by @mytharcher
[File manager] Move the delete button on v2 attachment and Attachment (URL) cards to the top-right corner to reduce accidental deletion during preview. (#10508) by @katherinehhh
[AI employees] Fixed AI employee data query tools returning no records when the collection's role permission uses a data scope based on the current user (#10501) by @cgyrock
[Workflow: Approval] Hide approval action buttons for queued sequential approvers and show a waiting hint. by @mytharcher

v2.2.12

Release date: 2026-09-11

🐛 Bug Fixes

[client-v2] Fixed the issue where variables nested deeper than three levels cannot be used in workflow query node conditions (#10494) by @mytharcher
[Workflow] Fix workflow list loading parameters under MySQL 8.3+ (#10486) by @mytharcher

v2.2.11

Release date: 2026-09-11

🐛 Bug Fixes

[Office File Previewer] Fixed the issue with incorrect URLs being used for Office file previews (#10496) by @mytharcher

v2.3.0-beta.10

Release date: 2026-09-15

🐛 Bug Fixes

[client-v2] Fixed the issue where variables nested deeper than three levels cannot be used in workflow query node conditions (#10494) by @mytharcher
[Workflow] Fix workflow list loading parameters under MySQL 8.3+ (#10486) by @mytharcher
[Office File Previewer] Fixed the issue with incorrect URLs being used for Office file previews (#10496) by @mytharcher

develop

v2.4.0-alpha.6

Release date: 2026-09-15

🚀 Improvements

[utils] Added an option to block server-side requests and redirects to literal IP addresses (#10490) by @2013xile
[client-v2] Improve V2 form QR scanning reliability on iOS. (#10456) by @katherinehhh

🐛 Bug Fixes

[server]
- Prevent secret environment variable exposure in custom request URLs (#10503) by @2013xile
- Fixed misleading preparing status when a subapp deployment environment is unavailable (#10485) by @2013xile
[client-v2]
- Fixed the issue where variables nested deeper than three levels cannot be used in workflow query node conditions (#10494) by @mytharcher
- Fix filter forms not collapsing on mobile (#10479) by @zhangzhonghe
- Fix interrupted option value input for custom radio and checkbox fields in filter forms (#10480) by @zhangzhonghe
- Fixed the v2 Update record field settings failing after an assigned field was deleted. (#10483) by @katherinehhh
- Fix full-page reloads when opening settings pages (#10474) by @zhangzhonghe
- Hide unsupported built-in date variables from workflow create and update field assignments. (#10442) by @mytharcher
- Show the standard deleted-field warning for historical V2 field assignments. (#10484) by @katherinehhh
[AI employees] Fixed AI employee data query tools returning no records when the collection's role permission uses a data scope based on the current user (#10501) by @cgyrock
[Office File Previewer] Fixed the issue with incorrect URLs being used for Office file previews (#10496) by @mytharcher
[Workflow: Delay node] Fixed delay duration variable validation and report invalid resolved values instead of waiting unexpectedly. (#10469) by @mytharcher
[Workflow] Fix workflow list loading parameters under MySQL 8.3+ (#10486) by @mytharcher
[Access control] Fix role permissions so selecting a deeply nested menu also selects all parent menus (#10473) by @zhangzhonghe
[Data source manager] Fixed the inverse-field option not remaining selected when editing a v2 relation field. (#10482) by @katherinehhh
[Flow engine] Fixed non-admin variable resolution in form linkage rules, referenced templates, and scripts. (#10467) by @gchust
[Workflow: Approval] Fix approval cards showing outdated content after saving an edited draft by @zhangzhonghe
[App supervisor] Fixed subapp access failures after rolling updates or deployment environment changes by @2013xile

Weekly Updates: Improvements and Bug Fixes

NocoBase — Fri, 11 Sep 2026 09:42:33 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.10

Release date: 2026-09-10

🚀 Improvements

[utils] Added an option to block server-side requests and redirects to literal IP addresses (#10490) by @2013xile
[client-v2] Improve V2 form QR scanning reliability on iOS. (#10456) by @katherinehhh

🐛 Bug Fixes

[client-v2] Hide unsupported built-in date variables from workflow create and update field assignments. (#10442) by @mytharcher
[server] Fixed misleading preparing status when a subapp deployment environment is unavailable (#10485) by @2013xile
[Workflow: Delay node] Fixed delay duration variable validation and report invalid resolved values instead of waiting unexpectedly. (#10469) by @mytharcher
[App supervisor] Fixed subapp access failures after rolling updates or deployment environment changes by @2013xile

v2.2.9

Release date: 2026-09-09

🐛 Bug Fixes

[client-v2]
- Fixed the v2 Update record field settings failing after an assigned field was deleted. (#10483) by @katherinehhh
- Show the standard deleted-field warning for historical V2 field assignments. (#10484) by @katherinehhh
- Fix filter forms not collapsing on mobile (#10479) by @zhangzhonghe
- Support displaying to-many association fields as read-only subtables in client v2 forms. (#10478) by @katherinehhh
- Fix nested association fields rendering blank in V2 forms when the parent relation uses dropdown selection. (#10477) by @katherinehhh
- Fixed the inverse relationship type being editable in v2 field configuration. (#10476) by @katherinehhh
- Fix interrupted option value input for custom radio and checkbox fields in filter forms (#10480) by @zhangzhonghe
- Fix full-page reloads when opening settings pages (#10474) by @zhangzhonghe
[cli] Restrict legacy local upload URLs to signed-in users by default, with an opt-in compatibility switch for public access. (#10471) by @mytharcher
[Data source manager] Fixed the inverse-field option not remaining selected when editing a v2 relation field. (#10482) by @katherinehhh
[Flow engine] Fixed non-admin variable resolution in form linkage rules, referenced templates, and scripts. (#10467) by @gchust
[Access control] Fix role permissions so selecting a deeply nested menu also selects all parent menus (#10473) by @zhangzhonghe
[Block: Kanban] Fixed an issue where newly created records were not immediately visible in the Kanban block. (#10463) by @gaurangagar
[Workflow: Approval] Fix approval cards showing outdated content after saving an edited draft by @zhangzhonghe

v2.2.8

Release date: 2026-09-08

🚀 Improvements

[WeCom] Improved type safety and unified the notification recipient selector in the WeCom plugin. by @chenzhizdt

🐛 Bug Fixes

[server] Fixed applications unexpectedly starting in environments where they were not deployed (#10464) by @2013xile
[Notification: In-app message] Allow all workflow variable types in in-app notification titles and detail links. (#10470) by @mytharcher
[File manager] Prevent file redirects from reusing expired signed storage URLs. (#10475) by @mytharcher
[Data source manager] Added current user and current role variable selection to v2 permission data scopes (#10472) by @jiannx
[Workflow: JavaScript] Fixed an issue where a timed-out JavaScript workflow node could incorrectly abort the workflow instead of respecting "Continue when exception thrown". (#10461) by @mytharcher
[AI employees] Fixed AI employees repeatedly querying knowledge bases when the Knowledge Base Prompt omitted the retrieved-content placeholder, and added clear validation guidance when saving the configuration. (#10413) by @cgyrock
[AI: Knowledge base] Fixed PGVector connection testing, ZIP import result display, document segment-setting inheritance, and validation for chunk overlap values in AI knowledge bases. by @cgyrock
[App supervisor] Fixed exposure of sub-application authentication secrets in application management responses by @2013xile
[DingTalk] Unified the DingTalk notification recipient selector. by @chenzhizdt

v2.2.7

Release date: 2026-09-05

🎉 New Features

[AI: Knowledge base] Added an authenticated knowledge base retrieval API and a built-in provider for connecting remote NocoBase knowledge bases. by @cgyrock

🚀 Improvements

[undefined] Corrected the root package license metadata to Apache-2.0 and raised the Node.js requirement to version 22 (#10448) by @hongboji
[Notification: In-app message] Fixed frontend freezing after selecting an in-app message or email channel in workflow v2 notification nodes (#10445) by @jiannx
[DingTalk] DingTalk ActionCard button links can now be configured to open in an external browser. by @chenzhizdt

🐛 Bug Fixes

[Collection: SQL] Restricted SQL collections from querying PostgreSQL system objects or executing multiple statements (#10455) by @2013xile
[Block: Comment] Fixed the record comments block to display the commenter's nickname when using the Last modified by field (#10446) by @jiannx
[AI employees]
- Prevented Bedrock errors caused by aborted AI responses leaving tool calls without matching tool results. (#10447) by @cgyrock
- Fixed an error that prevented business analysis reports containing charts from opening. (#10440) by @cgyrock
[Collection field: Markdown(Vditor)] Fix Vditor detail fields to use HTML preview by default so Markdown images can be displayed. (#10459) by @mytharcher
[Data source manager] Fix the missing record unique key setting in the v2 collection editor. (#10453) by @katherinehhh
[Workflow] Fixed workflow user selection when a user-related collection uses its primary key as the user foreign key (#10354) by @mytharcher
[File manager] Fixed AI employee workflow nodes failing to access NocoBase permanent file URLs and unnecessarily copying internal files to AI storage. (#10408) by @cgyrock
[AI: Knowledge base] Knowledge base uploads now allow all document formats supported by the backend by @cgyrock
[Template print] Fix dynamic image rendering for stable file URLs in template printing. by @hongboji

v2.3.0-beta.9

Release date: 2026-09-10

🚀 Improvements

[utils] Added an option to block server-side requests and redirects to literal IP addresses (#10490) by @2013xile
[client-v2] Improve V2 form QR scanning reliability on iOS. (#10456) by @katherinehhh
[WeCom] Improved type safety and unified the notification recipient selector in the WeCom plugin. by @chenzhizdt

🐛 Bug Fixes

[client-v2]
- Hide unsupported built-in date variables from workflow create and update field assignments. (#10442) by @mytharcher
- Fix full-page reloads when opening settings pages (#10474) by @zhangzhonghe
- Fixed the v2 Update record field settings failing after an assigned field was deleted. (#10483) by @katherinehhh
- Show the standard deleted-field warning for historical V2 field assignments. (#10484) by @katherinehhh
- Fix interrupted option value input for custom radio and checkbox fields in filter forms (#10480) by @zhangzhonghe
- Support displaying to-many association fields as read-only subtables in client v2 forms. (#10478) by @katherinehhh
- Fix nested association fields rendering blank in V2 forms when the parent relation uses dropdown selection. (#10477) by @katherinehhh
- Fixed the inverse relationship type being editable in v2 field configuration. (#10476) by @katherinehhh
- Fix filter forms not collapsing on mobile (#10479) by @zhangzhonghe
[server] Fixed misleading preparing status when a subapp deployment environment is unavailable (#10485) by @2013xile
[cli] Restrict legacy local upload URLs to signed-in users by default, with an opt-in compatibility switch for public access. (#10471) by @mytharcher
[Workflow: Delay node] Fixed delay duration variable validation and report invalid resolved values instead of waiting unexpectedly. (#10469) by @mytharcher
[Data source manager]
- Fixed the inverse-field option not remaining selected when editing a v2 relation field. (#10482) by @katherinehhh
- Added current user and current role variable selection to v2 permission data scopes (#10472) by @jiannx
[Notification: In-app message] Allow all workflow variable types in in-app notification titles and detail links. (#10470) by @mytharcher
[Access control] Fix role permissions so selecting a deeply nested menu also selects all parent menus (#10473) by @zhangzhonghe
[Block: Kanban] Fixed an issue where newly created records were not immediately visible in the Kanban block. (#10463) by @gaurangagar
[File manager] Prevent file redirects from reusing expired signed storage URLs. (#10475) by @mytharcher
[Flow engine] Fixed non-admin variable resolution in form linkage rules, referenced templates, and scripts. (#10467) by @gchust
[Workflow: Approval] Fix approval cards showing outdated content after saving an edited draft by @zhangzhonghe
[App supervisor] Fixed subapp access failures after rolling updates or deployment environment changes by @2013xile

v2.3.0-beta.8

Release date: 2026-09-07

🎉 New Features

[AI: Knowledge base] Added an authenticated knowledge base retrieval API and a built-in provider for connecting remote NocoBase knowledge bases. by @cgyrock

🚀 Improvements

[Notification: In-app message] Fixed frontend freezing after selecting an in-app message or email channel in workflow v2 notification nodes (#10445) by @jiannx

🐛 Bug Fixes

[server] Fixed applications unexpectedly starting in environments where they were not deployed (#10464) by @2013xile
[AI employees]
- Fixed AI employees repeatedly querying knowledge bases when the Knowledge Base Prompt omitted the retrieved-content placeholder, and added clear validation guidance when saving the configuration. (#10413) by @cgyrock
- Prevented Bedrock errors caused by aborted AI responses leaving tool calls without matching tool results. (#10447) by @cgyrock
[Collection field: Markdown(Vditor)] Fix Vditor detail fields to use HTML preview by default so Markdown images can be displayed. (#10459) by @mytharcher
[Collection: SQL] Restricted SQL collections from querying PostgreSQL system objects or executing multiple statements (#10455) by @2013xile
[Block: Comment] Fixed the record comments block to display the commenter's nickname when using the Last modified by field (#10446) by @jiannx
[Workflow] Fixed workflow user selection when a user-related collection uses its primary key as the user foreign key (#10354) by @mytharcher
[Data source manager] Fix the missing record unique key setting in the v2 collection editor. (#10453) by @katherinehhh
[Workflow: JavaScript] Fixed an issue where a timed-out JavaScript workflow node could incorrectly abort the workflow instead of respecting "Continue when exception thrown". (#10461) by @mytharcher
[AI: Knowledge base]
- Knowledge base uploads now allow all document formats supported by the backend by @cgyrock
- Fixed PGVector connection testing, ZIP import result display, document segment-setting inheritance, and validation for chunk overlap values in AI knowledge bases. by @cgyrock
[Template print] Fix dynamic image rendering for stable file URLs in template printing. by @hongboji
[App supervisor] Fixed exposure of sub-application authentication secrets in application management responses by @2013xile
[DingTalk] Unified the DingTalk notification recipient selector. by @chenzhizdt

develop

v2.4.0-alpha.5

Release date: 2026-09-09

🚀 Improvements

[WeCom] Improved type safety and unified the notification recipient selector in the WeCom plugin. by @chenzhizdt

🐛 Bug Fixes

[client-v2]
- Support displaying to-many association fields as read-only subtables in client v2 forms. (#10478) by @katherinehhh
- Fixed the inverse relationship type being editable in v2 field configuration. (#10476) by @katherinehhh
- Fix nested association fields rendering blank in V2 forms when the parent relation uses dropdown selection. (#10477) by @katherinehhh
[cli] Restrict legacy local upload URLs to signed-in users by default, with an opt-in compatibility switch for public access. (#10471) by @mytharcher
[Workflow: JavaScript] Fixed an issue where a timed-out JavaScript workflow node could incorrectly abort the workflow instead of respecting "Continue when exception thrown". (#10461) by @mytharcher
[File manager] Prevent file redirects from reusing expired signed storage URLs. (#10475) by @mytharcher
[Notification: In-app message] Allow all workflow variable types in in-app notification titles and detail links. (#10470) by @mytharcher
[Data source manager] Added current user and current role variable selection to v2 permission data scopes (#10472) by @jiannx
[Block: Kanban] Fixed an issue where newly created records were not immediately visible in the Kanban block. (#10463) by @gaurangagar
[DingTalk] Unified the DingTalk notification recipient selector. by @chenzhizdt

v2.4.0-alpha.4

Release date: 2026-09-06

🎉 New Features

[AI: Knowledge base] Added an authenticated knowledge base retrieval API and a built-in provider for connecting remote NocoBase knowledge bases. by @cgyrock

🚀 Improvements

[Notification: In-app message] Fixed frontend freezing after selecting an in-app message or email channel in workflow v2 notification nodes (#10445) by @jiannx

🐛 Bug Fixes

[server] Fixed applications unexpectedly starting in environments where they were not deployed (#10464) by @2013xile
[Collection field: Markdown(Vditor)] Fix Vditor detail fields to use HTML preview by default so Markdown images can be displayed. (#10459) by @mytharcher
[AI employees]
- Fixed AI employees repeatedly querying knowledge bases when the Knowledge Base Prompt omitted the retrieved-content placeholder, and added clear validation guidance when saving the configuration. (#10413) by @cgyrock
- Prevented Bedrock errors caused by aborted AI responses leaving tool calls without matching tool results. (#10447) by @cgyrock
[Block: Comment] Fixed the record comments block to display the commenter's nickname when using the Last modified by field (#10446) by @jiannx
[Data source manager] Fix the missing record unique key setting in the v2 collection editor. (#10453) by @katherinehhh
[Workflow] Fixed workflow user selection when a user-related collection uses its primary key as the user foreign key (#10354) by @mytharcher
[Collection: SQL] Restricted SQL collections from querying PostgreSQL system objects or executing multiple statements (#10455) by @2013xile
[AI: Knowledge base]
- Fixed PGVector connection testing, ZIP import result display, document segment-setting inheritance, and validation for chunk overlap values in AI knowledge bases. by @cgyrock
- Knowledge base uploads now allow all document formats supported by the backend by @cgyrock
[Template print] Fix dynamic image rendering for stable file URLs in template printing. by @hongboji
[App supervisor] Fixed exposure of sub-application authentication secrets in application management responses by @2013xile

10 Open-Source AI Agent Platforms for Business: From Automation to Internal Apps

NocoBase — Sat, 05 Sep 2026 14:07:48 +0000

Originally published at https://www.nocobase.com/en/blog/open-source-ai-agent-platforms-for-business

TL;DR

These 10 platforms can be roughly grouped into three categories:

NocoBase, Activepieces, Kestra, and Windmill are better suited to connecting AI with enterprise data, automation, and business processes.
Coze Studio, Langflow, and Dify are better suited to visually building Agents and AI applications.
MaxKB, AnythingLLM, and RAGFlow are better suited to enterprise knowledge bases and RAG.

If a company needs to manage structured business data, permissions, and internal applications, NocoBase is worth considering first. If the main goal is to connect multiple SaaS tools and automate tasks, Activepieces is a strong option. If the focus is building Agents and AI workflows, Dify, Langflow, or Coze Studio are good starting points. If private document Q&A and complex knowledge retrieval matter most, MaxKB, AnythingLLM, or RAGFlow are more suitable.

Introduction

More companies are starting to bring AI Agents into everyday work. Customer follow-up, email organization, task reminders, and data summaries are all examples of repetitive work that can increasingly be handed over to AI.

On Reddit's r/smallbusiness, one small-business owner explained that they already use ChatGPT and want to go further by letting AI handle customer follow-up, email classification, proposal reminders, and weekly summaries. As they researched further, they came across n8n, Zapier, APIs, MCP, and various Agent-building tools. They do not have a development background and do not want to learn an entire technical stack just for a few automation workflows. What made the decision even harder was the maintenance question: if it takes several weeks to build these applications, will they then need constant upkeep and eventually become more complicated than the original way of working?

This is a common problem when businesses choose AI Agent tools. A simple search for “AI Agent” brings up very different types of products: developer frameworks such as LangChain, CrewAI, and Haystack; Agent-building platforms; automation tools; RAG platforms; and enterprise application platforms that can manage business data, pages, permissions, and workflows in the same system.

Based on practical business use cases, this article collects 10 open-source AI Agent projects that support self-hosting and already provide visual applications, workflows, knowledge bases, or business-system capabilities. For each project, we look at the basics, notable AI Agent capabilities, business use cases, and the types of teams it is best suited for.

To keep the scope clear, the projects included here need to meet several basic criteria: the core code is public and actively maintained, self-hosting is supported, Agent, tool-calling, or AI workflow capabilities are already available, and the project provides at least one of the following: visual applications, automation, knowledge bases, or enterprise business systems. Project information and selection guidance are based mainly on official websites, GitHub repositories, and official documentation. This is not a benchmark under a unified test environment or a complete ranking.

💡 If you are more interested in development frameworks such as LangChain and CrewAI and want to compare different Agent frameworks and development platforms, see our earlier article: 8 Open-Source AI Agent Platforms for Internal Tools.

Before going through the projects one by one, you can first scan the list below to understand how their positioning, use cases, and technical requirements differ.

1. Enterprise Applications and Business Automation

1. NocoBase

Website: https://www.nocobase.com/

GitHub: https://github.com/nocobase/nocobase

GitHub Stars: 23.9K

Related documentation

AI Employees: https://docs.nocobase.com/ai-employees/quick-start

AI Builder: https://docs.nocobase.com/ai-builder

NocoBase is an open-source, self-hosted AI no-code platform for enterprise applications. It is mainly used to build CRM systems, ticketing systems, IT management systems, approval workflows, and other internal business applications. It provides the foundational capabilities required by enterprise applications, including data models, pages, permissions, and workflows, while also allowing AI to participate in both application building and later adjustments. AI Employees can also be configured inside the system so AI can combine current business data, tools, and processes to perform analysis, information processing, and task execution.

Core AI Capabilities

AI + no-code application building: Users can describe business requirements in natural language, and AI can create data tables and relationships, pages, workflows, and role permissions. NocoBase provides both a no-code portal and an AI portal. The no-code portal makes it easier for business users to continue adjusting the application visually, while the AI portal is better suited to complex interactions and highly customized pages.

👉 AI Portal Quick Start - NocoBase Documentation

AI Portal:

No-code Portal:

AI Employees and business execution: AI can participate in daily work as a specific role, handling tasks such as data analysis, email organization, and information extraction. It can also use system tools and workflows to query data, fill forms, or trigger business processes.

👉 AI Employees: Using Tools - NocoBase Documentation

Enterprise knowledge base: AI Employees can retrieve enterprise knowledge automatically or on demand, with accessible content filtered according to the current user's role. This allows customer service, sales, or internal assistants to work with the company's own knowledge.

👉 NocoBase AI Knowledge Base Documentation

Enterprise permissions and execution control: AI Employees inherit the current user's data permissions. Important operations such as modifying data can also require confirmation before execution, helping prevent an Agent from gaining access beyond the user's own permission scope.

👉 AI Employee Roles and Permissions - NocoBase Documentation

Business Use Cases

CRM: Organize communication details from customer emails or meeting notes, generate follow-up suggestions, and assist sales using customer, contact, and opportunity data.

Customer support and ticketing: Analyze submitted customer issues, determine category and priority, generate response suggestions using the knowledge base, and participate in ticket-handling workflows.

IT management: Identify IT request types, priorities, and handling suggestions from employees' natural-language descriptions, then work with asset, maintenance, approval, and related business data.

Internal business applications: Configure AI Employees for different roles in procurement, approval, project management, operations, and other systems, allowing them to use business data and workflows to complete routine tasks.

Selection Guidance

NocoBase is a good fit for teams with clearly defined business needs such as CRM, customer support ticketing, IT management, or approvals, especially when they want AI to accelerate application building without asking AI to create an entire business system from scratch. Core capabilities such as data models, permissions, and workflows are already provided by the platform. Business teams can complete most of the setup with no-code tools and AI, then extend the system further through APIs and plugins. It is especially suitable for teams building internal systems that are expected to be used and iterated over the long term.

2. Activepieces

Website: https://www.activepieces.com/

GitHub: https://github.com/activepieces/activepieces

GitHub Stars: 24.0K

Related documentation

MCP: https://www.activepieces.com/docs/mcp/overview

Product Overview

Activepieces is an open-source, self-hosted AI automation platform mainly used to connect the applications, data, and business processes a company already relies on. It brings AI Agents, automation workflows, and data into the same environment and is well suited to sales, customer support, operations, and other work that spans multiple tools.

Core AI Capabilities

Visual AI Agent creation: Users can define an Agent's task, model, and available tools, then place the Agent directly inside automation workflows. Existing workflows can also be reused as Agent tools.

Natural-language automation building: Users can describe what they want to accomplish and let AI generate an Agent or automation workflow. They can then continue editing visually by adding conditions, loops, and code execution.
Connect business tools: The platform can connect more than 700 applications, including CRM systems, email, collaboration tools, spreadsheets, and other commonly used services. Through MCP, tools and workflows built in the platform can also be exposed to other AI clients that support MCP.

Business Use Cases

Sales lead processing: Capture new leads from email or forms, let AI classify customer type and priority, update the CRM, and generate follow-up content.
Customer support workflows: Automatically read customer issues, classify and summarize them, assign tickets, and synchronize information between customer support systems and CRM.
Daily operations automation: Organize email, extract information, synchronize spreadsheets or databases, and automatically generate daily reports, weekly reports, and business notifications from data across multiple systems.

Selection Guidance

Activepieces is better suited to small and midsize teams or business departments that already use several SaaS tools but have limited development resources. Sales, marketing, customer support, and operations teams that frequently move data, send messages, and follow up across multiple systems can start with visual workflows and later add APIs or custom integrations as requirements become more complex.

3. Kestra

Website: https://kestra.io/

GitHub: https://github.com/kestra-io/kestra

GitHub Stars: 28.0K

Related documentation

AI Copilot: https://kestra.io/docs/ai-tools/ai-copilot

Product Overview

Kestra is an open-source, self-hosted workflow orchestration platform mainly used to manage automation across data, AI, and infrastructure. AI Agents can run directly as tasks inside workflows, calling tools, executing other tasks, or triggering existing flows based on their goals.

Core AI Capabilities

AI Agents working with workflows: AI Copilot can generate or modify workflows from natural-language instructions. Agents can also be placed directly inside existing workflows, where they can use models, memory, tools, and existing Kestra tasks and flows, then decide the next step based on execution results.

Visual and code-based development: Workflows can be created and adjusted through the visual interface, while more complex requirements can be extended with YAML, Python, Docker, and custom scripts.

Traceable execution: Agents and regular tasks share the same runtime system, making it possible to inspect execution status, logs, and failure records in one place for easier troubleshooting and maintenance.

Business Use Cases

Data-processing automation: Choose next steps based on data state and call existing workflows to complete cleaning, analysis, and aggregation.
IT and operations workflows: Analyze alerts or system events, then execute checks, notifications, or other follow-up tasks.
Complex business and AI workflows: Combine models, tools, approvals, data processing, and cross-system tasks to handle workflows that require multiple steps and dynamic decisions.

Selection Guidance

Kestra is better suited to teams that already have some automation foundation and have developers, data engineers, or operations specialists involved. Its orchestration capabilities become more valuable when workflows grow longer and need task dependencies, retries, execution-state tracking, and multi-step AI decisions. If a small team only wants to build a few simple business automations quickly, it may not need such a complete workflow system.

4. Windmill

Website: https://www.windmill.dev/

GitHub: https://github.com/windmill-labs/windmill

GitHub Stars: 17.7K

Related documentation

AI Agent applications: https://www.windmill.dev/use-cases/ai-agents

Product Overview

Windmill is an open-source, self-hosted development and automation platform that can run scripts, APIs, workflows, and internal applications in one environment. It supports both visual orchestration and code in Python, TypeScript, Go, SQL, and other languages, making it more suitable for teams with some technical expertise.

Core AI Capabilities

Add Agents to workflows: AI Agents can run directly as workflow steps and be combined with conditions, approvals, error handling, and other nodes to handle tasks that require AI judgment.

Use existing technical resources: Agents can use scripts, databases, APIs, and other workflows already available in Windmill. They can also connect to MCP tools, allowing teams to reuse existing code and internal services directly inside Agent workflows.

Permissions, approvals, and execution records: Teams can limit which resources an Agent can access and execute, require human confirmation before important actions, and inspect tool calls, inputs and outputs, logs, and execution status for each run.

Business Use Cases

IT and operations automation: Analyze problems based on alerts or system state, then call scripts to perform checks, remediation, and notifications.
Data processing and analysis: Query databases or run existing data scripts, let an Agent analyze the results, and trigger subsequent workflows.
Internal AI tools: Combine Agents, backend scripts, and internal app interfaces to build data assistants, operations tools, and other internal applications.

Selection Guidance

Windmill is more suitable for teams that already have developers, data specialists, or operations engineers. If a company has accumulated many scripts, databases, APIs, and internal services and wants to reuse those existing resources for Agents and automation, Windmill can be a natural fit. For teams without technical staff that mainly want to build a few simple workflows visually, its development-platform orientation may feel heavier.

2. Visual AI Agent Building Platforms

5. Coze Studio

Website: https://www.coze.cn/home

GitHub: https://github.com/coze-dev/coze-studio

GitHub Stars: 21.5K

AI Agent documentation: https://github.com/coze-dev/coze-studio/wiki/1.-What-is-Coze-Studio

Product Overview

Coze Studio is an open-source, all-in-one AI Agent development platform from ByteDance. Its main focus is visually creating, debugging, and deploying Agents. Users can combine models, knowledge, and tools directly, making it suitable for quickly building customer-service assistants, knowledge Q&A, content assistants, and other AI applications.

Core AI Capabilities

Visual Agent and workflow building: Configure models, prompts, and tools through the interface, or orchestrate multi-step workflows on a canvas with conditions, data processing, and other logic.

RAG and knowledge bases: Connect enterprise documents and knowledge data so Agents can answer questions and handle tasks based on specified content.
Plugins and external tools: Agents can call external services through plugins, bringing search, queries, data processing, and other capabilities into the execution process.

Development, debugging, and deployment: Agents can be created, tested, and deployed within the same platform, reducing the need to switch between multiple tools.

Business Use Cases

AI customer support: Use knowledge bases to answer product, service, and after-sales questions, while plugins query additional business information.
Enterprise knowledge assistants: Provide employee Q&A, document lookup, and information organization based on internal documents and knowledge bases.
Content and marketing assistants: Combine search, content generation, and workflows for research, content organization, and first-draft creation.

Selection Guidance

Coze Studio is a good fit for teams that are just starting to experiment with AI Agents and want to quickly build customer-service assistants, knowledge Q&A, or content assistants without dedicated AI developers. Product, operations, or business teams can validate ideas visually first, then add knowledge bases, plugins, and more complex workflows as needed.

6. Langflow

Website: https://www.langflow.org/

GitHub: https://github.com/langflow-ai/langflow

GitHub Stars: 153.9K

Related documentation

Agents: https://docs.langflow.org/agents

Product Overview

Langflow is an open-source visual AI application development platform mainly used to build Agents and AI workflows. It combines models, tools, data, and other Agents through modular components while retaining Python extensibility, making it suitable for AI application scenarios that require frequent experimentation and iteration.

Core AI Capabilities

Drag-and-drop building and multi-Agent composition: Configure Agents on a visual canvas and connect models, prompts, tools, and other components into complete workflows. Components and flows can also be used as Agent tools, and multiple Agents can divide work such as retrieval, analysis, and organization.
MCP support: Connect external MCP services or expose workflows built in Langflow to other AI applications that support MCP.

Models and Python extensions: Freely combine different models and data sources. When built-in components do not cover a requirement, custom Python components can connect enterprise APIs and processing logic.

Business Use Cases

Knowledge and document applications: Combine internal documents, retrieval, models, and Agents for knowledge Q&A, document analysis, and information extraction.
Multi-Agent workflows: Let different Agents handle retrieval, analysis, organization, and other tasks, then connect them into one complete process.
AI application prototypes: Quickly validate ideas such as customer support assistants, research assistants, and content-generation tools, then connect them to existing products through APIs.

Selection Guidance

Langflow is better suited to teams with some technical involvement that need to experiment frequently with different models and Agent structures. Product or data teams can first build workflows visually, while developers add more complex functionality through Python, custom components, and APIs. It is well suited to prototyping and continuous experimentation. For teams with no technical staff that only want to launch fixed business workflows quickly, later-stage maintenance may depend more heavily on developers.

7. Dify

Website: https://dify.ai/

GitHub: https://github.com/langgenius/dify

GitHub Stars: 154.0K

Related documentation

Official documentation: https://docs.dify.ai/

Dify is an open-source AI application development platform for building Agents, knowledge assistants, and more complex AI workflows. It covers the full lifecycle from application creation and debugging to publishing and ongoing runtime management, making it suitable for teams that want to develop multiple AI applications continuously within one platform.

Core AI Capabilities

Agent and workflow building: Configure Agent models, instructions, tools, and knowledge bases through the visual interface, or use the canvas to orchestrate multi-step workflows with conditions, knowledge retrieval, tool calls, and human input.

RAG and knowledge processing: Build knowledge bases from PDF, PPT, and other documents, with content cleaning, chunking, indexing, and retrieval testing.

Model and plugin extensions: Connect multiple model providers and add new tools, data sources, triggers, and Agent capabilities through plugins.
Publishing and runtime management: Publish completed applications as web apps or APIs, while monitoring logs, feedback, latency, and usage.

Business Use Cases

AI customer support and knowledge assistants: Combine enterprise knowledge bases and external tools to handle customer inquiries or internal employee knowledge searches.
Business information processing: Connect extraction, classification, analysis, generation, and tool calls into complete workflows.
Rapid AI application launch: Publish completed Agents or workflows as applications or APIs, then integrate them with existing products and business systems.

Selection Guidance

Dify is a good fit when a team has moved beyond experimenting with a single Agent and plans to keep building customer support, knowledge assistants, content-processing tools, and other AI applications. Business and product teams can complete most configuration visually, while developers can add plugins, APIs, and deeper integrations when needed. For small and midsize businesses or product teams that want to manage multiple AI projects on one platform, it can be easier than maintaining several separate tools.

3. Enterprise Knowledge and RAG Agents

8. MaxKB

Website: https://maxkb.cn/

GitHub: https://github.com/1Panel-dev/MaxKB

GitHub Stars: 22.6K

Related documentation

Official documentation: https://maxkb.cn/docs/v2/index.html

Product Overview

MaxKB is an open-source, self-hosted enterprise Agent platform that is well suited to starting with enterprise knowledge bases and knowledge Q&A. In addition to basic RAG, it provides visual workflows and tool-calling capabilities that can be extended into customer support, office assistants, and similar scenarios.

Core AI Capabilities

Enterprise knowledge bases and RAG: Upload documents or crawl online content, then perform chunking, vectorization, and knowledge retrieval for internal materials and professional Q&A.
Visual workflows and tool calling: Combine AI conversation, knowledge retrieval, conditions, forms, document extraction, and other nodes on a canvas. MCP services can also be connected so models can call external tools.
Multiple models and local deployment: Connect public models such as OpenAI, Claude, Gemini, DeepSeek, and Qwen, as well as local models through Ollama, vLLM, and similar tools.
Integration with existing systems: Completed Agents can be embedded into websites and internal applications through public links, embed code, or APIs.

Business Use Cases

AI customer support: Connect product knowledge bases, FAQs, and business materials to an Agent for handling customer inquiries.
Professional knowledge applications: Use industry materials for search, organization, and analysis in finance, education, research, and other specialized scenarios.

Selection Guidance

MaxKB is particularly suitable for teams that already have a large amount of enterprise documentation and knowledge material and want to build knowledge-focused AI Agents relatively quickly. Its visual workflows and knowledge-base capabilities have a relatively low entry barrier, while local deployment and local models make it a good fit for organizations with requirements around internal knowledge use, data control, and third-party system integration.

9. AnythingLLM

Website: https://anythingllm.com/

GitHub: https://github.com/Mintplex-Labs/anything-llm

GitHub Stars: 65.4K

Related documentation

Agent Flow: https://docs.anythingllm.com/agent-flows/overview

Product Overview

AnythingLLM is an open-source, local-first AI application mainly used to build AI assistants based on private documents and internal knowledge. It offers both desktop and self-hosted versions with a relatively complete graphical interface, so teams can start without first setting up a complex development environment.

Core AI Capabilities

Private documents and RAG: Add PDF, Word, text, and other files to separate workspaces so AI can answer questions based on selected content while preserving citations.

Agent Flow: Visually combine web scraping, API calls, model instructions, file reading and writing, and other steps into repeatable processing flows.
Multi-user and permissions: The self-hosted version supports multiple users and permission management, allowing teams to separate workspaces and knowledge access by user or group.

Business Use Cases

Internal knowledge and document assistants: Answer questions, summarize information, and extract data from company policies, product materials, training documents, contracts, and reports.
Research and document organization: Combine internal documents, web information, and tool calls to collect, organize, and analyze information.

Selection Guidance

AnythingLLM is better suited to individuals, small teams, or companies that want to pilot a private AI assistant within a department first. Even without dedicated AI developers, teams can start quickly with document Q&A and information organization. If the main goal is to let AI use internal knowledge securely rather than build complex business workflows, it is a lighter-weight option.

10. RAGFlow

Website: https://ragflow.io/

GitHub: https://github.com/infiniflow/ragflow

GitHub Stars: 89.7K

Related documentation

Agent guide: https://github.com/infiniflow/ragflow/tree/main/docs/guides/agent

Product Overview

RAGFlow is an open-source RAG and AI Agent platform focused on complex document processing and enterprise knowledge retrieval. Compared with simpler knowledge-Q&A tools, it is better suited to scenarios with complex document types, large knowledge volumes, and stronger requirements for retrieval accuracy and source traceability.

Core AI Capabilities

Complex document understanding: Process PDF, Word, PPT, spreadsheets, images, and long documents, extracting information that can be used for retrieval and analysis.
High-accuracy RAG: Combine vector retrieval, keyword search, reranking, and metadata filtering to improve retrieval accuracy and traceability.
Agent workflows: Use a visual canvas to combine retrieval, models, conditions, loops, classification, and other steps. More complex patterns such as multi-Agent workflows, planning, and reflection are also supported.

Tools and data-source integration: Agents can call external tools and support MCP. Enterprise knowledge can also be synchronized from Confluence, S3, Notion, Google Drive, and other sources.

Business Use Cases

Complex enterprise knowledge bases: Build a unified knowledge retrieval system across large collections of policies, technical manuals, reports, and professional materials.
Legal and compliance analysis: Retrieve supporting evidence from regulations, contracts, cases, and internal materials, then generate analysis with sources.
Research and decision support: Combine internal data and external materials so Agents can retrieve, analyze, and generate reports.

Selection Guidance

RAGFlow is suitable for teams with large knowledge volumes, complex documents, and some technical resources. In legal, manufacturing, technical support, research, and similar settings, it has stronger advantages when materials contain many long documents, tables, images, or specialized content and when retrieval accuracy and source evidence matter significantly.

Conclusion

Many AI Agent products are beginning to overlap in functionality. Visual workflows, knowledge bases, MCP, and tool calling are now available on more and more platforms. In practice, teams need to consider whether these capabilities can fit smoothly into existing work and how much additional operational and maintenance overhead they will introduce.

Hopefully, this article helps narrow down the options. Feel free to share it with friends or teams that are also looking for AI Agent tools.

If you want to build similar enterprise applications with AI and NocoBase, these complete examples may be useful:

👉 Build a CRM with AI + NocoBase

👉 Build an Enterprise IT Operations System with AI + NocoBase

Related reading:

Weekly Updates: Improvements and Bug Fixes

NocoBase — Fri, 04 Sep 2026 08:33:13 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.6

Release date: 2026-09-02

🚀 Improvements

[Migration manager] Displayed migration file sizes with readable binary units instead of raw byte counts by @hongboji

🐛 Bug Fixes

[utils] Prevent stored XSS in rich-text fields written through APIs and rendered in display or edit mode. (#10425) by @katherinehhh
[database] Fixed SQL Server string filters failing to match literal square brackets and other LIKE wildcard characters (#10436) by @hongboji
[Collection field: Markdown(Vditor)] Restore table actions in V2 Markdown Vditor fields. (#10438) by @katherinehhh
[File manager] Fixed the missing file storage selector in v2 file collection create and edit forms. (#10439) by @katherinehhh
[File storage: S3(Pro)] Fix S3 Pro multipart upload failures for backup files larger than 5 MB. by @mytharcher

v2.2.5

Release date: 2026-08-31

🐛 Bug Fixes

[Workflow]
- Improve workflow task detail handling on mobile by using a full-width Drawer and responsive task-center presentation. (#10428) by @mytharcher
- Optimized pending workflow job recovery by adding a composite index on job status and ID. (#10427) by @mytharcher
- Fix schedule workflows in static mode running one more time after endsOn (#10411) by @Tespera
[Notification manager] Fix workflow user recipient variables displaying Variable parsing failed and unify user selectors across workflow nodes. (#10432) by @mytharcher
[Workflow: Approval]
- Adapted approval task details and remote forms to narrow mobile viewports. by @mytharcher
- Fix approval assignee variables displaying Variable parsing failed and reuse the shared workflow user selector. by @mytharcher

v2.2.4

Release date: 2026-08-28

🐛 Bug Fixes

[AI: Knowledge base] Fixed AI employees incorrectly reporting no knowledge-base access for root users by @hongboji
[Workflow: Approval] Fixed the approval trigger-variable form not rendering for subflow nodes on v1 workflow pages. by @mytharcher
[DingTalk] Fixed an issue where DingTalk Stream mode synchronization sources could not be submitted in the v1 client. by @chenzhizdt

v2.3.0-beta.6

Release date: 2026-08-31

🐛 Bug Fixes

[Workflow]
- Optimized pending workflow job recovery by adding a composite index on job status and ID. (#10427) by @mytharcher
- Fix schedule workflows in static mode running one more time after endsOn (#10411) by @Tespera
- Improve workflow task detail handling on mobile by using a full-width Drawer and responsive task-center presentation. (#10428) by @mytharcher
[Notification manager] Fix workflow user recipient variables displaying Variable parsing failed and unify user selectors across workflow nodes. (#10432) by @mytharcher
[Workflow: Approval]
- Fix approval assignee variables displaying Variable parsing failed and reuse the shared workflow user selector. by @mytharcher
- Adapted approval task details and remote forms to narrow mobile viewports. by @mytharcher
[DingTalk] Fixed an issue where DingTalk Stream mode synchronization sources could not be submitted in the v1 client. by @chenzhizdt

develop

v2.4.0-alpha.3

Release date: 2026-09-02

🚀 Improvements

[AI employees] Removed the persisted AI context data source settings and selector while keeping direct data source query capabilities. (#10450) by @cgyrock

v2.4.0-alpha.2

Release date: 2026-09-02

🚀 Improvements

[undefined] Corrected the root package license metadata to Apache-2.0 and raised the Node.js requirement to version 22 (#10448) by @hongboji
[DingTalk] DingTalk ActionCard button links can now be configured to open in an external browser. by @chenzhizdt

🐛 Bug Fixes

[File manager] Fixed AI employee workflow nodes failing to access NocoBase permanent file URLs and unnecessarily copying internal files to AI storage. (#10408) by @cgyrock
[AI employees] Fixed an error that prevented business analysis reports containing charts from opening. (#10440) by @cgyrock

v2.4.0-alpha.1

Release date: 2026-09-02

🚀 Improvements

[Migration manager] Displayed migration file sizes with readable binary units instead of raw byte counts by @hongboji

🐛 Bug Fixes

[database] Fixed SQL Server string filters failing to match literal square brackets and other LIKE wildcard characters (#10436) by @hongboji
[utils] Prevent stored XSS in rich-text fields written through APIs and rendered in display or edit mode. (#10425) by @katherinehhh
[Collection field: Markdown(Vditor)] Restore table actions in V2 Markdown Vditor fields. (#10438) by @katherinehhh
[File manager] Fixed the missing file storage selector in v2 file collection create and edit forms. (#10439) by @katherinehhh
[File storage: S3(Pro)] Fix S3 Pro multipart upload failures for backup files larger than 5 MB. by @mytharcher

How to Build a Production-Ready Ticketing System with AI

NocoBase — Thu, 03 Sep 2026 07:49:25 +0000

Originally published at https://www.nocobase.com/en/blog/build-production-ready-ticketing-system-with-ai

TL;DR

AI can build a ticketing system quickly, but “the features have been generated” does not mean “the system is ready for production.”

A system that a team can actually use needs at least clear data relationships, inspectable role permissions, and workflows whose execution results can be traced. This article uses a NocoBase ticketing system as an example to show how AI can turn natural-language requirements into an application and how to verify these core business foundations.

How to Build a Production-Ready Ticketing System with AI

Building a ticketing system with AI may not seem difficult. But can it really be used in production?

On Reddit in the r/nocode community, one user described a problem their team had encountered. They tried several AI + no-code tools. The applications looked good at first, but once real business data was added, problems started appearing one after another, and it was often difficult to tell what had gone wrong.

One reply in the comments pointed to the core issue: many AI-built systems start to fail in more complex business scenarios because they do not maintain a complete internal model of the application, including who is using the system, what permissions different roles have, how work moves through the process, and what users ultimately need to accomplish.

AI can generate pages and features quickly, but for an application to run reliably over the long term, the underlying platform still needs clear data models, relationships, permissions, and workflow capabilities. Otherwise, as business complexity grows, the features generated by AI become increasingly difficult to keep working correctly.

In this article, I will use a ticketing system as an example to show how AI and NocoBase can be used together to build a system with the foundations required for production use.

In this process, NocoBase provides the underlying capabilities for data relationships, permission control, and workflows. AI is responsible for understanding business requirements, converting natural language into data structures, pages, and features, and continuing to adjust the system as requirements evolve.

Step 1: Describe the Business Requirements and Let AI Design the System

Before building anything, start from the actual work. Clarify the problems the team is facing and what the system needs to solve, then describe those requirements to AI in natural language so it can build the required ticketing system on NocoBase.

If you are not sure how to describe the requirements, start from a few angles. For a ticketing system, for example:

How customer issues enter the system: which channels they usually come from and how they are currently collected and handled;
What happens after an issue comes in: who takes ownership, how follow-up works, and when the issue is considered resolved;
Which situations require special attention: for example, urgent issues, tickets that remain unassigned for too long, or tickets that have been open for an extended period.

Once these points are clear, they can be turned directly into a natural-language requirement for AI. Below is the actual requirement we used in this build:

We are a small software company with four customer support agents. Customers mainly report issues through email and the support entry point on our website.

We currently handle these issues through a shared inbox. As the volume grows, issues are sometimes missed. People may assume someone else has already replied, only to find that no one handled the issue. Some tickets go through several rounds of communication, but it becomes unclear who currently owns them. Urgent issues can also remain unresolved for too long.

I want to build a customer support ticketing system. Each customer issue should be recorded separately and assigned to a specific support agent. Agents should be able to continuously update progress until the issue is resolved. For urgent issues, tickets that remain unassigned for too long, or tickets that are close to breaching their deadline, the system should remind the team to take action.

We also want an overview page that quickly shows how many issues are still open, which issues need priority attention, and how many issues have recently been resolved.

Please design and build this system based on these actual business requirements.

AI first breaks the requirements down into a data structure. In NocoBase, it creates tables for tickets, customers, support agents, communication records, SLA rules, and related data, then defines the relationships between them.

On top of the data model, AI continues building the pages.

In the end, AI creates a ticket list, ticket detail pages, and a support workspace, covering the basic scenarios of ticket recording, assignment, follow-up, and overview.

At this point, we have turned a business description into a working ticketing system. But “the features have been built” and “the system is ready for production” are not the same thing.

Once the whole team starts using the system, three questions still need to be verified: Are the data relationships accurate? Can different team members collaborate according to their permissions? Can assignment, reminders, SLA breaches, and escalation rules execute reliably?

Step 2: Solve Three Core Problems for Production Use

The Reddit comment mentioned earlier pointed out that many AI-built applications begin to fail once real data is added because they do not maintain a complete internal model of the application: who uses the system, what roles different members have, how the data is related, and which rules govern the flow of work.

The ticketing system now has data tables and pages, but when four support agents start working with real customer issues, we still need to validate three core areas.

1. Are the Data Relationships Accurate?

A ticket is not an isolated record.

Each ticket needs to be associated with the customer who submitted it, the current owner, historical communication records, and the applicable SLA rule. When the ticket status changes, statistics and pending items on the workspace also need to update accordingly.

If these relationships are not defined clearly, the system may still look complete while failing in actual use. After changing the owner, previous handling records may become difficult to find. A ticket may be matched to the wrong response deadline, or numbers on the overview page may no longer match reality.

In NocoBase, these relationships are not temporary pieces of logic written by AI into a specific page. They are defined directly in the data model. Using the ticket table as an example, the SLA policy, queue, ticket type, and submitter are defined as many-to-one relationships. One ticket can be linked to multiple satisfaction records, attachments, followers, and other tickets. Parent-child ticket relationships are also explicitly defined in field configuration.

These relationships become part of the NocoBase data model and are shared by pages, permissions, workflows, and reporting features. Users can inspect each field type and relationship directly in the data source interface and continue adjusting them as business requirements change.

This is different from a Vibe Coding approach that starts from generated code. In a code-generated application, data relationships usually need to be implemented across the database structure, backend models, APIs, and page queries. If a relationship is incomplete or only one layer is updated later, data inconsistencies can occur. Manual inspection also requires developers to look into both code and database structures to verify the actual implementation.

NocoBase already provides data modeling capabilities. AI only needs to translate business requirements into tables, fields, and relationships instead of building the entire data layer from scratch. After the system is generated, people can inspect and modify the model directly in the same interface.

2. Can Different Roles Collaborate According to the Rules?

When only one person uses a system, permissions are usually not a major issue. Once an entire team starts collaborating, it becomes necessary to define who can see what and who can change what.

In this ticketing system, AI can configure the corresponding roles and data permissions directly in NocoBase.

This is another important difference between building with NocoBase and using a Vibe Coding approach. In an AI-generated application, permission rules often need to be implemented separately across pages, APIs, and data queries. As the number of roles and rules increases, configuration becomes more complex. During manual review, teams often need to return to the code or test the application directly to confirm whether permissions are actually taking effect.

NocoBase already provides permission management capabilities. AI does not need to rebuild a permission system. It only needs to configure which data different roles can view and operate on according to the business requirements. The result is also clearly visible in the administration interface, where users can inspect the permission scope for each role and switch identities to validate the result.

3. Can Business Rules Execute Reliably?

Many rules in a ticketing system need to be monitored continuously and triggered automatically by the system.

In the workflow management interface, users can directly inspect how each rule is triggered, its execution mode, whether it is enabled, and how many times it has run. There is no need to enter the codebase to confirm which rules are active, what conditions trigger them, and whether they have actually executed.

Execution results can also be inspected in detail. Take the “escalate overdue urgent tickets” workflow as an example. The system iterates through tickets that meet the condition, processes their deadlines, and runs the notification node. In the execution record shown in the screenshot, the escalation notification to the current owner has completed successfully, and the node status is shown as complete.

This means business rules are no longer hidden pieces of code. AI can configure them directly using NocoBase's existing workflow capabilities, while people can inspect the workflow structure, runtime status, and individual execution records from the interface.

This is exactly what an internal application needs before being used in real operations: it is not enough to define a business process. Teams also need to know whether it was triggered, how far it progressed, and whether it ultimately completed successfully.

Step 3: Add AI Capabilities to the System

Another advantage of building on NocoBase is that AI does not only help during the application-building stage. Once the core system is ready, AI Employees and workflows can allow AI to participate directly in ticket handling.

In the current ticketing system, we use AI in two specific parts of the process.

The first is ticket creation.

Support agents do not need to fill in every ticket field manually from the start. They can simply describe the customer's issue in natural language. AI Smart Form Fill first turns that description into a ticket title and issue description. Once the basic information is filled in, AI Smart Triage can review the ticket and suggest a category and priority.

Here, AI is responsible for converting the customer's natural-language description into structured information, but it does not bypass the form and submit the ticket automatically. The support agent can still review and edit the generated content before confirming and creating the ticket.

The second part is ticket handling.

On the ticket detail page, a support agent can ask AI to draft the next customer reply based on the current ticket. AI reads the customer's issue, handling progress, and communication history, then refers to the help articles matched by the system. It summarizes the ticket situation and response strategy before generating a reply draft.

More importantly, AI does not operate outside the system's permission model. NocoBase can control which users are allowed to use which AI Employees based on role. When an AI Employee calls the built-in data query tools, the system applies the current user's data permissions and only returns data that the user is allowed to access.

This means that when a regular support agent uses AI, AI does not automatically gain access to data that only a supervisor is allowed to see. What AI can access is still constrained by the original permission boundaries of the business system.

This is also what distinguishes NocoBase's AI capabilities from temporarily calling a large language model outside the application. AI is not just an extra chat entry point. It operates inside the existing data, permission, and workflow system. It can participate in the business process without bypassing the application's existing management rules.

Conclusion

Back to the question at the beginning: can an AI-built ticketing system really be used in production?

It depends on whether the system has a clear, inspectable business structure underneath it.

In this case, we first describe the business problems and requirements to AI. AI then uses NocoBase's existing data model, permission, and workflow capabilities to turn those requirements into a working ticketing system.

That is the value of combining AI with NocoBase: AI understands the requirements and improves building efficiency, while NocoBase provides a manageable and inspectable system foundation. The final business rules and go-live results are still confirmed by people.

If you have an internal process that still depends on spreadsheets, a shared inbox, or manual reminders, start with four questions:

Who will use the system?
What business information does the system need to record?
What can different roles view and operate on?
Which rules need to be executed automatically by the system?

Once these questions are described clearly, AI has a much better starting point for building the business system.

If you want to try this approach, first connect your Coding Agent to NocoBase AI Builder, then describe your business requirements in natural language.

During initialization, you can give AI the following instruction:

Help me install the NocoBase CLI and complete initialization:
https://docs.nocobase.com/ai/ai-quick-start.md
(Please open and read the linked documentation directly.)

After initialization is complete, continue with the specific business requirements and ask AI to build on NocoBase's existing data model, permissions, workflows, and related capabilities. You can then keep modifying the same application as the requirements evolve.

Try the NocoBase + AI Demo: Request an online demo
Build it yourself: View the AI Builder documentation

Related reading:

Weekly Updates: Added DeepSeek V4 Flash with Reasoning Continuation and Web Search

NocoBase — Fri, 28 Aug 2026 15:57:41 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.2.3

Release date: 2026-08-26

🐛 Bug Fixes

[client-v2] Fix a render error when switching a v2 association field to popup record selection. (#10419) by katherinehhh
[Public forms] Fix duplicate Submit actions in V2 regular form configuration when Public Forms is enabled. (#10417) by katherinehhh
[AI LLM: GigaChat] Fixed an application startup error on iOS 15.6 and earlier when the GigaChat AI provider is enabled (#10418) by cgyrock
[WeCom] Fixed WeCom automatic login lifecycle and notification form compatibility in client-v2. by chenzhizdt

v2.2.2

Release date: 2026-08-25

🚀 Improvements

[undefined] Clarified how to use public NocoBase file URLs in Markdown, external pages, and third-party services (#10406) by mytharcher Reference: Storage engine overview

🐛 Bug Fixes

[Access control] Fixed an ACL bypass that allowed firstOrCreate or updateOrCreate to read or modify existing records without the required view or update permission. (#10403) by mytharcher
[Workflow]
- Fix option fields being unable to select configured values in v2 workflow Create record and Update record nodes. (#10414) by katherinehhh
- Fix the extra trigger at startsOn for schedule workflows repeating on a cron expression (#10410) by Tespera
- Fixed workflow task center menus so the active menu can be collapsed by clicking it again while retaining its selected highlight (#10404) by mytharcher
- Fixed collection event as sub-workflows failing when called with a record ID and no preload associations configured (#10407) by mytharcher
[UI templates] Fix the error when closing an approval task containing a referenced block (#10415) by zhangzhonghe

v2.2.1

Release date: 2026-08-24

🐛 Bug Fixes

[UI layout] Fix the issue where desktop routes may be empty after upgrading (#10405) by zhangzhonghe
[Action: Export records Pro] Fix a crash when changing and drag-sorting Pro export fields. by katherinehhh

v2.2.0

Release date: 2026-08-22

🎉 New Features

[client-v2]
- Tabs on pages, subpages and pop-ups support the configuration of linkage rules (#10099) by zhangzhonghe
- Added configurable App and Portal entry support for V2 action panels and the left-top app switcher. (#9893) by katherinehhh
- Add an environment variable to configure legacy and modern route entry modes. (#9891) by Molunerfinn
[undefined]
- Added configurable App and Portal entries for the V2 action panel and app switcher. by katherinehhh
- Add Multi-Portal plugin by zhangzhonghe
[AI employees]
- Added configurable automatic or on-demand knowledge-base retrieval for AI employees, with role-based knowledge-base access filtering. (#10362) by cgyrock
- Added DeepSeek V4 Flash and V4 Pro Responses API support with reasoning continuity, native web search, citations, and model-aware web search controls (#10337) by cgyrock
- AI employees can now be assigned skills from the employee settings page. Skills are built from plugins. (#10237) by cgyrock
- Added UI navigation for supported LLM service CLI commands, including provider preselection when creating a service. (#10210) by cgyrock
- Added an embeddable AI chat box block that supports scoped conversations, AI employee tasks, and shared chat runtime behavior. (#10125) by cgyrock
- Added frontend AI tools for JS blocks (#10121) by 2013xile
- Added RunJS APIs for triggering AI employee tasks from JS blocks. (#10061) by cgyrock
- Added structured AI usage records for usage statistics (#10004) by 2013xile
- Added an external vector store configuration form for AI knowledge bases. (#9723) by cgyrock
[WEB client] Reduced application language responses to requested resource namespaces (#10175) by 2013xile
[Public forms] In the v1 public form, support creating v2 forms and prohibit creating v1 forms (#10045) by zhangzhonghe
[Block: Comment]
- Improved comment block settings with data scope, default sorting, selectable page size, optional last-page jumping, and scalar owner field mapping. (#9954) by jiannx
- Added a comments block. (#9916) by jiannx
[Notification: Email] Migrated the workflow notification node client to v2, restored channel-specific notification forms, and kept legacy workflow route compatibility for migrated notification configuration. (#9817) by jiannx
[Workflow: mailer node] Added v2 client support for configuring the workflow mailer node. (#9825) by jiannx
[UI layout] Add support for mobile layout (#9641) by zhangzhonghe
[Workflow]
- Added workflow database transaction scope support. (#9742) by mytharcher Reference: Database Transaction
- Migrate the Workflow settings page to the v2 client and share a reusable draggable category-tabs component via @NocoBase/client-v2. (#9645) by Molunerfinn
[Multi-space]
- Added default-space configuration so newly created users automatically join the selected default space. by jiannx
- Added debounced display-name search to space switchers and space management in both v1 and v2 by jiannx
[AI: Knowledge base]
- Added UI navigation for creating and editing vector databases from CLI commands, with provider preselection for new databases. by cgyrock
- Added role-based read-only and read/write permissions for knowledge-base management, including creator ownership and read-only management views. by cgyrock
[Workflow: Database transaction node]
- Added the database transaction workflow node plugin. by mytharcher
- Added a client-v2 implementation for the workflow database transaction node while preserving the legacy client entry. by katherinehhh
[Record history] Added client v2 support for the record history plugin. by jiannx
[Workflow: Approval]
- Added usage instructions and card-style workflow selection to the approval initiation list in client v2 by mytharcher
- Added usage instructions and card-style workflow selection to the approval initiation list by mytharcher
- Add approval initiation and todo blocks for v2 pages by zhangzhonghe
[Email manager]
- Email synchronization now uses recoverable background jobs with status history and safer full-resync cleanup, including Gmail Spam and Trash. by jiannx
- Migrated the email manager client to v2. by jiannx
[Auth: LDAP] Add LDAP user synchronization configuration support for client v2. by chenzhizdt

🚀 Improvements

[undefined]
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10103) by mytharcher
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9942) by sembaev-a-a
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9816) by sembaev-a-a
- Improved AI knowledge base retrieval and documentation. (#9765) by cgyrock
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9754) by sembaev-a-a
[cli] nb api resource create now accepts a JSON array for --values to create multiple records in a single request. (#10325) by Molunerfinn
Reference: nb api resource create
[client-v2]
- Refactor Markdown Vditor into a unified plugin-backed Markdown engine with compatibility bridges for existing Markdown block and Vditor field plugins. (#9998) by katherinehhh
- Refactor Markdown Vditor into a unified plugin-backed Markdown engine with compatibility bridges for existing Markdown block and Vditor field plugins. (#9998) by katherinehhh
- Adjusted the v2 System settings menu order and page panel height to match the standard settings layout. (#9849) by katherinehhh
- Fixed missing Settings entries for Client V2 plugin manager cards when a plugin uses a shared or legacy settings path. (#9852) by katherinehhh
[Workflow]
- Grouped task-center items by workflow in the new client and kept workflow filters consistent across task types. (#10374) by mytharcher
- Workflow create and update nodes now support combining text with variables when assigning string and text fields (#10238) by mytharcher
- Workflow tasks can now be filtered and navigated by workflow, with per-workflow pending counts (#10173) by mytharcher
- Improved workflow pending task handling by persisting start, resume, and rerun tasks in the event queue. (#9846) by mytharcher
- Unsupported workflow v2 canvas nodes now keep the normal node card actions while showing the node type as unsupported. (#10054) by mytharcher
- Simplified workflow v2 create/update field assignment, improved selected variable display, and avoided generating unused assign-form model data. (#9887) by katherinehhh
- Exported workflow v2 canvas extension APIs for downstream workflow node plugins. (#9834) by katherinehhh
- Migrate the workflow output node configuration to v2 and align v2 workflow result viewers with the legacy display behavior for string results. (#9813) by Molunerfinn
- Migrate the workflow end node to the v2 implementation. (#9795) by Molunerfinn
[AI employees]
- Simplified AI knowledge base vector configuration (#10178) by cgyrock
- Improved AI employee reliability across validation, data permissions, record context, attachments, workflow tasks, conversation recovery, and coding editor lifecycle handling. (#10162) by cgyrock
- Fixed AI employee model settings persistence, disabled employee conversation creation, and mobile chatbox layout behavior. (#10120) by cgyrock
- Improved AI employee tool settings, data-query guardrails, relation field querying, and malformed tool call diagnostics. (#10042) by cgyrock
- Improved AI employee web search to reduce unnecessary model reasoning and better use provider-specific thinking controls. (#9996) by cgyrock
- Removed the deprecated Datasource entry from AI employee settings and context selection in the v2 UI. (#9988) by cgyrock
- Migrated the AI employee plugin to client-v2. (#9794) by cgyrock
[File manager] Added independent storage settings for returning original file URLs and allowing public access to file URLs (#10160) by mytharcher
[Workflow: Manual node] Show manual workflow tasks in the V2 task center and guide users to the legacy page for processing (#10085) by zhangzhonghe
[Flow engine]
- Support multi portals for ui build apis. (#10072) by gchust
- Open runjs browser globals. (#9841) by gchust
[Collection: SQL] Not user-facing; added client-v2 unit test coverage for migrated plugins. (#9967) by katherinehhh
[Data visualization] Improved chart event scripts so custom event handlers can clean up safely (#10034) by 2013xile
[Data source manager]
- Hide deprecated v2 main data source collection templates from the create collection menu. (#10009) by katherinehhh
- Display unsupported external data source fields in V2 Configure fields, and align backup restore form label styles. (#9983) by katherinehhh
[Block: Comment]
- Improved comment submit actions and fixed related comment/user form submission issues. (#10002) by jiannx
- Added the new comment block plugin to the NocoBase preset and marked the legacy comments plugin as deprecated. (#9936) by jiannx
[Users]
- Improve client-v2 test coverage for the users plugin. (#9975) by jiannx
- Improved the Users & Permissions v2 page layout and department tree behavior. (#9780) by jiannx
[Workflow: JavaScript]
- Aligned v2 workflow request and mailer node configuration fields with legacy layout and attachment variable behavior. (#9952) by jiannx
- Migrated the JavaScript workflow node to client-v2 (#9805) by jiannx
[UI layout] Improved the v2 mobile tab bar so crowded tabs scroll horizontally instead of overlapping. (#9949) by katherinehhh
[Workflow: Aggregate node] Improved v2 workflow field selection for update and aggregate query nodes, including safer associated collection selection in aggregate query nodes. (#9938) by katherinehhh
[Logger] Added the Logger settings page to the client v2 runtime. (#9933) by jiannx
[Form drafts] Migrate plugin form drafts to client v2. (#9910) by gchust
[Workflow: JSON calculation] Migrated the workflow JSON calculation node configuration UI to the v2 workflow canvas while preserving v1 canvas compatibility. (#9902) by mytharcher
[User data synchronization] Added modern UI support for user data synchronization settings (#9837) by 2013xile
[Public forms] Separated v1 and v2 public form lists and fixed the v2 Configure page to open a configurable form detail page. (#9851) by katherinehhh
[Backup manager]
- Improved backup manager table styling and long file name display. (#9864) by katherinehhh
- Tables whose collection dataCategory is marked as 'runtime' are now excluded from backups automatically. (#9804) by cgyrock
[Workflow: Custom action event] Migrated workflow triggers and bind-workflow settings to client-v2, including action trigger, custom action trigger, request interception trigger, and submit/update action workflow binding settings. (#9845) by mytharcher
[Workflow: HTTP request node] Migrated the workflow HTTP request node to client-v2. (#9806) by jiannx
[Locale tester] Added a client v2 settings page for the locale tester. (#9744) by jiannx
[Access control] Aligned the v2 Users & Permissions settings pages with v1 behavior, including pagination totals, department tree behavior, selected styles, and internal permissions-panel scrolling. (#9810) by jiannx
[AI: Knowledge base]
- Aligned the vector database list styling with other settings tables by cgyrock
- Vector database and embedding settings can now be configured directly for each AI knowledge base by cgyrock
- Migrated the AI knowledge base settings pages to the v2 client and fixed layout and loading issues in knowledge base and vector store pages. by cgyrock
[HTTP request encryption] Added v2 client support for HTTP request encryption so query parameters continue to be encrypted in the v2 client. by jiannx
[Workflow: Database transaction node] Improved the v2 workflow database transaction node layout so branch labels and the commit marker have better spacing. by katherinehhh
[Workflow: Subflow] Change pending queue strategy based on workflow engine refactored by mytharcher
[File storage: S3(Pro)]
- S3 Pro uploads now return the created file record with permanent file URLs. by mytharcher
- Added independent S3 Pro settings for original URLs, public file URL access, and unsigned URLs by mytharcher
[Workflow: Approval]
- Updated approval task grouping and timelines in the new client to match the legacy experience. by mytharcher
- Approval application and todo tasks can now be filtered by workflow with per-workflow pending counts by mytharcher
[Email manager]
- Moved the department-based mail viewing option to the V1 general mail settings page, prevented service credential saves from overwriting it, and placed V2 General settings before Service provider settings. by jiannx
- Moved the department-based mail viewing option to the general mail settings page. by jiannx
[App supervisor] Hid the standalone V2 Applications block while keeping its settings page available internally. by katherinehhh
[WeCom] Added modern UI support for WeCom authentication, sync, and notification settings by 2013xile
[DingTalk]
- Complete DingTalk client v2 support, including Stream synchronization, notification configuration, and automatic login improvements. by chenzhizdt
- Added modern UI support for DingTalk authentication, sync, and notification settings by 2013xile

🐛 Bug Fixes

[undefined] Fix nb plugin import failing on plugin tarballs built by yarn build --tar, and correct example code and scaffold structure in the plugin development docs. (#10351) by Molunerfinn
[client-v2]
- Fixed relationship picker labels when association form values contain only a related record ID. (#10386) by cgyrock
- Fixed a false DatePicker missing-component error in v2 table filters. (#10392) by katherinehhh
- Fixed false missing-component console errors when opening v2 table filters. (#10389) by katherinehhh
- Fixed an error that prevented filter conditions from being cleared in workflow settings. (#10388) by Molunerfinn
- Fixed missing frontend response notifications on Client V2 pages, including errors returned by pre-action workflows (#10376) by mytharcher
- Fix Chinese text appearing when searching mobile select fields in English (#10367) by zhangzhonghe
- Fixed pages under /v remaining in UI editing mode after switching to a role without page configuration permission (#10359) by jiannx
- Show a retryable localized fallback in v2 blocks when an external data source is unavailable. (#10336) by katherinehhh
- Redirect users without Settings access to the first available page (#10331) by zhangzhonghe
- Automatically redirect to an accessible Settings tab when the current tab is unavailable (#10332) by zhangzhonghe
- Fix incorrect editing and display of large decimal values in V2 fields. (#10330) by katherinehhh
- Fixed Kanban column quick create records not inheriting the selected group value (#10321) by jiannx
- Fixed automatic SSO redirect providers failing to preserve authentication order in production builds (#10100) by jiannx
- Workflow filters now preserve workflow variable expressions and show a clear parsing error when variable metadata cannot be resolved. (#10088) by Molunerfinn
- Fix an error in v2 workflow value editors when a collection field is named nodeName. (#10067) by katherinehhh
- Fixed workflow v2 variable editors to preserve saved variable pills, disabled states, and operator labels consistently across trigger, filter, and field assignment forms. (#10041) by Molunerfinn
- Fixed an issue where v2 workflow assigned fields could still be edited in read-only executed workflow versions. (#10014) by katherinehhh
- Fix the issue where opening an empty V2 Group menu item shows 404 (#9896) by zhangzhonghe
- Fix workflow execution revision navigation so creating a new version after manual execution opens the correct workflow page in both legacy and modern shells. (#9955) by Molunerfinn
- Fixed V2 admin group routes showing 404 when the group has no available child menu page. (#9932) by katherinehhh
- Fixed link actions becoming invisible on mobile embedded pages when icon-only mode is enabled but no icon is configured. (#9919) by katherinehhh
- Fixed a brief no-pages prompt flash when refreshing in UI Editor mode. (#9918) by katherinehhh
[flow-engine]
- Fix issue where RunJS resource create actions could not create associated sub-table records (#10355) by gchust
- Fix dropdown menus being cut off in short browser windows (#10379) by zhangzhonghe
- Fixed an issue where users could type extra text after selecting a variable in single-value variable inputs. (#10050) by katherinehhh
- Fix the issue where mobile popups with long content cannot scroll (#9871) by zhangzhonghe
[client] Fix incomplete long sidebar menu titles and misaligned configuration toolbars (#10380) by zhangzhonghe
[auth] Fixed occasional Invalid CSRF token errors on API requests in cross-origin deployments (#10245) by mytharcher
[server] Fixed custom portals missing when multi-application plugins are disabled (#10055) by 2013xile
[AI employees]
- Fix V2 Import drag-and-drop being blocked by the AI attachment overlay. (#10384) by katherinehhh
- Fixed AI employee chat streaming long responses causing other idle browser tabs to balloon to multiple gigabytes of memory (#10352) by cgyrock
- Fixed the untranslated Settings tab in the AI plugin's client-v2 settings pages (#10234) by cgyrock
- Fixed frontend Tools asking for confirmation in chat instead of using runtime approval (#10166) by 2013xile
- Fix unnecessary login-required requests on V2 public form pages (#10013) by zhangzhonghe
[Workflow]
- Disable workflow execution mode selection until a trigger type is selected. (#10296) by Molunerfinn
- Fixed workflow execution page titles and added a workflow-list link for missing workflows (#10360) by mytharcher
- Improved regression coverage for permanent file URLs, attachment thumbnails, preview downloads, and local storage security headers (#10148) by mytharcher
- Workflow form controls now correctly inherit the disabled state when viewing executed workflows. (#10079) by Molunerfinn
- Refresh the workflow canvas after updating trigger configuration (#10068) by zhangzhonghe
- Fixed workflow v2 condition operands to stay on one row by default and wrap correctly when selected variable paths are too long. (#10033) by Molunerfinn
- Fix display and detail loading issues in the workflow v2 task center (#10001) by zhangzhonghe
- Fix untranslated workflow result labels and oversized CC configuration dialogs (#9977) by zhangzhonghe
- Fix workflow context mismatches across bundles so branches and some variable pickers work correctly in legacy workflow pages. (#9951) by Molunerfinn
- Fix issues after migrated client to v2 (#9929) by mytharcher
- Fix the issue where in-app message content cannot be configured in v2 workflows (#9885) by zhangzhonghe
- Restored debounced remote search for workflow collection trigger manual execution and aligned the selector with the v1 200-record fetch behavior. (#9870) by Molunerfinn
- Fixed the workflow v2 add-node menu so unavailable node types are disabled according to workflow and branch rules (#9855) by mytharcher
[Notification: In-app message] Fixed the in-app message template form showing workflow canvas variables instead of the variables provided by the page. (#10180) by Molunerfinn
[Block: Map] Fixed region selection not finishing on double-click when map point data is displayed, and fixed AMap remaining in a loading state (#10373) by jiannx
[UI layout]
- Fix mobile pages appearing in the desktop navigation (#10375) by zhangzhonghe
- Hide the mobile UI Editor when the current role cannot configure the interface (#10341) by zhangzhonghe
- Fix desktop pages using mobile styles on narrow screens (#10229) by zhangzhonghe
- Fix the Mobile settings link losing the current sub-application path (#10078) by zhangzhonghe
- Fixed the Mobile settings link opening the main application from a sub-application. (#10075) by katherinehhh
[File manager]
- Fixed local storage files such as logos failing to load in sub-applications after stable URL redirects (#10358) by mytharcher
- Fixed shared attachments such as the system logo not loading for authenticated member users (#10268) by mytharcher
- Fixed 404 errors when uploading files to attachment URL fields in external data sources (#9809) by 2013xile
[Users]
- Fixed required-field validation being skipped when submitting forms in UI editor mode (#10371) by jiannx
- Show backend errors when adding a user or changing a password in V2. (#10364) by katherinehhh
[Block: Tree]
- Fixed tree filter permissions and connected tree-table expansion state, and corrected details pagination totals after filtering. (#10361) by jiannx
- Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10323) by jiannx
[Action: Import records] Fixed an issue where files could not be imported by dragging them into the v2 Import dialog. (#10350) by katherinehhh
[Action: Print]
- Fix the missing print action model registration on V1 pages. (#10347) by katherinehhh
- Fixed v2 detail block printing so empty detail blocks no longer print the whole page. (#9832) by katherinehhh
[Verification] Add a refresh button to the Verification list (#10340) by zhangzhonghe
[Notification manager]
- Fixed locale tester errors when no saved locale record exists, and allowed notification channel identifiers to be customized when creating channels (#10311) by jiannx
- Fix receiver selection saving user IDs as text (#10093) by zhangzhonghe
- Fix incorrect workflow variables shown in CC configuration (#9937) by zhangzhonghe
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10322) by jiannx
[Localization] Fixed a crash when opening Localization settings with the Lina AI assistant entry. (#10293) by cgyrock
[Backup manager]
- Prevent repeated V2 backup restore submissions while a restore request is in progress. (#10262) by katherinehhh
- Improved the stability and accuracy of backup plugin frontend tests. (#10184) by cgyrock
- Fixed inconsistent bold labels on the v2 Backup manager settings page. (#9908) by katherinehhh
[Variables and secrets] Fix validation feedback for v2 environment variable bulk imports and fix Type filtering failures. (#10154) by katherinehhh
[Authentication]
- Fixed declaration generation errors in the v2 authenticator management page (#10095) by jiannx
- Fixed missing saved Authenticator settings when editing authenticators in the v2 authentication manager. (#10091) by jiannx
- Fixed incorrect redirects after SSO login in v2 sub applications (#9927) by 2013xile
[Workflow: JSON variable mapping] Fix an error when selecting loop scope variables in the JSON variable mapping workflow node. (#10094) by Molunerfinn
[Workflow: Delay node] Fix delay node duration input and prevent values below the minimum from being saved. (#10056) by Molunerfinn
[Workflow: Aggregate node] Fix validation rule to allow null filter (#10053) by mytharcher
[Public forms] Fix the issue where public forms can still be configured when UI Editor is off (#10036) by zhangzhonghe
[Embed NocoBase]
- Fixed an issue where tokens could be polluted when embedding NocoBase pages. (#9948) by gchust
- Fixed v2 embed pages losing token-based access after the URL token is removed and the page is refreshed. (#9857) by katherinehhh
[Action: Export records] Fixed a crash when dragging v2 exportable fields after selecting relation fields. (#9995) by katherinehhh
[Block: Comment] Adjusted the default action order for new Comment blocks. (#9976) by jiannx
[Flow engine] Fixed the issue where mobile page can't be created by flow surface api. (#9911) by gchust
[Workflow: mailer node] Fixed workflow v2 test failures caused by missing mocks for trigger workflow action registration. (#9863) by jiannx
[Data source manager] Added a warning and quick setup for v2 data source collections without a primary key or record unique key. (#9872) by katherinehhh
[Workflow: JavaScript] Fixed JavaScript workflow node registration failure in the legacy workflow client. (#9826) by jiannx
[Workflow: Response message] Migrated the workflow response message node to the v2 canvas and fixed unsupported workflow types being able to add it. (#9830) by jiannx
[API documentation] Fixed the API documentation package declaration build failure. (#9752) by katherinehhh
[AI: Knowledge base] Added an overwrite option for AI knowledge base workflow document creation, allowing workflows to replace existing documents with the same key. by cgyrock
[Data source: External PostgreSQL] Automatically load collections when editing an external relational data source in client v2. by katherinehhh
[plugin-service-platform]
- Restored licensed plugin downloads from the service platform. by jiannx
- Disabled the service platform plugin download endpoint. by jiannx
[Verification: TOTP authenticator] Fixed TOTP authenticator bindings so temporary setup secrets are removed and previously verified codes cannot be reused. by jiannx
[Data source: External NocoBase] Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by mytharcher
[Multi-space] Fixed authentication recovery requests being blocked by stale multi-space headers. by jiannx
[Auth: SAML 2.0] Fixed SAML automatic sign-in redirects for unauthenticated users in the modern client while preserving the original destination path by jiannx
[App SSO] Fixed incorrect App SSO redirects in v2 sub applications by 2013xile
[Workflow: Subflow] Fixed workflow title search in the subflow node configuration selector. by mytharcher
[Migration manager]
- Fixed duplicate migration creation on repeated submission and improved v2 migration log and process drawer display. by katherinehhh
- Improve v2 migration error feedback, prevent duplicate migration rule names, and fix environment check modal overflow. by katherinehhh
[Auth: OIDC] Fixed OIDC automatic login redirects in production builds and retained the original modern-client path after login by jiannx
[Workflow: Approval]
- Invalid approval workflows in the new to-do center are now disabled and display a configuration warning. by mytharcher
- Fixed related approval blocks failing to load on Client V2 record detail pages by mytharcher
- Fix workflow form action buttons responding in configuration dialogs by zhangzhonghe
- Fix Approval blocks not refreshing after withdrawal or return by zhangzhonghe
- Guide users to V1 pages when approval interfaces cannot be used in V2 by zhangzhonghe
- Fix blank approval forms and missing or incorrect action buttons by zhangzhonghe
- Allow users to view approval interfaces and cards after a workflow has been executed by zhangzhonghe
- Fixed premature applicant validation and untranslated role labels in the approval workflow manual execution dialog. by Molunerfinn
- Fix the error when configuring approval workflow conditions by zhangzhonghe
- Fix the approval workflow task title remaining editable in executed workflow configurations after production builds. by Molunerfinn
- Close the Apply new drawer when opening an approval form by zhangzhonghe
- Fix empty approval interfaces and fixed assignee IDs by zhangzhonghe
- Fix the error when opening CC node settings by zhangzhonghe
- Fix v2 approval subtables not displaying correctly in details by zhangzhonghe
- Fix approval assignee sorting and hide unsupported legacy configuration entries by zhangzhonghe
- Fix missing approval data on approval task cards by zhangzhonghe
- Fix missing processed approval details in v2 task detail popups by zhangzhonghe
- Fix approval task form and action issues in the workflow v2 task center by zhangzhonghe
- Fix issues involved by migrating to client v2 by mytharcher
- Fix display and action issues in approval initiator interfaces by zhangzhonghe
- Fix the issue where approval tables appear in the block data source list by zhangzhonghe
- Fix an error that could prevent V2 pages from opening when approval and notification plugins are enabled by zhangzhonghe
[Collection field: Signature] Fix client-v2 signature field file collection selector localization and option filtering. by katherinehhh
[Audit logs] Fixed raw translation expressions appearing in the client V2 audit log Role column. by katherinehhh
[App supervisor] Fixed app visit links losing the v2 path in sub applications by 2013xile
[WeCom]
- Fixed WeCom notification channels not saving the selected authenticator. by jiannx
- Fixed a blank flash when switching route menu items with the WeCom plugin enabled in Client V2 by 2013xile
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form by jiannx

v2.1.44

Release date: 2026-08-21

🎉 New Features

[Multi-space] Added search to space switchers and space management in both v1 and v2 by jiannx

🐛 Bug Fixes

[DingTalk] Fixed DingTalk internal auto-login retaining the previous user's session after switching accounts. by chenzhizdt

v2.1.43

Release date: 2026-08-19

🐛 Bug Fixes

[app] Added runtime polyfills for modern JavaScript APIs in supported older browsers (#10385) by mytharcher
[undefined] Fixed customized external database field display names being reset when selected tables are reloaded by cgyrock
[Data source manager] Fixed customized external database field display names being reset when a data source is submitted or its selected tables are changed (#10387) by cgyrock
[Workflow: Approval] Fixed approval workflows configured to return to any previous approval node only allowing the nearest upstream node by mytharcher

v2.1.42

Release date: 2026-08-18

🚀 Improvements

[undefined]
- Added LDAP and DingTalk user data synchronization guides, including permissions, event modes, synchronized fields, department owners, and troubleshooting. (#10377) by chenzhizdt Reference: DingTalk synchronization, LDAP synchronization
- Improve LDAP and DingTalk user synchronization documentation and add all supported translations. (#10382) by chenzhizdt Reference: DingTalk / LDAP

🐛 Bug Fixes

[Workflow: JavaScript] Fixed JavaScript workflow task recovery repeatedly enqueueing jobs whose executions have ended or expired. (#10366) by mytharcher
[Action: Export records Pro] Fix export errors when using complex filters with the Export Pro plugin by zhangzhonghe
[Action: Import records Pro] Fixed asynchronous imports not respecting field-level import permissions by mytharcher
[App supervisor] Fixed Kingbase connections when creating supervised applications by 2013xile

v2.3.0-beta.4

Release date: 2026-08-25

🚀 Improvements

[undefined] Clarified how to use public NocoBase file URLs in Markdown, external pages, and third-party services (#10406) by mytharcher Reference: Storage engine overview

🐛 Bug Fixes

[UI layout] Fix the issue where desktop routes may be empty after upgrading (#10405) by zhangzhonghe
[Workflow] Fixed workflow task center menus so the active menu can be collapsed by clicking it again while retaining its selected highlight (#10404) by mytharcher
[Action: Export records Pro] Fix a crash when changing and drag-sorting Pro export fields. by katherinehhh

v2.2.0-beta.18

Release date: 2026-08-20

🎉 New Features

[AI employees] Added DeepSeek V4 Flash and V4 Pro Responses API support with reasoning continuity, native web search, citations, and model-aware web search controls (#10337) by cgyrock
[Multi-space]
- Added search to space switchers and space management in both v1 and v2 by jiannx
- Added debounced display-name search to space switchers and space management in both v1 and v2 by jiannx
[Email manager] Email synchronization now uses recoverable background jobs with status history and safer full-resync cleanup, including Gmail Spam and Trash. by jiannx
[Auth: LDAP] Add LDAP user synchronization configuration support for client v2. by chenzhizdt

🚀 Improvements

[undefined]
- Improve LDAP and DingTalk user synchronization documentation and add all supported translations. (#10382) by chenzhizdt Reference: DingTalk / LDAP
- Added LDAP and DingTalk user data synchronization guides, including permissions, event modes, synchronized fields, department owners, and troubleshooting. (#10377) by chenzhizdt Reference: DingTalk synchronization, LDAP synchronization
[lock-manager] Added renewable local lock leases and ensured try-acquired locks are released safely across reuse and errors (#10368) by jiannx
[cli] nb api resource create now accepts a JSON array for --values to create multiple records in a single request. (#10325) by Molunerfinn
Reference: nb api resource create
[Workflow] Grouped task-center items by workflow in the new client and kept workflow filters consistent across task types. (#10374) by mytharcher
[Block: Tree] Tree filter blocks now support configurable default sorting. (#10339) by jiannx
[Redis lock adapter] Added renewable Redis lock leases and made reusable lock handles release safely during contention and errors by jiannx
[Workflow: Approval] Updated approval task grouping and timelines in the new client to match the legacy experience. by mytharcher
[DingTalk] Complete DingTalk client v2 support, including Stream synchronization, notification configuration, and automatic login improvements. by chenzhizdt

🐛 Bug Fixes

[client-v2]
- Fixed relationship picker labels when association form values contain only a related record ID. (#10386) by cgyrock
- Fixed a false DatePicker missing-component error in v2 table filters. (#10392) by katherinehhh
- Fixed false missing-component console errors when opening v2 table filters. (#10389) by katherinehhh
- Fixed an error that prevented filter conditions from being cleared in workflow settings. (#10388) by Molunerfinn
- Fixed missing frontend response notifications on Client V2 pages, including errors returned by pre-action workflows (#10376) by mytharcher
- Fix Chinese text appearing when searching mobile select fields in English (#10367) by zhangzhonghe
- Fix filter forms refreshing automatically in UI edit mode (#10356) by zhangzhonghe
- Use Cascader by default for tree-structured relation fields in v2 filter forms (#10357) by zhangzhonghe
- Fix JS items incorrectly appearing in form field linkage rule actions (#10363) by gchust
- Fixed pages under /v remaining in UI editing mode after switching to a role without page configuration permission (#10359) by jiannx
- Automatically redirect to an accessible Settings tab when the current tab is unavailable (#10332) by zhangzhonghe
- Fix mobile single-select relation fields not clearing when the selected record is tapped again (#10346) by zhangzhonghe
- Fix the issue where China region fields cannot be added directly to filter forms (#10333) by zhangzhonghe
- Fixed an issue where ctx.form.submit could not correctly submit form data. (#10063) by gchust
- Redirect users without Settings access to the first available page (#10331) by zhangzhonghe
- Fix incorrect editing and display of large decimal values in V2 fields. (#10330) by katherinehhh
- Show a retryable localized fallback in v2 blocks when an external data source is unavailable. (#10336) by katherinehhh
[app] Added runtime polyfills for modern JavaScript APIs in supported older browsers (#10385) by mytharcher
[flow-engine] Fix dropdown menus being cut off in short browser windows (#10379) by zhangzhonghe
[client] Fix incomplete long sidebar menu titles and misaligned configuration toolbars (#10380) by zhangzhonghe
[undefined]
- Fix nb plugin import failing on plugin tarballs built by yarn build --tar, and correct example code and scaffold structure in the plugin development docs. (#10351) by Molunerfinn
- Fixed customized external database field display names being reset when selected tables are reloaded by cgyrock
[database] Fixed prefix indexes on camel-case fields when underscored database naming is enabled (#10329) by 2013xile
[Data source manager] Fixed customized external database field display names being reset when a data source is submitted or its selected tables are changed (#10387) by cgyrock
[Workflow: JavaScript] Fixed JavaScript workflow task recovery repeatedly enqueueing jobs whose executions have ended or expired. (#10366) by mytharcher
[Workflow]
- Fixed workflow execution page titles and added a workflow-list link for missing workflows (#10360) by mytharcher
- Disable workflow execution mode selection until a trigger type is selected. (#10296) by Molunerfinn
[Notification: In-app message] Fixed the in-app message template form showing workflow canvas variables instead of the variables provided by the page. (#10180) by Molunerfinn
[Block: Map] Fixed region selection not finishing on double-click when map point data is displayed, and fixed AMap remaining in a loading state (#10373) by jiannx
[Collection field: Markdown(Vditor)] Fix Markdown HTML previews in v2 details blocks under dark themes. (#10370) by katherinehhh
[UI layout]
- Fix mobile pages appearing in the desktop navigation (#10375) by zhangzhonghe
- Hide the mobile UI Editor when the current role cannot configure the interface (#10341) by zhangzhonghe
[AI employees]
- Fix V2 Import drag-and-drop being blocked by the AI attachment overlay. (#10384) by katherinehhh
- Fixed AI employee chat streaming long responses causing other idle browser tabs to balloon to multiple gigabytes of memory (#10352) by cgyrock
[Workflow: JSON calculation] Fixed JSON Query jobs losing structured parser errors and displaying [object Object] (#10344) by mytharcher
[Users]
- Show backend errors when adding a user or changing a password in V2. (#10364) by katherinehhh
- Fixed required-field validation being skipped when submitting forms in UI editor mode (#10371) by jiannx
[File manager]
- Fix the extra submit step when selecting an existing file in a single-value field (#10372) by zhangzhonghe
- Fixed local storage files such as logos failing to load in sub-applications after stable URL redirects (#10358) by mytharcher
- Fixed video previews not updating when switching between files (#10345) by mytharcher
[Action: Import records] Fixed an issue where files could not be imported by dragging them into the v2 Import dialog. (#10350) by katherinehhh
[Action: Print] Fix the missing print action model registration on V1 pages. (#10347) by katherinehhh
[Block: Tree] Fixed tree filter permissions and connected tree-table expansion state, and corrected details pagination totals after filtering. (#10361) by jiannx
[Verification] Add a refresh button to the Verification list (#10340) by zhangzhonghe
[Block: Kanban] Fixed configured content disappearing after reopening a kanban card's detail drawer (#10334) by jiannx
[Action: Export records]
- Fix table export errors after filtering by multiple relation fields (#10342) by zhangzhonghe
- Fixed a page crash when sorting an edited relation field in Export V2. (#10335) by katherinehhh
[Notification manager] Fixed locale tester errors when no saved locale record exists, and allowed notification channel identifiers to be customized when creating channels (#10311) by jiannx
[Action: Duplicate record] Improve direct duplication failure feedback in v2 without duplicate API error messages. (#10327) by katherinehhh
[Data source: External PostgreSQL] Automatically load collections when editing an external relational data source in client v2. by katherinehhh
[Collection field: Encryption] Fixed bulk import failing with model.changed is not a function when the collection contains an encryption field by cgyrock
[Action: Export records Pro] Fix export errors when using complex filters with the Export Pro plugin by zhangzhonghe
[Action: Import records Pro]
- Fixed asynchronous imports not respecting field-level import permissions by mytharcher
- Fixed asynchronously imported records not being associated with the current space by jiannx
- Clarified import results by showing the number of newly created records separately from updated records by mytharcher
[Workflow: Webhook] Fixed a 400 error when manually executing a webhook workflow without request headers by mytharcher
[Record history] Improved record history write performance for collections with large snapshot tables by 2013xile
[Workflow: Approval]
- Fixed approval workflows configured to return to any previous approval node only allowing the nearest upstream node by mytharcher
- Add data scope filtering to Client V2 related approval blocks by zhangzhonghe
- Fix Approval blocks not refreshing after withdrawal or return by zhangzhonghe
- Invalid approval workflows in the new to-do center are now disabled and display a configuration warning. by mytharcher
- Fix inconsistent subtable column widths in approval details by zhangzhonghe
- Fixed related approval blocks failing to load on Client V2 record detail pages by mytharcher
[Audit logs] Fixed raw translation expressions appearing in the client V2 audit log Role column. by katherinehhh
[App supervisor] Fixed Kingbase connections when creating supervised applications by 2013xile