DEV Community: NocoBase

Awesome NocoBase: Discover and Share Plugins Built by the Community

NocoBase — Tue, 28 Jul 2026 03:05:50 +0000

Originally published at https://www.nocobase.com/en/blog/awesome-nocobase-community-plugins

From day one, NocoBase has been built on a plugin architecture.

This architecture gives NocoBase the flexibility and extensibility needed for long-term growth. Developers can continuously add new capabilities for different business needs without modifying the core system.

With the rise of AI coding tools, plugin development is becoming easier than ever. With tools like Claude Code, Codex, and Cursor, together with NocoBase’s AI plugin development capabilities, more developers can quickly build their own plugins.

Now, you can discover community-built plugins in Awesome NocoBase, or share your own extensions and help grow the NocoBase plugin ecosystem.

Featured Community Plugins

Currently, Awesome NocoBase features a collection of plugins created by community developers. These plugins are built from real-world projects and experiences. Some address common needs, some extend NocoBase’s core capabilities, and others provide solutions for specific business scenarios.

NocoBase Hooks

Author: Bunnarin

NocoBase Hooks provides an extension mechanism similar to PocketBase’s pb_hooks. Developers can write server-side extensions directly in the storage/hooks/ directory while leveraging NocoBase capabilities such as database events, middleware, custom APIs, ACL, and logging.

It also supports automatic loading, hot reload during development, TypeScript, and independent dependency management.

Global Search

Author: trumanharry

Global Search adds a cross-table search entry to the NocoBase admin interface, making it easier to find information across different data collections such as customers, orders, projects, and contacts.

Office File Previewer

Author: OneTwoSmall

Office File Previewer enhances NocoBase’s file preview capabilities with flexible support for Office documents and other file formats.

For use cases such as knowledge bases, contract management, archives, and internal file systems, users can preview files directly inside NocoBase without downloading files or switching between applications.

Enhanced Table Block

Author: OneTwoSmall

Enhanced Table Block extends NocoBase table blocks with richer data display and interaction features.

It is ideal for scenarios involving reports, inventory, orders, and financial data, allowing users to manage information in a more spreadsheet-like way.

Auth: Email

Author: OneTwoSmall

Supports authentication through email verification codes.

Custom Login Page

Author: JAVA-LW

Custom Login Page allows administrators to configure NocoBase login page themes, styles, and branding directly from the backend.

It is suitable for projects that require a consistent brand experience or dedicated login portals for customers, employees, and partners.

Block: Tabs

Author: zoudeming-vk

Block: Tabs provides a tab block that organizes multiple NocoBase blocks within a single interface.

For information-heavy detail pages and management screens, it reduces scrolling and groups related content into tabs, creating a clearer page structure.

Watermark

Author: fengwenkai168

Watermark adds semi-transparent watermarks to NocoBase pages and can display information about the current user.

Administrators can customize watermark text, opacity, and font size. It is suitable for contracts, customer data, and other sensitive information where reducing screenshot-based data leakage is important.

Role Switcher

Author: michaelxmn

Role Switcher adds a quick role switching option to the top navigation bar.

It helps users with multiple roles switch contexts more efficiently, and makes permission testing easier for administrators and developers.

Per-User Column Settings

Author: Albert-mah

Per-User Column Settings allows each user to save their own table column preferences.

Users can customize visible fields, reorder columns, freeze columns, and adjust column widths without affecting other users. It is especially useful for business systems where different roles focus on different information.

Field Sequence Pro

Author: ericto888

Field Sequence Pro extends the built-in auto-numbering field with support for form variables, value mapping dictionaries, and multi-dimensional isolated counters while keeping the original functionality.

It is suitable for generating unique identifiers such as order numbers, contract numbers, and business serial numbers based on different rules.

HTTP Error Handler

Author: Albert-mahmahuantest

HTTP Error Handler provides global 4xx/5xx error handling for NocoBase.

Administrators can define error handling rules using JS expressions, display unhandled API errors with custom error pages, or redirect users to specific pages automatically.

Workflow: URL Trigger

Author: Albert-mah

Workflow: URL Trigger enables workflows to be triggered by external HTTP requests.

It supports wildcard and regular expression matching, uses request parameters as workflow variables, and can work with the HTTP Response node to build Webhooks, API integrations, and automation workflows.

Workflow: Crypto

Author: Albert-mah

Workflow: Crypto provides AES encryption and decryption nodes for workflows.

It supports variable inputs and automatic JSON parsing after decryption, making it suitable for secure data exchange with external systems.

Workflow: Auth Token

Author: Albert-mah

Workflow: Auth Token generates real NocoBase login JWTs within workflows.

It can be used to create SSO login links and programmatic access tokens, and combined with URL Trigger and Crypto to build complete single sign-on workflows.

Build the NocoBase Plugin Ecosystem Together

If you have created a NocoBase plugin, we welcome you to submit it to Awesome NocoBase.

Our goal is to help more users discover valuable plugins while giving great plugins and their developers more exposure.

In the future, we will continue highlighting outstanding community plugins and the developers behind them.

Weekly Updates：Remote Search for Approval Notification Channels

NocoBase — Mon, 27 Jul 2026 10:23:21 +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.1.30

Release date: 2026-07-24

🚀 Improvements

[client-v2] Improved v2 QR code and barcode scan recognition, camera lifecycle safety, and responsive preview behavior. (#10145) by @katherinehhh
[client] Added Myanmar (my-MM) to the legacy System Settings language selector. (#10153) by @hongboji
[Workflow: Approval]
- Added usage instructions and card-style workflow selection to the approval initiation list by @mytharcher
- Improved the approval timeline with clearer status badges, timing details, user avatars, responsive layout, and connected submission rounds by @mytharcher

🐛 Bug Fixes

[client-v2]
- Fix RunJS values not taking effect in client v2 date range limits. (#10157) by @katherinehhh
- Improve error messages for unsupported and missing pages in the /v/ branch (#10159) by @zhangzhonghe
- Fix v2 table action titles being reverted after linkage refresh. (#10140) by @katherinehhh
- Fixed required association values being cleared after selection in popup sub-table forms with parent-item data scopes. (#10146) by @katherinehhh
- Fix record picker lists not refreshing after creating a record in client v2. (#10142) by @katherinehhh
[flow-engine]
- Fix v2 block configuration dropdowns closing when clicking their active trigger. (#10143) by @katherinehhh
- Fixed untranslated default text in secondary confirmation settings when using Simplified Chinese (#10149) by @mytharcher
[Authentication]
- Fixed an intermittent database connection error during application shutdown when Redis cache is enabled (#10151) by @mytharcher
- Fixed incorrect SSO redirects for sub-applications using custom domains (#10170) by @2013xile
[AI employees] Prevented Nathan from reporting malformed or unchanged code patches as successfully applied (#10174) by @2013xile
[Collection field: Sequence] Fixed v2 sequence rule options not saving entered values and fixed-text rules incorrectly reporting a required-field error. (#10156) by @katherinehhh
[Backup manager] Fix missing visible error notifications when Backup Manager restore requests fail in the v2 client. (#10158) by @katherinehhh
[Block: Kanban] Fixed Calendar and Kanban popup templates not taking effect or being cleared incorrectly when using copied popup templates (#9856) by @jiannx
[App SSO] Fixed App SSO failures when the public issuer is unreachable from sub-application servers by @2013xile
[Auth: OIDC] Fixed incorrect redirects after OIDC login through a sub-application custom domain by @2013xile
[Workflow: Approval] Hide approval configuration controls when UI Editor is off by @zhangzhonghe

v2.1.29

Release date: 2026-07-21

🚀 Improvements

[Workflow: Approval] Approval notification channels can now be searched remotely by title by @mytharcher

🐛 Bug Fixes

[flow-engine] Fixed an issue where the Add Block menu could unexpectedly disappear while searching. (#10097) by @gchust
[client-v2]
- Fixed full and specified height settings not working for JS Blocks displayed with a card (#10126) by @gchust
- Fix the issue where date filter defaults become a single date (#9854) by @zhangzhonghe
[Calendar] Add scrolling to the v2 calendar event overlay when many events are shown. (#10138) by @katherinehhh
[Multi-space] Fixed account switching failures caused by stale space headers during authentication recovery by @jiannx

How to Choose a Smartsheet Alternative: 7 Tools Compared

NocoBase — Fri, 24 Jul 2026 17:49:46 +0000

Originally published at https://www.nocobase.com/en/blog/best-smartsheet-alternatives

Smartsheet is one of the first tools many teams consider when setting up project management and collaboration workflows.

It retains a familiar spreadsheet-style interface while adding boards, Gantt charts, forms, automation, reports, and dashboards. For teams that previously relied on Excel to manage projects, the learning curve is relatively low, making it easier to establish consistent processes for task assignment, progress tracking, and project reporting.

However, a tool that works well at the beginning may not remain suitable for every stage of a team’s development.

Recently, we came across a discussion about alternatives in the Smartsheet community on Reddit. The original poster works for a construction company with about 100 employees and belongs to a seven-person department. Previously, everyone managed projects according to their own habits: some used spreadsheets, some relied on personal task tools, and others tracked progress through email and meetings. As the number of projects increased, the team wanted to establish a unified project management and reporting process.

The comments showed that opinions about Smartsheet were mixed.

Users who supported Smartsheet mentioned:

Migrating from Excel is relatively straightforward
Real-time data can be connected across different sheets
Dashboards and reporting are intuitive
Forms, file review, approvals, and automation are well covered
Business teams do not have to wait for IT to develop every system

Users considering replacing Smartsheet mentioned:

Changes to pricing and licensing models
Uneven adoption across departments
Automation is often maintained by only a few advanced users
Complex relational data remains difficult to manage
Maintenance costs increase as data volume and usage expand

Based on these needs, we selected several representative Smartsheet alternatives, including open-source platforms. The following sections introduce each product’s positioning, core capabilities, major differences from Smartsheet, pricing, and suitable team types.

Before examining each product in detail, use the comparison table below to quickly identify options that may better match your team’s needs.

Product	Open Source	Primary Positioning	Similarities to Smartsheet	Key Differences
NocoBase	Yes	Enterprise business system development	Tables, pages, workflows	Focuses on data relationships, permissions, and controlled operations; highly flexible plugin architecture; self-hosted and extensible
Baserow	Yes	No-code database	Spreadsheet-style data management	Open source, self-hosted, relational data
monday	No	Visual work management	Projects, boards, automation	Greater emphasis on boards and team collaboration
SmartSuite	No	Comprehensive work management	Projects, records, processes	Combines data management with project execution
Airtable	No	Relational data collaboration	Tables, views, automation	Stronger at linked data and interface building
ClickUp	No	All-in-one project management	Tasks, dashboards, automation	Task-centric with broad feature coverage
Asana	No	Project and task management	Tasks, dependencies, timelines	Clearer and more standardized project workflows

💬 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

1. NocoBase: For Teams Moving From Collaborative Spreadsheets to Business Systems

Product Information

Website: https://www.nocobase.com/
Documentation: https://docs.nocobase.com/
Pricing: https://www.nocobase.com/en/commercial
GitHub: https://github.com/nocobase/nocobase
GitHub Stars: 23.4K

What Is NocoBase?

NocoBase is an open-source AI-powered no-code platform for building enterprise business systems such as project management, CRM, contract management, order management, approvals, and ticketing.

Teams can first create related data tables for customers, projects, contracts, tasks, invoices, and other business objects. They can then configure tables, boards, forms, detail pages, charts, and action buttons through a visual interface. As business requirements change, pages, permissions, workflows, and plugins can continue to be adjusted.

Why Can It Replace Smartsheet?

NocoBase provides tables, boards, forms, detail pages, charts, and workflows, covering common Smartsheet scenarios such as project management, data collection, progress tracking, and automation.

For teams with increasingly complex data structures, NocoBase can also create multiple related tables. For example, one customer can have multiple projects, while each project can be linked to contracts, tasks, invoices, and payment records. Sales, finance, project managers, and executives can work from the same underlying data while using different pages and receiving role-based data and operation permissions.

NocoBase also offers two types of AI collaboration capabilities that support both system development and ongoing operations.

The first is AI-assisted development. Teams can connect commonly used AI agents such as Claude Code, Codex, and Cursor to NocoBase, describe business requirements in natural language, and have the AI agent assist with data modeling, page configuration, workflow orchestration, permission settings, and plugin development. The generated system can still be reviewed and adjusted through NocoBase’s no-code interface.

The second is AI Employees. After the business system goes live, AI Employees can understand business context from the current page, data blocks, and selected records. They can invoke relevant skills to query data, organize information, fill in forms, analyze trends, generate reports, and process content. AI Employees can also be orchestrated into workflows, bringing AI capabilities into specific business processes.

NocoBase also supports self-hosting, plugin extensions, and external database connections, making it suitable for teams that want control over their data and deployment environment while continuously expanding business modules.

Key Differences From Smartsheet

Smartsheet mainly uses worksheets as the collaboration entry point, with members typically viewing and updating project data directly in a grid. NocoBase starts with a data model and then configures pages, permissions, operations, and workflows around that data.

In NocoBase, users do not all have to enter the same underlying data table. Administrators can configure separate work interfaces for different roles:

Sales teams can view customers, contacts, and opportunities;
Project managers can view projects, tasks, and delivery progress;
Finance teams can view contracts, invoices, and payments;
Executives can view aggregated metrics and dashboards.

Data modification methods can also be configured according to business risk. Routine fields such as task status and assignee can support quick editing. Critical data such as contract amounts, payment status, and approval results can be entered, validated, confirmed, and submitted through dedicated forms. Once submitted, the system can trigger notifications, approvals, data updates, or other workflows.

AI further expands this system-oriented approach. During development, AI agents can understand NocoBase’s data models, pages, permissions, and workflow configurations to help teams build systems faster. During operation, AI Employees can read business context, analyze data, and perform authorized actions.

This means AI can participate throughout the complete lifecycle of a business system:

Assist with creating data models and pages from natural-language requirements;
Configure role permissions, operation methods, and business processes;
Analyze and process business data after the system goes live;
Continue participating in daily operations through AI Employees or workflows.

For teams already using Smartsheet to manage customers, contracts, projects, and financial data, this design can reduce errors and management pressure caused by multiple people directly maintaining complex worksheets.

Which Teams Is It Best For?

NocoBase is better suited to teams that:

Already use Smartsheet to manage formal business data such as customers, contracts, orders, or payments;
Have complex data relationships across multiple worksheets;
Need different operating interfaces for sales, finance, operations, and management;
Need to control which data different roles can view and modify;
Require validation, confirmation, approval, or auditing for critical data changes;
Want to use AI agents to accelerate business system development;
Want AI Employees to participate in data analysis and business processing after launch;
Need self-hosting and control over data and deployment environments;
Plan to continue adding business modules on the same platform.

🎉 NocoBase lightweight solutions are now available. Try them today!

These focused business solutions are built with NocoBase. They are open source, controllable, and easy to extend or modify around your own processes.

Each solution includes a standard prompt. Give it to an AI agent connected to your instance, and you can reproduce the same system in minutes.

https://www.nocobase.com/en/ai-blueprints

2. Baserow: For Teams That Want to Keep a Spreadsheet-Style Experience

Product Information

Website: https://baserow.io/
Documentation: https://baserow.io/user-docs
Pricing: https://baserow.io/pricing
GitHub: https://github.com/baserow/baserow
GitHub Stars: 5.3K

What Is Baserow?

Baserow is an open-source no-code database and application-building platform. It retains a spreadsheet-like interface, allowing users to manage customers, projects, content, inventory, and other information through tables, fields, linked records, and multiple views. Teams can also build internal applications, dashboards, and automated processes. Baserow additionally provides AI fields, AI formula generation, and the Kuma AI assistant.

Why Can It Replace Smartsheet?

Baserow supports tables, forms, boards, calendars, timelines, and dashboards, covering common Smartsheet needs such as data collection, project tracking, and information presentation. It also supports table relationships, lookups, rollups, and formulas, making it more suitable for related data. For teams accustomed to editing information directly in tables but seeking stronger database capabilities, the post-migration experience is relatively easy to understand.

Key Differences From Smartsheet

Smartsheet places greater emphasis on project management, task dependencies, resource planning, and cross-project reporting, while Baserow is closer to a no-code database. Teams can freely create tables and relationships, then use the application builder to turn underlying data into internal tools or customer portals. Baserow also offers an open-source, self-hosted version, allowing teams to control their deployment environment, data storage, and system extensions.

Which Teams Is It Best For?

Baserow is suitable for teams that are comfortable with spreadsheets, need to manage multiple related data tables, and prefer an open-source or self-hosted solution. It is particularly useful for content management, lightweight CRM, project data, inventory, and internal information management, as well as teams that want to build simple internal tools on top of data tables.

3. monday: For Project Teams That Prioritize Visual Collaboration

Product Information

Website: https://monday.com/
Documentation: https://support.monday.com/hc/en-us
Pricing: https://monday.com/pricing

How Does monday Organize Team Work?

monday is a visual work management platform. Teams can centralize projects, tasks, owners, deadlines, and current status in a Board, then switch among Kanban, timeline, Gantt, calendar, and dashboard views to review progress from different perspectives. It is used for project management, marketing campaigns, product development, operational planning, and cross-functional collaboration, and the platform is also adding AI workflows and AI agents.

Why Is It a Suitable Smartsheet Alternative?

For teams seeking a consistent way to collaborate on projects, monday provides a relatively intuitive starting point. Administrators can use templates to quickly create project spaces, while members work around tasks, status, owners, and milestones. Automation rules can send notifications, update fields, or move tasks when a status changes, a date arrives, or a task is assigned. Dashboards can aggregate project progress, budgets, and team workloads across multiple Boards.

monday’s AI workflows can also add content generation, information analysis, and task assignment to existing processes. Its AI agents can monitor activities, determine the next action, and execute tasks within the context of Boards and workflows, although this capability is still being rolled out gradually.

Key Differences From Smartsheet

Smartsheet retains stronger spreadsheet conventions and is well suited to managing data, formulas, and cross-sheet reports in dense grids. monday focuses more on Boards, statuses, and task progression. Colors, groups, views, and automation make it easier for members to understand who owns each task and how far the work has progressed.

This design is collaboration-friendly, particularly for scenarios that require frequent status updates, owner coordination, and milestone tracking. For complex formulas, extensive cross-sheet references, or relational business data, monday differs significantly from traditional spreadsheets and should be evaluated against each existing Smartsheet use case.

Which Teams Are Better Suited to monday?

monday is better suited to marketing, operations, product, PMO, and cross-functional teams centered on projects, tasks, and team collaboration. When members need to quickly understand owners, deadlines, current status, and project risks while also using boards, Gantt charts, automation, and management dashboards, monday can be more intuitive than maintaining complex worksheets directly.

4. SmartSuite: For Teams Managing Projects, Data, and Business Processes Together

Product Information

Website: https://www.smartsuite.com/
Documentation: https://help.smartsuite.com/en/
Pricing: https://www.smartsuite.com/pricing

What Is SmartSuite?

SmartSuite is a work management platform for business teams. It uses Solutions, Tables, and Records as its basic structure. Within one workspace, teams can manage projects, tasks, customers, contracts, risks, assets, and other business records, then view progress through tables, boards, calendars, timelines, Gantt charts, and dashboards.

SmartSuite is also gradually adding AI capabilities. Users can describe the business they need to manage in natural language, and AI Solution Generator can automatically create a solution containing tables, fields, and relationships. AI Field Agents can use field content from records to generate summaries, classifications, recommendations, or structured results and write those results directly back to the records.

Why Is It a Suitable Smartsheet Alternative?

For teams already using Smartsheet to manage projects, customers, suppliers, or operational processes, SmartSuite provides a similar table view while adding more complete record pages, linked data, and templates for multiple scenarios.

For example, a team can create separate customer, project, and task tables and connect them through linked records. Project managers can manage task dependencies and schedules in Gantt charts, business users can open individual records to view files, comments, checklists, and activity history, and management can monitor overall progress through dashboards.

Key Differences From Smartsheet

Smartsheet retains a strong worksheet-based approach, with many operations centered on rows, columns, formulas, and cross-sheet reports. SmartSuite places greater emphasis on records and the relationships among them. A project record can link to customers, tasks, budgets, risks, and deliverables while providing its own detail page and collaboration information.

This design positions SmartSuite between a traditional project management tool and a business data platform. Teams can use boards, Gantt charts, and timelines to move projects forward while connecting projects with customers, contracts, assets, and other business information. Linked records can also be used across different Solutions, reducing duplicate maintenance of the same data in multiple workspaces.

Which Teams Is It Best For?

SmartSuite is better suited to teams that manage both projects and structured business records, including professional services, marketing operations, product management, construction projects, procurement, supplier management, and lightweight CRM teams. When teams need boards, Gantt charts, and task dependencies while also connecting customers, projects, files, budgets, and risks, SmartSuite is more complete than a task-only management tool.

It is also suitable for teams that want to adopt ready-made templates and cloud services quickly and do not require self-hosting. AI Solution Generator can shorten initial configuration time, while AI Field Agents can automatically organize content, classify information, and suggest next steps after records are updated.

5. Airtable: For Teams Managing Linked Data and Flexible Business Processes

Product Information

Website: https://www.airtable.com/
Documentation: https://support.airtable.com/docs
Pricing: https://airtable.com/pricing

What Is Airtable?

Airtable is a no-code application platform built on a relational database. Teams can enter and organize data much like they would in a spreadsheet while using linked records, lookups, rollups, and formulas to connect customers, projects, tasks, content, products, and other information. Interface Designer can create operating interfaces for different teams from the same data, while automation connects notifications, record updates, and external tools.

Airtable is also strengthening its AI capabilities. Omni can create and adjust tables, interfaces, and automations from natural-language instructions. Field Agents can use record content to conduct research, classify information, generate content, and analyze feedback.

Why Is It a Suitable Smartsheet Alternative?

Airtable provides tables, boards, calendars, timelines, forms, interfaces, and automation, covering common Smartsheet needs such as data collection, project tracking, and team collaboration. It is stronger at linked data. For example, teams can create separate tables for customers and projects, projects and tasks, or products and suppliers, then keep information synchronized through linked records and reduce duplicate maintenance across multiple tables.

Key Differences From Smartsheet

Smartsheet is more focused on managing projects through worksheets, task progress, and cross-sheet reports, while Airtable is built on relational data. Users can create one-to-many and many-to-many relationships through linked records and use Interface to turn underlying data into pages for marketing, product, operations, or management teams.

This structure is suitable for scenarios involving many data objects and complex relationships. However, teams that rely heavily on Smartsheet’s task dependencies, resource management, and project portfolio capabilities should still confirm whether Airtable can cover their existing processes.

Which Teams Is It Best For?

Airtable is better suited to marketing, content, product, research, and operations teams. Common scenarios include content calendars, product roadmaps, campaign management, lightweight CRM, user research, and asset management. Teams that want to retain the flexibility of spreadsheet-style operations while connecting multiple data tables, configuring role-specific interfaces, and adding automation or AI can prioritize Airtable.

6. ClickUp: For Teams That Want to Consolidate Multiple Project Tools

Product Information

Website: https://clickup.com/
Documentation: https://help.clickup.com/hc/en-us
Pricing: https://clickup.com/pricing

What Is ClickUp?

ClickUp is an all-in-one work management platform that brings tasks, documents, whiteboards, goals, chat, calendars, and dashboards into one workspace. Teams can manage projects through list, board, Gantt, and timeline views, and use ClickUp Brain, AI agents, and automation for task summaries, content generation, information queries, and process execution.

Why Is It a Suitable Smartsheet Alternative?

ClickUp can cover common Smartsheet needs such as task assignment, project progress, automation, Gantt charts, and dashboards. Its task structure includes owners, priorities, dependencies, time tracking, and custom fields, while documents, communication, and goal management are integrated into project spaces. It is suitable for teams that want to reduce switching among multiple tools.

Key Differences From Smartsheet

Smartsheet is closer to a spreadsheet with project management capabilities, while ClickUp is centered on tasks and project execution. Team members primarily open tasks to review requirements, update progress, and communicate, making daily collaboration more centralized. Complex formulas, cross-table calculations, and large volumes of structured business data are not its main strengths.

Which Teams Is It Best For?

ClickUp is suitable for product, engineering, marketing, and operations teams, especially those currently using separate task, document, chat, and goal-management tools and wanting to bring them into one platform.

7. Asana: For Teams That Emphasize Ownership and Project Processes

Product Information

What Is Asana?

Asana is a collaborative project management platform organized around projects, tasks, owners, deadlines, and dependencies. Teams can use lists, boards, calendars, timelines, and Gantt charts to move projects forward, while forms, rules, dashboards, and portfolios support cross-team work. Asana also provides AI Studio and AI Teammates for building intelligent workflows, generating status reports, and assisting with project tasks.

Why Is It a Suitable Smartsheet Alternative?

Asana covers common Smartsheet needs such as task assignment, project timelines, dependencies, automation, and progress reporting. Task ownership and project processes are clearly defined, allowing members to see what they are responsible for, when work is due, and which tasks are blocking the project.

Key Differences From Smartsheet

Smartsheet allows teams to organize data freely around worksheets, while Asana places greater emphasis on standardized task execution. It is suitable for breaking plans into projects, milestones, and tasks, but it is less flexible for complex data tables, formula calculations, and relationships across multiple tables.

Which Teams Is It Best For?

Asana is suitable for marketing campaigns, product launches, operational plans, and cross-functional projects, especially for teams that want clear task owners, deadlines, dependencies, and project goals.

Asana is better suited to project execution than directly replacing a complex database. The Advanced plan costs significantly more than Starter, while cross-project management capabilities such as portfolios, goals, and workloads are mainly available in Advanced and higher plans.

Three-Year Pricing Summary

Even when plans are labeled Team, Standard, or Pro, the included project views, automation, permissions, and data management capabilities can differ substantially among products.

The following table provides an approximate view of each product’s budget.

The calculations use publicly listed annual billing prices for five and 15 editable members over three consecutive years. For each product, we selected a representative plan that is more suitable for ongoing team use.

Product	Reference Plan	Three-Year Cost for 5 Users	Three-Year Cost for 15 Users	Pricing Notes
Smartsheet	Business	$3,420	$10,260	Per-member subscription; includes timelines, workload management, and unlimited automation
NocoBase	Standard	$800	$800	One-time license with no user-based pricing; server and maintenance costs are separate
Baserow	Advanced	$3,240	$9,720	Per-paid-user subscription; includes more complete role and field permissions
monday	Pro	$3,420	$10,260	Per-seat subscription; includes higher automation limits and workload management
SmartSuite	Professional	$5,760	$17,280	Per-editor subscription; includes advanced permissions and higher data capacity
Airtable	Team	$3,600	$10,800	Primarily charges for editors; read-only users generally do not require paid seats
ClickUp	Business	$2,160	$6,480	Per-user subscription; AI and some enterprise management capabilities may require additional purchases
Asana	Advanced	$4,498.20	$13,494.60	Per-user subscription; includes portfolios, workload management, and approvals

We hope this article helps you find a Smartsheet alternative that better fits your team. Feel free to share it with teams evaluating project management tools, multi-dimensional spreadsheets, open-source self-hosted platforms, or enterprise business systems.

Related reading:

How a Volunteer Fire Department Manages 200 Callouts a Year with NocoBase

NocoBase — Thu, 23 Jul 2026 07:49:58 +0000

Originally published at https://www.nocobase.com/en/blog/polish-volunteer-fire-department-nocobase-case-study

A Volunteer Fire Department in Poland

Volunteer fire departments are an essential part of Poland’s fire protection system. Although their members serve their communities as volunteers, they take on many of the same responsibilities as professional fire services, including regular training, emergency response, vehicle and equipment management, and tracking personnel certifications.

OSP Radlin II is one of these active units and the busiest volunteer fire department in its county. Its operational team includes 30 fully trained responders and handles around 200 emergency callouts each year.

For every callout, the team must ensure that responders are properly qualified, vehicles are ready, and equipment is available. They also need to accurately record who participated, how long the operation lasted, how far each vehicle traveled, and which supplies were used.

To manage this work more effectively, the members of OSP Radlin II began searching for a system that could better support the department’s real operational needs.

From Google Drive to NocoBase

Previously, OSP Radlin II mainly relied on free cloud storage tools such as Google Drive to store and share information.

As incident records, member details, medical checks, rescue certifications, vehicle inspections, and equipment records continued to grow, important information became scattered across multiple files. There was also no consistent way to structure or update the data.

Cloud storage worked well for keeping documents, but it could not support the workflows needed to run an active fire department.

The team needed a centralized, secure platform that could be fully adapted to the department’s real operational needs.

To find the right solution, they tested more than ten similar platforms. After several rounds of evaluation, they chose NocoBase.

An Operations System Built by the Whole Team

From the start, the system was a collaborative effort. Members contributed to data entry, workflow design, and system maintenance based on their responsibilities, gradually creating a clear division of work.

Some members handle administrative work, including:
- Tracking equipment inspection deadlines
- Managing routine medical checks
- Maintaining rescue certifications
- Handling funding applications and other administrative tasks
Commanders record information from each emergency callout, including:
- Incident records
- Callout details
- Lists of participating crew members

The system is no longer maintained by a single person. Instead, the members directly involved in each area keep the information up to date. Today, it supports most of the fire department’s day-to-day operations.

System Homepage

The homepage gives members a single place to access their work. Calendars, tasks, announcements, member information, and quick actions are all available from one interface, helping each role quickly find what they need.

Track equipment inspection deadlines
Manage routine medical checks
Track rescue certifications
Manage funding applications and other administrative work
Record emergency responses
Add incident descriptions
Maintain crew participation lists

Emergency Response and Incident Management

Members can quickly create emergency response records from a tablet or mobile phone. They can enter departure and return times, incident type, location, vehicles used, participating crew members, and supplies consumed.

NocoBase then turns this information into useful statistics, including the number and types of incidents, vehicle mileage, and the total time each firefighter has spent on emergency responses.

Personnel, Qualifications, and Administration

Beyond incident management, the department uses NocoBase to maintain member profiles, medical clearances, rescue certifications, and other specialist qualifications.

Members responsible for administrative work also use the system to track funding applications and other day-to-day office tasks.

The team has also created a separate project board for non-emergency work, such as fire station renovations, community events, and other internal projects.

Vehicles, Equipment, and Maintenance

Fire engines, trailers, and firefighting equipment are all managed in the same system.

Members can record vehicle usage, mileage, technical condition, annual inspection dates, and upcoming equipment inspection or maintenance deadlines.

Automating Routine Work

As more information was centralized in NocoBase, the department began using workflows to automate tasks that had previously relied on manual checks and reminders.

Deadline Reminders

The system automatically monitors and sends reminders for important dates that may affect operational readiness, including:

Member medical examination deadlines
Fire vehicle inspection dates
Member birthdays and other important dates

Emergency Response Hours

Based on incident records, the system automatically calculates how much time each firefighter has spent participating in emergency operations.

Team Communication

An automated announcement system allows management to share important updates more consistently through both email and in-app notifications.

A System That Continues to Grow

The OSP Radlin II system is now about 90% complete. It covers around 80 members across the organization, with approximately 20 active users regularly entering and maintaining data.

By bringing its data into one place, the department can more easily track emergency callouts, vehicle mileage, equipment status, and the time each firefighter spends on emergency responses.

More importantly, the system is not a one-time project that stops evolving once it goes live. As more members use it, new needs continue to emerge, and the team keeps adding new features, automations, and operational workflows.

OSP Radlin II has no dedicated software development team. Instead, its members have used their deep understanding of the department’s day-to-day work to gradually turn real firefighting operations into a system that can support the organization for years and continue evolving with its needs.

More Customer Stories:

Weekly Updates: Added RunJS API for AI Employee Tasks in JS Blocks

NocoBase — Mon, 20 Jul 2026 08:19:35 +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.1.28

Release date: 2026-07-19

🐛 Bug Fixes

[client-v2] Fix mobile menus hidden incorrectly by device type rules (#10123) by @zhangzhonghe
[Workflow: Approval] Fix occasional errors when opening approval task details directly by @zhangzhonghe

v2.1.27

Release date: 2026-07-19

🚀 Improvements

[client-v2] Added Myanmar (my-MM) to the languages selectable in System Settings. (#10131) by @hongboji

🐛 Bug Fixes

[resourcer] Fixed pre-action workflows not triggering when used together with before-save approval workflows. (#10119) by @mytharcher
[flow-engine] Fix mobile popups exceeding the screen and hiding the close button (#10118) by @zhangzhonghe
[client-v2]
- Fix inconsistent route state after renaming a newly enabled page tab (#10117) by @zhangzhonghe
- Fix an error that could prevent approval pages from loading (#10116) by @zhangzhonghe
[utils] Ensured server-side outbound request redirects also comply with SERVER_REQUEST_WHITELIST (#10109) by @mytharcher
Reference: Environment variables
[Workflow: Approval] Fix messages overriding by @mytharcher

v2.1.26

Release date: 2026-07-17

🚀 Improvements

[undefined]
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources

🐛 Bug Fixes

[server] Prevented uploaded XML and other active content files from executing scripts in the application origin (#10104) by @mytharcher
[database] Fixed an SQL injection risk when reading database view metadata (#10115) by @2013xile
[client-v2]
- Reset unwanted border and shadow styles on Markdown h2 headings. (#10107) by @katherinehhh
- Corrected the Urdu label and added a separate Uzbek option to the System Settings language list. (#10090) by @hongboji
[AI employees] Fixed an error when sending files pasted into the AI employee chat input (#10106) by @cgyrock
[File storage: S3(Pro)] Fixed S3-compatible file URLs omitting the configured storage path, which caused uploaded logos and attachments to return 404 errors by @mytharcher

v2.1.25

Release date: 2026-07-15

🎉 New Features

[DingTalk] Added DingTalk Stream mode support for organization event synchronization. by @chenzhizdt
[Auth: LDAP] Added LDAP user data sync source support, including optional AD department synchronization. by @chenzhizdt

🚀 Improvements

[ai] Reduced main-process memory usage when parsing uploaded knowledge base documents. (#10083) by @cgyrock
[undefined]
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
[File storage: S3(Pro)] S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[RabbitMQ queue adapter] Enhance the channel management and error recovery capabilities of the RabbitMQ adapter by @sdp-ncd

🐛 Bug Fixes

[User data synchronization] Fixed external department sync order so child departments can be reparented correctly when their parent is synced later. (#10028) by @chenzhizdt
[Collection field: Markdown(Vditor)] Fixed iframe sanitization for v1 Markdown rendering and editing. (#10096) by @katherinehhh
[Workflow] Fixed hidden fields being included when workflow serializes appended association data (#10086) by @mytharcher
[AI employees] Fixed AI tool-call approvals to authorize against the message's owning conversation before updating decisions. (#10077) by @cgyrock
[Data source: External NocoBase]
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
- Fixed workflow AI employees being unable to read attachments from External NocoBase data sources by @2013xile

v2.1.24

Release date: 2026-07-13

🐛 Bug Fixes

[client-v2]
- Fixed other column content showing through fixed v2 table columns when quick edit is enabled. (#10076) by @katherinehhh
- Fixed v2 scan input camera preview layout issues on iOS Chrome. (#10081) by @katherinehhh
[app] Fixed Redis cache configuration ignoring the dedicated cache URL (#10065) by @2013xile
[Action: Batch edit] Fixed Markdown editor initialization failure when a V2 form includes a process field. (#10080) by @katherinehhh
[AI employees] Fixed AI attachment handling to avoid trusting client-provided file paths or URLs. (#10037) by @cgyrock
[Workflow] Fixed manual workflow execution returning an error when a valid request does not start an execution. (#10049) by @mytharcher
[Redis worker ID allocator]
- Improved Redis worker ID isolation and failure diagnostics by @2013xile
- Restored standalone startup without Redis worker ID configuration by @2013xile
[Workflow: Approval] Filter approval file associations by current user ownership when the temporary switch is enabled. by @mytharcher

v2.2.0-beta.15

Release date: 2026-07-16

🎉 New Features

[client-v2]
- Tabs on pages, subpages and pop-ups support the configuration of linkage rules (#10099) by @zhangzhonghe
- Add an environment variable to configure legacy and modern route entry modes. (#9891) by @Molunerfinn
[AI employees] Added RunJS APIs for triggering AI employee tasks from JS blocks. (#10061) by @cgyrock
[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
[Workflow] Migrate the Workflow settings page to the v2 client and share a reusable draggable category-tabs component via @nocobase/client-v2. (#9645) by @Molunerfinn
[Workflow: Database transaction node] 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] Add approval initiation and todo blocks for v2 pages by @zhangzhonghe
[DingTalk] Added DingTalk Stream mode support for organization event synchronization. by @chenzhizdt

🚀 Improvements

[undefined]
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10103) by @mytharcher
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) 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
[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
[Workflow: Manual node] Show manual workflow tasks in the V2 task center and guide users to the legacy page for processing (#10085) by @zhangzhonghe
[Workflow]
- 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]
- 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
[Collection: SQL] Not user-facing; added client-v2 unit test coverage for migrated plugins. (#9967) 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
[Logger] Added the Logger settings page to the client v2 runtime. (#9933) by @jiannx
[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
[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
[Workflow: JSON calculation] Migrated the workflow JSON calculation node configuration UI to the v2 workflow canvas while preserving v1 canvas compatibility. (#9902) by @mytharcher
[Backup manager] 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
[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
[AI: Knowledge base] 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
[File storage: S3(Pro)] S3 Pro uploads now return the created file record with permanent file URLs. 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

🐛 Bug Fixes

[client-v2]
- Corrected the Urdu label and added a separate Uzbek option to the System Settings language list. (#10090) by @hongboji
- 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 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
[flow-engine] Fixed an issue where users could type extra text after selecting a variable in single-value variable inputs. (#10050) by @katherinehhh
[AI employees] Fixed an error when sending files pasted into the AI employee chat input (#10106) by @cgyrock
[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
[Notification manager]
- Fix receiver selection saving user IDs as text (#10093) by @zhangzhonghe
- Fix incorrect workflow variables shown in CC configuration (#9937) by @zhangzhonghe
[Workflow: JSON variable mapping] Fix an error when selecting loop scope variables in the JSON variable mapping workflow node. (#10094) by @Molunerfinn
[UI layout] Fix the Mobile settings link losing the current sub-application path (#10078) by @zhangzhonghe
[Workflow]
- 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 the issue where in-app message content cannot be configured in v2 workflows (#9885) by @zhangzhonghe
- Fix issues after migrated client to v2 (#9929) by @mytharcher
- 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
[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
[Block: Comment] Adjusted the default action order for new Comment blocks. (#9976) by @jiannx
[Workflow: mailer node] Fixed workflow v2 test failures caused by missing mocks for trigger workflow action registration. (#9863) by @jiannx
[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
[File manager] Fixed 404 errors when uploading files to attachment URL fields in external data sources (#9809) by @2013xile
[Verification: TOTP authenticator] Fixed TOTP authenticator bindings so temporary setup secrets are removed and previously verified codes cannot be reused. 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
[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 NocoBase] Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
[plugin-service-platform]
- Restored licensed plugin downloads from the service platform. by @jiannx
- Disabled the service platform plugin download endpoint. by @jiannx
[Workflow: Subflow] Fixed workflow title search in the subflow node configuration selector. by @mytharcher
[File storage: S3(Pro)] Fixed S3-compatible file URLs omitting the configured storage path, which caused uploaded logos and attachments to return 404 errors by @mytharcher
[Auth: OIDC] Fixed OIDC automatic login redirects in production builds and retained the original modern-client path after login by @jiannx
[Workflow: Approval]
- Fix blank approval forms and missing or incorrect action buttons by @zhangzhonghe
- Fixed premature applicant validation and untranslated role labels in the approval workflow manual execution dialog. by @Molunerfinn
- Fix the approval workflow task title remaining editable in executed workflow configurations after production builds. by @Molunerfinn
- Allow users to view approval interfaces and cards after a workflow has been executed by @zhangzhonghe
- Fix workflow form action buttons responding in configuration dialogs by @zhangzhonghe
- Fix display and action issues in approval initiator interfaces by @zhangzhonghe
- Close the Apply new drawer when opening an approval form by @zhangzhonghe
- Fix an error that could prevent V2 pages from opening when approval and notification plugins are enabled by @zhangzhonghe
- Fix approval task form and action issues in the workflow v2 task center by @zhangzhonghe
- Fix v2 approval subtables not displaying correctly in details by @zhangzhonghe
- Fix missing processed approval details in v2 task detail popups by @zhangzhonghe
- Fix empty approval interfaces and fixed assignee IDs by @zhangzhonghe
- Fix the issue where approval tables appear in the block data source list by @zhangzhonghe
- Fix issues involved by migrating to client v2 by @mytharcher
- Fix the error when configuring approval workflow conditions by @zhangzhonghe
- Guide users to V1 pages when approval interfaces cannot be used in V2 by @zhangzhonghe
- Fix approval assignee sorting and hide unsupported legacy configuration entries by @zhangzhonghe
- Fix the error when opening CC node settings by @zhangzhonghe
- Fix missing approval data on approval task cards by @zhangzhonghe
[Collection field: Signature] Fix client-v2 signature field file collection selector localization and option filtering. by @katherinehhh
[WeCom] Fixed WeCom notification channels not saving the selected authenticator. by @jiannx

v2.2.0-beta.14

Release date: 2026-07-15

🎉 New Features

[Auth: LDAP] Added LDAP user data sync source support, including optional AD department synchronization. by @chenzhizdt

🚀 Improvements

[ai] Reduced main-process memory usage when parsing uploaded knowledge base documents. (#10083) by @cgyrock
[undefined] File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
[Flow engine] Support multi portals for ui build apis. (#10072) by @gchust
[File storage: S3(Pro)] S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[RabbitMQ queue adapter] Enhance the channel management and error recovery capabilities of the RabbitMQ adapter by @sdp-ncd

🐛 Bug Fixes

[client-v2]
- Fixed other column content showing through fixed v2 table columns when quick edit is enabled. (#10076) by @katherinehhh
- Fixed v2 scan input camera preview layout issues on iOS Chrome. (#10081) by @katherinehhh
[Workflow]
- Fixed hidden fields being included when workflow serializes appended association data (#10086) by @mytharcher
- Fixed manual workflow execution returning an error when a valid request does not start an execution. (#10049) by @mytharcher
[Collection field: Markdown(Vditor)] Fixed iframe sanitization for v1 Markdown rendering and editing. (#10096) by @katherinehhh
[Action: Batch edit] Fixed Markdown editor initialization failure when a V2 form includes a process field. (#10080) by @katherinehhh
[UI layout] Fixed the Mobile settings link opening the main application from a sub-application. (#10075) by @katherinehhh
[AI employees]
- Fixed AI tool-call approvals to authorize against the message's owning conversation before updating decisions. (#10077) by @cgyrock
- Fixed AI attachment handling to avoid trusting client-provided file paths or URLs. (#10037) by @cgyrock
[User data synchronization] Fixed external department sync order so child departments can be reparented correctly when their parent is synced later. (#10028) by @chenzhizdt
[Data source: External NocoBase]
- Fixed workflow AI employees being unable to read attachments from External NocoBase data sources by @2013xile
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
[Workflow: Approval] Filter approval file associations by current user ownership when the temporary switch is enabled. by @mytharcher

develop

v2.2.0-alpha.9

Release date: 2026-07-16

🎉 New Features

[client-v2] Tabs on pages, subpages and pop-ups support the configuration of linkage rules (#10099) by @zhangzhonghe
[AI employees] Added RunJS APIs for triggering AI employee tasks from JS blocks. (#10061) by @cgyrock
[DingTalk] Added DingTalk Stream mode support for organization event synchronization. by @chenzhizdt
[Auth: LDAP] Added LDAP user data sync source support, including optional AD department synchronization. by @chenzhizdt

🚀 Improvements

[undefined]
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10103) by @mytharcher
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources
[ai] Reduced main-process memory usage when parsing uploaded knowledge base documents. (#10083) by @cgyrock
[Workflow: Manual node] Show manual workflow tasks in the V2 task center and guide users to the legacy page for processing (#10085) by @zhangzhonghe
[File storage: S3(Pro)]
- S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
- S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[RabbitMQ queue adapter] Enhance the channel management and error recovery capabilities of the RabbitMQ adapter by @sdp-ncd
[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

🐛 Bug Fixes

[client-v2]
- Fixed automatic SSO redirect providers failing to preserve authentication order in production builds (#10100) by @jiannx
- Corrected the Urdu label and added a separate Uzbek option to the System Settings language list. (#10090) by @hongboji
- Workflow filters now preserve workflow variable expressions and show a clear parsing error when variable metadata cannot be resolved. (#10088) by @Molunerfinn
- Fixed v2 scan input camera preview layout issues on iOS Chrome. (#10081) by @katherinehhh
- Fixed other column content showing through fixed v2 table columns when quick edit is enabled. (#10076) 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
[AI employees]
- Fixed an error when sending files pasted into the AI employee chat input (#10106) by @cgyrock
- Fixed AI tool-call approvals to authorize against the message's owning conversation before updating decisions. (#10077) by @cgyrock
- Fixed AI attachment handling to avoid trusting client-provided file paths or URLs. (#10037) by @cgyrock
[Collection field: Markdown(Vditor)] Fixed iframe sanitization for v1 Markdown rendering and editing. (#10096) by @katherinehhh
[Workflow]
- Fixed hidden fields being included when workflow serializes appended association data (#10086) 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
[Notification manager] Fix receiver selection saving user IDs as text (#10093) by @zhangzhonghe
[UI layout]
- 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
[Workflow: JSON variable mapping] Fix an error when selecting loop scope variables in the JSON variable mapping workflow node. (#10094) by @Molunerfinn
[User data synchronization] Fixed external department sync order so child departments can be reparented correctly when their parent is synced later. (#10028) by @chenzhizdt
[Action: Batch edit] Fixed Markdown editor initialization failure when a V2 form includes a process field. (#10080) by @katherinehhh
[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 workflow AI employees being unable to read attachments from External NocoBase data sources by @2013xile
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
[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
[File storage: S3(Pro)] Fixed S3-compatible file URLs omitting the configured storage path, which caused uploaded logos and attachments to return 404 errors by @mytharcher
[Auth: OIDC] Fixed OIDC automatic login redirects in production builds and retained the original modern-client path after login by @jiannx
[Workflow: Approval]
- Fix the approval workflow task title remaining editable in executed workflow configurations after production builds. by @Molunerfinn
- Fixed premature applicant validation and untranslated role labels in the approval workflow manual execution dialog. by @Molunerfinn
- Fix workflow form action buttons responding in configuration dialogs by @zhangzhonghe
- Allow users to view approval interfaces and cards after a workflow has been executed by @zhangzhonghe
- Filter approval file associations by current user ownership when the temporary switch is enabled. by @mytharcher
- Fix display and action issues in approval initiator interfaces by @zhangzhonghe
- Fix blank approval forms and missing or incorrect action buttons by @zhangzhonghe
- Fix an error that could prevent V2 pages from opening when approval and notification plugins are enabled by @zhangzhonghe
- Guide users to V1 pages when approval interfaces cannot be used in V2 by @zhangzhonghe
[WeCom] Fixed WeCom notification channels not saving the selected authenticator. by @jiannx

Announcing NocoBase 2.2-beta

NocoBase — Fri, 17 Jul 2026 04:04:27 +0000

Originally published at https://www.nocobase.com/en/blog/2.2.0-beta

This is a major upgrade centered on the V2 experience. This release brings Multi Portal, a new mobile client, and a new comment block, while continuing to enhance the AI knowledge base and workflow capabilities. For teams already using V2, the more noteworthy addition is the brand-new /v/ branch—it will serve as a dedicated front-end entry for V2 and carry forward all future feature development.

New Features

The new `/v/` branch

/v/ is a brand-new, standalone front-end entry that is built independently. In the 2.0 release we carried out a very large refactor of the front end, and at the time, for compatibility reasons, we kept support for V1 modules, pages, and so on. The /v/ branch, however, completely removes the V1 legacy content—you can no longer create or render V1 pages and blocks, and it keeps only V2-oriented capabilities. At the same time, the /v/ branch has been significantly optimized in terms of performance, and it will be the main branch that the NocoBase team iterates on going forward.

We recommend that, if your production environment consists entirely of users centered on v2 Pages, you consider starting to use the /v/ branch, so that upcoming new feature iterations can be used directly.

If you are centered on v2 Pages but have a small number of v1 Pages, consider first migrating the v1 Pages to v2 Pages, and then consider using the /v/ branch.

If you are centered on v1 Pages, we do not recommend switching directly to the /v/ branch. We suggest you first migrate your current v1 Pages to v2 Pages, and then switch to the /v/ branch.

Typically, you only need to add the /v/ prefix before the original path to enter the /v/ branch.

For example:

# Original path
https://nocobase.example.com/admin/1xl0epqn6q3

# v branch path
https://nocobase.example.com/v/admin/1xl0epqn6q3

Setting the application's default entry

You can control the application's entry mode via the environment variable APP_CLIENT_ENTRY_MODE:

legacy-default: both / and /v/ are accessible, and the default entry is /
modern-default: both / and /v/ are accessible, and the default entry is /v/
modern-only: only /v/ is accessible

Current status of the `/v/` branch

The /v/ branch is a progressive-migration branch. After entering the /v/ branch, there will be a few noticeable changes:

Pages created via Page V1 will no longer be displayed in the /v/ branch. Pages created via Page V2 will still display normally in the /v/ branch.
Plugins that are only adapted for client-v1 will no longer be loaded in the /v/ branch. The /v/ branch only loads plugins adapted for client-v2. For details, refer to the Client-side plugin development documentation.

At present, most of the plugins built into NocoBase have been adapted and migrated to client-v2 in this release, so most features can be used directly (a small number of plugins have not yet been migrated, and we will keep migrating them). However, some capabilities provided by certain plugins will only be updated and iterated on the /v/ branch going forward. Specifically:

The plugin list no longer shows deprecated plugins or plugins that support only 1.x
Adding new Page V1 is no longer supported
Public forms distinguish between v1 and v2; the /v/ branch does not display v1 public forms
If you want to use approval workflows on the /v/ branch, you need to reconfigure the related UI
The new mobile client is only supported on the /v/ branch
Multi Portal is only supported on the /v/ branch
The Display configuration for sub-applications in the App supervisor has been removed; you can use Portals instead
The "AI Employees / Data Sources" tab has been removed
The comment table, calendar table, expression table, and external data table have been removed
The workflow manual node is not yet supported on the /v/ branch
Adding badge counts to menus is not yet supported

You can carry out the migration to the /v/ branch based on the actual situation of your production environment.

Multi Portal (only supported on the `/v/` branch)

Portals are used to provide multiple access entries within the same application. Each Portal can have its own independent pages, menus, navigation structure, layout, and permission configuration. (Supported in the Professional edition and above)

In real-world business scenarios, different roles usually need different operational interfaces. For example, a retail management system:

Retail management system

├─ Headquarters Portal
├─ Store Portal
├─ Dealer Portal
└─ Mobile Portal

Headquarters staff care about:

Product management
Inventory management
Data analysis

Store staff care about:

Checkout
Stock counting
Order processing

Dealers care about:

Procurement
Reconciliation
Shipping status

Even though they use the same system, different roles don't need to see the same menus and pages. Multi Portal is precisely what solves this problem.

Reference documentation:

Multi Portal

New mobile client (only supported on the `/v/` branch)

The new mobile client provides a brand-new /v/mobile entry, and at the same time, Portals also support adding Portals with a mobile layout.

The mobile layout and desktop layout use the same data source and business data, but menus, routing, and page content are configured separately. This allows you to reorganize pages according to how they are used on mobile, without being constrained by the desktop page structure. In addition, using the bottom tab bar as the primary navigation makes it better suited for data entry, querying, approval, and task handling on phones.

Reference documentation:

Mobile layout

New comment block

The new comment block is no longer limited to the comment table of the main data source, and it can be used even outside of relationship blocks. The comment block is used to add commenting capabilities to business records. You can add a comment block on the detail page or popup of records such as tasks, articles, tickets, and customers, allowing users to view, reply to, and add comments around the current record.

Reference documentation:

Comment block

AI knowledge base improvements

In this release, the AI knowledge base has also completed its migration to the client-v2 version. In addition, when a workflow creates knowledge base documents, it now supports overwriting by the knowledge base document's key.

Reference documentation:

AI knowledge base

Workflow: Database transaction node

The workflow adds a database transaction node. It is used to execute a group of database operations within the same transaction. It is suited for scenarios that need to guarantee "all succeed or all roll back" across multi-step data processing—for example, deducting inventory, writing line items, and updating status after creating an order.

Reference documentation:

Database transaction node

The following plugins are no longer supported in V2 (deprecated but not yet removed)

Some plugins were actually deprecated much earlier. Some of them can still be used at present, but they will be completely removed in V3.

Plugin	Replacement	Notes
`@nocobase/plugin-audit-logs`	`@nocobase/plugin-audit-logger`	Deprecated since 1.0
`@nocobase/plugin-backup-restore`	`@nocobase/plugin-backups`	Deprecated since 1.0
`@nocobase/plugin-block-multi-step-form`	JS Block	Deprecated since 2.0
`@nocobase/plugin-charts`	`@nocobase/plugin-data-visualization`	Deprecated since 2.0
`@nocobase/plugin-collection-fdw`	Sync from database	Deprecated since 2.2
`@nocobase/plugin-comments`	`@nocobase/plugin-block-comment`	Deprecated since 2.2
`@nocobase/plugin-custom-variables`	Event flow	Deprecated since 2.2
`@nocobase/plugin-data-visualization-echarts`	`@nocobase/plugin-data-visualization`	Deprecated since 2.0
`@nocobase/plugin-disable-pm-add`	None	Deprecated since 2.2
`@nocobase/plugin-field-component-mask`	RunJS	Deprecated since 2.0
`@nocobase/plugin-graph-collection-manager`	None	Deprecated since 2.2
`@nocobase/plugin-mobile-client`	`@nocobase/plugin-ui-layout`	Deprecated since 2.0
`@nocobase/plugin-mobile`	`@nocobase/plugin-ui-layout`	Deprecated since 2.0
`@nocobase/plugin-mock-collections`	AI-assisted building	Deprecated since 2.0
`@nocobase/plugin-multi-app-manager`	`@nocobase/plugin-app-supervisor`	Deprecated since 2.0
`@nocobase/plugin-multi-app-share-collection`	None	Deprecated since 1.0
`@nocobase/plugin-notifications`	`@nocobase/plugin-notification-manager`	Deprecated since 1.0
`@nocobase/plugin-snapshot-field`	None	Deprecated since 1.0

5 Open-Source AI No-Code Tools for Complex Relational Data Models

NocoBase — Thu, 16 Jul 2026 05:49:45 +0000

Originally published at https://www.nocobase.com/en/blog/open-source-ai-no-code-tools-complex-relational-models

When teams use no-code tools to manage data, many start with Airtable, Notion, or Google Sheets for customers, orders, and project data. As the number of tables, relationships, permissions, and automation workflows grows, simple spreadsheet-style tools can gradually become hard to maintain.

The rise of AI has opened up new possibilities.

In a Reddit discussion about “Claude + Airtable” and “Claude + Sheets” workflows, a user shared their hands-on experience:

Google Sheets with Claude is suitable for fast setup and lightweight workflows. When a project involves multiple related tables, different views, member permissions, and complex data structures, it is clearer and easier to maintain if structured data is kept in Airtable or a database, while Claude handles data processing, information enrichment, and workflow automation. However, Airtable is a commercial closed-source product. For teams with limited budgets, or teams that care more about self-hosting, data control, and long-term extensibility, it may not be the right choice.

This article looks at five open-source AI no-code tools that are suitable for complex relational models, with a focus on their relationship modeling capabilities and AI capabilities.

1. NocoBase

Best for building complex enterprise business systems such as CRM, ERP, order management, project management, approvals, and ticketing.

Website: https://www.nocobase.com/en/
GitHub: https://github.com/nocobase/nocobase
GitHub Stars: 23.3k
Documentation: https://docs.nocobase.com/

NocoBase is an open-source AI no-code platform. It is built around data modeling and separates business data from page presentation. Teams can first create tables and relationships for customers, contacts, orders, products, and other objects, then configure pages and business features through a WYSIWYG interface. Its plugin-based architecture also makes it possible to add or develop new features for specific business needs.

Complex Relational Modeling

NocoBase supports one-to-one, one-to-many, many-to-one, and many-to-many relationships. For many-to-many relationships, you can use a junction table to connect two collections and store business fields such as quantity, price, status, and time in that junction table.

Take an order system as an example. You can create four tables: customers, orders, products, and order items. The order items table acts as the junction table between orders and products, recording purchase quantity, transaction price, discount, and subtotal. This keeps the many-to-many relationship between orders and products while preserving the detailed information for each transaction.

In the interface, related data can be displayed and maintained through dropdown selectors, record pickers, sub-forms, sub-tables, and sub-detail blocks. Sub-forms are suitable for directly editing related records, while sub-tables are better for managing one-to-many or many-to-many data in batches.

Association field documentation: https://docs.nocobase.com/data-sources/data-modeling/collection-fields/associations/

Many-to-many relationship documentation: https://docs.nocobase.com/data-sources/data-modeling/collection-fields/associations/m2m/

Association field components: https://docs.nocobase.com/interface-builder/fields/association-field

AI Building Capabilities

NocoBase can work with AI agents such as Claude Code, Codex, and Cursor to configure systems from natural language instructions.

For example, if you enter “I am building a CRM. Please help me design and build the data model,” AI can create tables such as customers, contacts, opportunities, and orders, add fields, and configure relationships. The data modeling skill also supports modifying and deleting tables, adding fields, and adjusting existing relationships.

In addition to data modeling, NocoBase Skills also cover:

Page and block configuration;
Workflow creation and diagnosis;
Role and permission configuration;
Plugin management;
Release, migration, and backup;
Version saving and recovery.

Data models, pages, workflows, and permissions created by AI can still be reviewed and modified in the no-code interface. Teams can let AI build the initial structure first, then have business users adjust fields, page layouts, and interaction details.

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

AI data modeling documentation: https://docs.nocobase.com/ai-builder/data-modeling

AI Employees

After the system is built, AI can also participate in daily operations as AI employees.

AI employees can read the current page, data blocks, data structure, and selected content, and call the appropriate skills to complete queries, analysis, filling, configuration, and content generation. They can also join workflows to process information or perform tasks within business processes.

For example, teams can ask AI employees to:

Analyze customer and sales data;
Organize or supplement form content;
Generate reports from current page data;
Process documents or assist with task assignment in workflows;
Answer business questions using an enterprise knowledge base.

AI building and AI employees play different roles. AI building is used to create and adjust systems, while AI employees assist with business work inside a running system.

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

External Data Sources and Deployment

The main NocoBase database supports MySQL, PostgreSQL, and MariaDB. Through data source plugins, it can also connect to external MySQL, MariaDB, PostgreSQL, Microsoft SQL Server, Oracle, REST APIs, and other NocoBase applications.

After connecting to an external database, NocoBase reads the existing tables and fields, and teams can configure pages and other business features based on that data. Table structures in external databases need to be modified in the original database and then synchronized to NocoBase. Different external data source plugins may have different version requirements, so the specific requirements should be checked before use.

NocoBase Community Edition provides the full source code, supports private deployment, and does not limit the number of applications, users, or records. Some external data source, enterprise management, and advanced features are included in commercial editions.

Data source management documentation: https://docs.nocobase.com/data-sources/data-source-manager/

External database documentation: https://docs.nocobase.com/data-sources/data-source-manager/external-database

Use Cases

NocoBase is suitable for CRM, sales management, ERP, inventory and sales management, order and inventory management, project management, approvals, ticketing, contract management, and supplier management. It is better suited to projects with many tables, complex relationships, and long-term needs to adjust data structures and system features.

2. Baserow

Best for teams migrating from Excel, Google Sheets, or Airtable to an open-source database.

Website: https://baserow.io/
GitHub: https://github.com/baserow/baserow
GitHub Stars: 5.3k
Documentation: https://baserow.io/user-docs/

Baserow is an open-source AI no-code platform for building databases, business applications, automation workflows, and AI agents. It keeps a spreadsheet-like editing experience, allowing users to start from data tables and gradually add field relationships, views, forms, and application pages.

Complex Relational Modeling

Baserow mainly connects different tables through the “link to table” field. By default, one field can link to multiple records, making it suitable for many-to-many relationships. If multiple selections are disabled, it can be restricted to a one-to-one relationship. When a relationship is created, the system can also automatically create a reverse relationship field in the other table.

After relationships are established, lookup fields can read fields from related tables, rollup fields can calculate counts, sums, averages, maximums, or minimums, and formulas can be used for further processing.

If you need to record purchase quantities, prices, or discounts between orders and products, you can create a separate “order items” junction table and link it to the orders and products tables.

AI Capabilities

Baserow’s AI assistant, Kuma, can create and modify tables, fields, views, and relationships from natural language. It can also generate formulas, add filters and groups, and organize existing data.

Kuma can also generate complete application pages, connect data sources, add forms and actions, and continue adjusting page structure and style based on follow-up instructions.

In addition, AI prompt fields can summarize, classify, and extract information from table content, and regenerate results when source fields change. This feature is included in the Premium plan and above.

Kuma AI documentation: https://baserow.io/user-docs/ai-assistant

Use Cases

Baserow is suitable for lightweight CRM, project and task management, content libraries, asset libraries, and scenarios that migrate from spreadsheets to structured data management. It is closer to an open-source Airtable alternative with AI capabilities, and is suitable for teams that value spreadsheet-style operation and self-hosting.

3. Teable

Best for teams that want to keep a spreadsheet-style interface while using a PostgreSQL-based data foundation.

Website: https://teable.ai/
GitHub: https://github.com/teableio/teable
GitHub Stars: 21.5k
Documentation: https://help.teable.ai/en/

Teable is a no-code database built on PostgreSQL, with an interface similar to Airtable. Users can manage data in tables, then gradually add relationship fields, calculated fields, application pages, and automation workflows.

Complex Relational Modeling

Teable’s relationship fields support one-to-one, one-to-many, many-to-one, and many-to-many relationships, and can be configured as one-way or two-way relationships. After relationships are established, lookup, rollup, conditional lookup, and conditional rollup fields can be used to read or aggregate data across tables.

For example, you can connect customers with orders, projects with tasks, and students with courses. In an order scenario, an order items table can also be used to record products, quantities, and prices.

AI Capabilities

Teable AI can analyze current data and generate charts and reports. It can also create or modify tables, fields, views, applications, and automation workflows. Users can directly describe the database or business application they need, then continue refining the generated result.

AI chat documentation: https://help.teable.ai/en/basic/ai/ai-chat

AI app builder documentation: https://help.teable.ai/en/basic/ai/app-builder

Use Cases

Teable is suitable as an Airtable alternative, collaborative database, order management tool, project management tool, and PostgreSQL data management layer. Teams that want both AI app building and self-hosting should further confirm which edition includes the required features.

4. ToolJet

Best for connecting existing databases and quickly generating admin panels and internal business applications.

Website: https://www.tooljet.com/
GitHub: https://github.com/ToolJet/ToolJet
GitHub Stars: 38.2k
Documentation: https://docs.tooljet.com/docs/

ToolJet is an open-source low-code application builder. It can connect to databases, APIs, cloud storage, and business software, then create admin panels, dashboards, and internal tools based on existing data. The community edition provides a visual page builder, a built-in database, and data source connection capabilities.

Complex Relational Modeling

ToolJet’s built-in database supports primary keys, foreign keys, unique constraints, and joins. Users can connect different tables using foreign keys and read related data based on existing relationships.

Many-to-many relationships usually require a junction table, with foreign keys pointing to the two business tables. ToolJet can also connect directly to PostgreSQL, MySQL, MongoDB, and many APIs, so it is better suited to building applications on top of existing data structures.

Database editor documentation: https://docs.tooljet.com/docs/tooljet-db/database-editor/

AI Capabilities

ToolJet AI can generate application pages, data structures, queries, and data bindings from natural language. It can also read existing database structures and create applications on top of existing data. After generation, users can continue adjusting pages, components, and queries.

ToolJet AI also provides query generation, component debugging, and AI agent building features. Its main AI capabilities belong to the enterprise edition, while the open-source community edition focuses on visual app building and data connections.

AI builder documentation: https://docs.tooljet.com/docs/build-with-ai/overview/

Use Cases

ToolJet is better suited for admin panels, internal operations tools, data query platforms, and business applications built on existing databases. Its strengths are clearer for teams that already have a database structure and want to quickly add pages and operation interfaces.

5. Budibase

Best for building form, approval, ticketing, and workflow-based internal applications.

Website: https://budibase.com/
GitHub: https://github.com/Budibase/budibase
GitHub Stars: 28.1k
Documentation: https://docs.budibase.com/docs/

Budibase is an open-source internal tool and workflow automation platform. It can connect to existing databases, APIs, and business systems, or use its built-in database to create forms, data pages, applications, and automation workflows.

Complex Relational Modeling

Budibase relationship fields support two-way relationships, and one record can also be linked to multiple records, making many-to-many relationships possible.

When connecting to external databases such as PostgreSQL, MySQL, MariaDB, Microsoft SQL Server, or Oracle, many-to-many relationships need to use a junction table. The junction table stores foreign keys pointing to both data tables, and Budibase then reads and manages related data based on those relationships.

SQL data source documentation: https://docs.budibase.com/docs/sql-datasource

AI Capabilities

Budibase AI can generate tables, fields, relationships, and sample data for the built-in database from prompts. It can also generate JavaScript and perform text classification, translation, summarization, content generation, and document information extraction in automations. The platform also supports building AI agents that can call data and workflows.

The AI table generation feature currently applies only to the built-in Budibase DB. It can generate one or more tables and their relationships, but it does not generate application pages at the same time. Before production use, field types and relationships should still be checked.

AI-powered table generation documentation: https://docs.budibase.com/docs/ai-powered-table-generation

Budibase AI configuration documentation: https://docs.budibase.com/docs/quickstart-budibase-ai

Use Cases

Budibase is suitable for approval and request forms, ticketing systems, internal operations tools, and data pages and automation workflows built on existing SQL databases. It is especially strong in forms, workflows, and AI-powered data processing.

Hope this article helps you find the right open-source AI no-code tool for complex relational models more quickly. Feel free to share it with teams evaluating Airtable alternatives, AI app builders, or internal business system tools.

Related reading:

Automating Company Background Research with Workflows and AI Employees

NocoBase — Tue, 14 Jul 2026 06:33:08 +0000

Originally published at https://www.nocobase.com/en/blog/automate-company-background-research-with-workflows-and-ai-employees

In NocoBase, company background research can be turned into a traceable automation flow. Business users still work on the familiar company profile page, while workflows and AI employees fill in background information, record the processing steps, and keep every generated report for later review.

This scenario addresses a common problem: company background information is not a static field that only needs to be entered once. Public information changes, regulatory events may appear, and cooperation status keeps evolving as business moves forward. If everything depends on manual updates, key information can easily be missed. If AI is allowed to overwrite company profiles directly, it becomes hard to explain how a given judgment was made. The approach here is to store current information and the research process separately. The company record keeps the version business users are working with, while background check records keep the status, output, and history of every AI research task.

Start With Two Tables

The company table provides the basic information about the research target, while the background check task table receives each research task. One stores the currently available information; the other stores the process and historical results.

`companies`: Company Table

Key Field	Purpose
Company name	Serves as the main identifier of the research target.
Website	Provides an official website clue and reduces misjudgment caused by companies with similar names or abbreviations.
Address	Helps identify region, legal entity, and business scope.
Company type	Marks business relationships such as customer, supplier, or partner, making it easier to prioritize follow-up.
Background information	Stores the company background report currently in use and presents structured content in Markdown.

`background_check_tasks`: Background Check Task Table

Key Field	Purpose
Company ID / Company name	Records which company this research task is for, making execution and historical review easier.
Status	Tracks task transitions from`pending` to `processing` and `completed`; it also helps prevent duplicate triggers.
Research report	Stores the full research report generated by AI for this run.
Summary	Stores AI’s summary of the research process, risk points, and information that still needs to be supplemented.
Previous background	Stores the previous version before write-back, supporting history tracking and report comparison.

Enter the Research Flow From Company Profiles

The company list is the most familiar entry point for business users. On the page, they can see company names, websites, company types, contacts, email addresses, and other information. After opening a company, users can view the current background report or actively start a new background research task.

On the edit page, Background information is displayed with a Markdown editor. The AI output is not a short summary, but a structured report that can be read, copied, and maintained directly. Business users can still edit it manually, but every AI-generated result will leave a corresponding history record in the background check task table.

As a result, the page still looks like a normal company profile management interface, but the underlying structure has become “current information + research history.” The company table stores the current version, while the task table stores the process and evidence chain.

Three Trigger Methods

Background research should not depend on only one manual button. In real business work, you may want to automatically complete information after a new company is added, rerun checks for historical records on a schedule, or actively start a new review before signing, revisiting, or reassessing a company.

The New company background check workflow handles automatic research after a company is added or updated. It listens to data events in the company table and is triggered when a company name exists and background information is empty. After triggering, it does not call AI immediately. Instead, it first checks whether there is already an unfinished task for the same company. Only when no such task exists does it create a new background check record.

The Timing company background check workflow continuously supplements historical data. It runs every 30 minutes, queries companies whose background information is still empty, and processes them in batches through a loop. Inside the loop, it also checks whether a task already exists before deciding whether to create a new one. This allows the scheduled task to run repeatedly without creating multiple concurrent processing records from repeated scans.

The Manual company background check workflow is bound to the Run background check button on the company detail page. It is suitable for business users who want to actively start a research task before visits, signing, or reassessment. Manual and automatic triggers use the same downstream chain: first create a background check record, then let the task execution workflow take over AI research.

These three entry points solve problems at different moments, but they all converge into the same background check task table. New-record triggers, scheduled triggers, and manual triggers only record that “research is needed.” The actual execution, status management, and result write-back are handled by the downstream workflow in a unified way.

Turn AI Research Into Tasks

Do company background check is the workflow that actually performs the research. It listens to pending records in the background check task table. Once an automatic, scheduled, or manual flow creates a task, this workflow is triggered asynchronously.

During execution, the workflow first checks whether the company still exists. If the company no longer exists, the task is closed with an explanation. If the company exists, the task status changes to processing, and the workflow then calls an AI employee to generate the report. The AI employee’s prompt requires two outputs: a Markdown report that can be written directly into the company background field, and a summary for manual review.

After AI returns structured results, the workflow first writes the report, summary, and previous background content into the background check record, then writes the new report back to the company record. This order avoids the problem of having only the latest result without a process record: the company page keeps the latest usable content, while the task record keeps the context of this generation and the content before write-back.

After research is task-based, batch processing also becomes more natural. The scheduled workflow does not need to wait for each company’s research to finish. It only creates multiple pending records; each record then independently triggers AI research. Multiple companies can move forward in parallel, and a failure or timeout in one task will not block the others.

Make AI Results Reviewable

AI-generated reports follow a fixed structure: company overview, core business, development history and capital background, market position and competitive perspective, sales follow-up judgment, and reference links. Business users see more than a conclusion. They can also review the risk notes and missing information highlighted by AI in the summary.

The background check record detail page displays Research report and Previous background in separate tabs and provides a Copy action. This makes it easy to copy the current report during discussion, review, or external communication, and to compare it with the previous version when needed.

The record detail page also includes two AI employee tasks:

Improve background research report: supplement information through conversation, regenerate the report, and write the result back to the company record.
Compare new and old background research reports: read both reports and let AI explain what substantive changes this update introduced.

This allows AI to go beyond generating a one-time text. It participates in continuous maintenance, review, and version comparison.

How the Workflows Fit Together

At a high level, this set of workflows can be divided into four layers.

The first layer creates tasks. New company background check handles companies after creation or update, Timing company background check supplements historical data, and Manual company background check supports active manual initiation. They all check for unfinished records before creating a task, reducing duplicate processing at the source.

The second layer executes tasks. Do company background check listens to background check records, moves pending tasks into processing, calls the AI employee, and writes the report, summary, and current company background field after completion.

The third layer provides AI employees with controlled write-back capability. Update company background works as a tool workflow, restricting AI to write into specified records with explicit parameters instead of granting overly broad data modification permissions.

The fourth layer cleans up exceptions. Clean overtime processing background check runs every 30 minutes and cleans up non-completed tasks that have remained unfinished for more than 15 minutes, preventing interrupted tasks from staying in the processing state for too long.

Where This Pattern Can Be Reused

This scenario is not just a standalone form or a single AI button. It combines several NocoBase capabilities: data tables carry business objects and history records, pages allow business users to view and trigger actions, workflows handle scheduling and write-back, and AI employees generate structured results that can be reviewed.

The same pattern can be applied to supplier onboarding, customer due diligence, contract risk pre-review, lead quality scoring, public opinion tracking, investment target screening, and similar scenarios. Whenever a business process requires continuously completing information, keeping traces of AI results, and preserving historical versions instead of overwriting them, this approach can be used to build a runnable, traceable, and extensible automation flow.

Reference Documents

Weekly Updates: Added Structured AI Usage Records

NocoBase — Mon, 13 Jul 2026 06:43:59 +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.1.23

Release date: 2026-07-10

🐛 Bug Fixes

[client-v2]
- Fixed v2 ScanInput recognition for Safari QR images selected from the upload path. (#10011)by katherinehhh
- Fixed client runtime asset base URL normalization when __webpack_public_path__ is injected without a trailing slash, and added coverage for that edge case. (#10040)by chenos
- Fixed an issue where button linkage rule states in table blocks could become polluted after pagination. (#10038)by gchust
[app] Fix lazy-loaded assets using an external script URL when CDN_BASE_URL is empty. (#10052)by Molunerfinn
[flow-engine] Fixed an issue where overriding ctx.api in a JS block could cause a Maximum call stack size exceeded error. (#10051)by gchust
[Workflow: Delay node] Prevented delay nodes from accepting numeric durations less than 1 through the API (#10057)by mytharcher
[Form drafts] Fixed form drafts disappearing after consecutive page refreshes (#10059)by gchust
[Data source: Main] Prevented invalid many-to-many relationship field configurations from being saved (#10044)by 2013xile
[Collection: Tree] Fixed tree path collection creation to avoid passing internal field model metadata into collection options. (#10035)by cgyrock
[Workflow] Fixed subflow nodes remaining pending when the child workflow fails before creating an execution record (#10043)by mytharcher
[Flow engine]
- Fixed an issue where using a local AI agent to configure linkage rules could trigger rendering errors. (#10023)by gchust
- Fixed popup record variables failing to resolve from external NocoBase data sources (#10048)by gchust
[Template print] Fixed template print permission checks so hidden fields and records outside the current role's view scope are not rendered.by jiannx
[Workflow: Approval]
- Allow string type of assignee ID to be addedby mytharcher
- Fix approval form fields becoming single-column in print previewby zhangzhonghe
- Fix the issue where fields in disabled approval subtables can still be editedby zhangzhonghe

v2.1.22

Release date: 2026-07-09

🐛 Bug Fixes

[client-v2]
- Fix association fields showing the default operator setting in filter forms (#10025)by zhangzhonghe
- Fix mobile popup spacing for table quick edit and select fields (#10020)by zhangzhonghe
[cli] Fixed NocoBase CLI default value issues for image registry fallback, built-in database images, env info display, and prompt initialization. (#10027)by chenos
[Authentication] Fix the issue where reset password links open the sign-in page (#10006)by zhangzhonghe

v2.1.21

Release date: 2026-07-08

🎉 New Features

[AI employees] Add OrcaRouter as an LLM provider (#10003)by jinhaosong-source

🚀 Improvements

[Workflow] Remove arithmetic operators for condition node (#10019)by mytharcher

🐛 Bug Fixes

[client-v2]
- Fixed stale linkage field states when switching records in runtime edit popups. (#10010)by katherinehhh
- Fixed an issue where association field default values in filter forms could not be cleared. (#10022)by gchust
[File manager]
- Reject active-content filenames during file upload unless the configured storage MIME type rule explicitly allows them. (#10021)by mytharcher Reference: Local storage, Security guide
- Fixed missing Attachment field interface in v2 data table management, and fixed image upload preflight checks for public form file relationship fields. (#10012)by katherinehhh
[Data source manager] Hide the historical attachment field interface from the V2 data table Add field menu. (#10018)by katherinehhh
[Data visualization] Fixed chart click interactions that could stop working after chart rerendering (#10031)by 2013xile
[Migration manager] Fixed an issue where migration could leave an app stuck on the repair screenby 2013xile
[App supervisor] Fixed app JWT secret isolation so main app tokens are no longer accepted by sub apps after an independent secret is enabledby 2013xile

v2.1.20

Release date: 2026-07-07

🚀 Improvements

[cli]
- Improved the Docker CLI setup by supporting configurable default NocoBase image registry/variant, fixing proxy and no-nginx image port compatibility, and adding Docker Nginx/Caddy installation guides. (#9972)by chenos
- Refactor CLI setup startup to reuse nb app start, normalize API base path redirects, persist shared env proxy defaults, and rebuild Docker proxy containers when published ports change. (#9997)by chenos

🐛 Bug Fixes

[client-v2]
- Fixed Vditor asset loading in production by resolving plugin CDN paths from the effective webpack public path. (#10008)by chenos
- Fixed an issue where Quick Edit could fail to switch dropdown options when navigating between pages. (#10007)by gchust
[flow-engine] Fixed an issue where popup configuration became inconsistent when toggling design modes. (#10005)by gchust
[File manager] Reject active-content filenames during file upload unless the configured storage MIME type rule explicitly allows them. (#9994)by mytharcher
Reference: Local storage, Security guide
[Data source: External MariaDB] Fix Add all collections toggle in MySQL, MSSQL, and MariaDB external data source settings.by katherinehhh

v2.2.0-beta.13

Release date: 2026-07-12

🐛 Bug Fixes

[Redis worker ID allocator] Restored standalone startup without Redis worker ID configurationby 2013xile

v2.2.0-beta.12

Release date: 2026-07-11

🐛 Bug Fixes

[server] Fixed custom portals missing when multi-application plugins are disabled (#10055)by 2013xile
[app] Fixed Redis cache configuration ignoring the dedicated cache URL (#10065)by 2013xile
[Redis worker ID allocator] Improved Redis worker ID isolation and failure diagnosticsby 2013xile

v2.2.0-beta.11

Release date: 2026-07-11

🐛 Bug Fixes

[app] Fix lazy-loaded assets using an external script URL when CDN_BASE_URL is empty. (#10052)by Molunerfinn
[client-v2]
- Fixed v2 ScanInput recognition for Safari QR images selected from the upload path. (#10011)by katherinehhh
- Fixed an issue where button linkage rule states in table blocks could become polluted after pagination. (#10038)by gchust
- Fixed client runtime asset base URL normalization when __webpack_public_path__ is injected without a trailing slash, and added coverage for that edge case. (#10040)by chenos
[flow-engine] Fixed an issue where overriding ctx.api in a JS block could cause a Maximum call stack size exceeded error. (#10051)by gchust
[Workflow: Delay node] Prevented delay nodes from accepting numeric durations less than 1 through the API (#10057)by mytharcher
[Form drafts] Fixed form drafts disappearing after consecutive page refreshes (#10059)by gchust
[Workflow] Fixed subflow nodes remaining pending when the child workflow fails before creating an execution record (#10043)by mytharcher
[Flow engine]
- Fixed an issue where using a local AI agent to configure linkage rules could trigger rendering errors. (#10023)by gchust
- Fixed popup record variables failing to resolve from external NocoBase data sources (#10048)by gchust
[Data source: Main] Prevented invalid many-to-many relationship field configurations from being saved (#10044)by 2013xile
[Collection: Tree] Fixed tree path collection creation to avoid passing internal field model metadata into collection options. (#10035)by cgyrock
[Template print] Fixed template print permission checks so hidden fields and records outside the current role's view scope are not rendered.by jiannx
[Workflow: Approval]
- Allow string type of assignee ID to be addedby mytharcher
- Fix approval form fields becoming single-column in print previewby zhangzhonghe
- Fix the issue where fields in disabled approval subtables can still be editedby zhangzhonghe

v2.2.0-beta.10

Release date: 2026-07-09

🎉 New Features

[AI employees]
- Add OrcaRouter as an LLM provider (#10003)by jinhaosong-source
- Added structured AI usage records for usage statistics (#10004)by 2013xile

🚀 Improvements

[Workflow] Remove arithmetic operators for condition node (#10019)by mytharcher
[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

🐛 Bug Fixes

[client-v2]
- Fix association fields showing the default operator setting in filter forms (#10025)by zhangzhonghe
- Fix mobile popup spacing for table quick edit and select fields (#10020)by zhangzhonghe
- Fixed an issue where association field default values in filter forms could not be cleared. (#10022)by gchust
- Fixed stale linkage field states when switching records in runtime edit popups. (#10010)by katherinehhh
- Fixed an issue where Quick Edit could fail to switch dropdown options when navigating between pages. (#10007)by gchust
- Fixed Vditor asset loading in production by resolving plugin CDN paths from the effective webpack public path. (#10008)by chenos
[cli] Fixed NocoBase CLI default value issues for image registry fallback, built-in database images, env info display, and prompt initialization. (#10027)by chenos
[flow-engine] Fixed an issue where popup configuration became inconsistent when toggling design modes. (#10005)by gchust
[Data visualization] Fixed chart click interactions that could stop working after chart rerendering (#10031)by 2013xile
[AI employees] Fix unnecessary login-required requests on V2 public form pages (#10013)by zhangzhonghe
[Authentication] Fix the issue where reset password links open the sign-in page (#10006)by zhangzhonghe
[Data source manager] Hide the historical attachment field interface from the V2 data table Add field menu. (#10018)by katherinehhh
[File manager]
- Reject active-content filenames during file upload unless the configured storage MIME type rule explicitly allows them. (#10021)by mytharcher Reference: Local storage, Security guide
- Fixed missing Attachment field interface in v2 data table management, and fixed image upload preflight checks for public form file relationship fields. (#10012)by katherinehhh
[Embed NocoBase] Fixed an issue where tokens could be polluted when embedding NocoBase pages. (#9948)by gchust
[Data source: External MariaDB] Fix Add all collections toggle in MySQL, MSSQL, and MariaDB external data source settings.by katherinehhh
[Migration manager] Fixed an issue where migration could leave an app stuck on the repair screenby 2013xile
[App supervisor] Fixed app JWT secret isolation so main app tokens are no longer accepted by sub apps after an independent secret is enabledby 2013xile

develop

v2.2.0-alpha.8

Release date: 2026-07-13

🎉 New Features

[Public forms] In the v1 public form, support creating v2 forms and prohibit creating v1 forms (#10045)by zhangzhonghe

🚀 Improvements

[Workflow] Unsupported workflow v2 canvas nodes now keep the normal node card actions while showing the node type as unsupported. (#10054)by mytharcher
[Flow engine] Support multi portals for ui build apis. (#10072)by gchust
[AI employees] Improved AI employee tool settings, data-query guardrails, relation field querying, and malformed tool call diagnostics. (#10042)by cgyrock
[Collection: SQL] Not user-facing; added client-v2 unit test coverage for migrated plugins. (#9967)by katherinehhh

🐛 Bug Fixes

[client-v2]
- Fix an error in v2 workflow value editors when a collection field is named nodeName. (#10067)by katherinehhh
- Fixed an issue where button linkage rule states in table blocks could become polluted after pagination. (#10038)by gchust
- 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
[app]
- Fixed Redis cache configuration ignoring the dedicated cache URL (#10065)by 2013xile
- Fix lazy-loaded assets using an external script URL when CDN_BASE_URL is empty. (#10052)by Molunerfinn
[server] Fixed custom portals missing when multi-application plugins are disabled (#10055)by 2013xile
[flow-engine]
- Fixed an issue where users could type extra text after selecting a variable in single-value variable inputs. (#10050)by katherinehhh
- Fixed an issue where overriding ctx.api in a JS block could cause a Maximum call stack size exceeded error. (#10051)by gchust
[Workflow: Delay node]
- Fix delay node duration input and prevent values below the minimum from being saved. (#10056)by Molunerfinn
- Prevented delay nodes from accepting numeric durations less than 1 through the API (#10057)by mytharcher
[Workflow]
- Fixed subflow nodes remaining pending when the child workflow fails before creating an execution record (#10043)by mytharcher
- Fixed manual workflow execution returning an error when a valid request does not start an execution. (#10049)by mytharcher
[Data source: Main] Prevented invalid many-to-many relationship field configurations from being saved (#10044)by 2013xile
[Flow engine] Fixed popup record variables failing to resolve from external NocoBase data sources (#10048)by gchust
[Form drafts] Fixed form drafts disappearing after consecutive page refreshes (#10059)by gchust
[Workflow: Aggregate node] Fix validation rule to allow null filter (#10053)by mytharcher
[Redis worker ID allocator]
- Restored standalone startup without Redis worker ID configurationby 2013xile
- Improved Redis worker ID isolation and failure diagnosticsby 2013xile
[plugin-service-platform] Restored licensed plugin downloads from the service platform.by jiannx
[Template print] Fixed template print permission checks so hidden fields and records outside the current role's view scope are not rendered.by jiannx
[Workflow: Approval]
- Fix v2 approval subtables not displaying correctly in detailsby zhangzhonghe
- Fix empty approval interfaces and fixed assignee IDsby zhangzhonghe
- Fix the issue where fields in disabled approval subtables can still be editedby zhangzhonghe
- Allow string type of assignee ID to be addedby mytharcher
- Fix approval form fields becoming single-column in print previewby zhangzhonghe
- Close the Apply new drawer when opening an approval formby zhangzhonghe
- Fix missing approval data on approval task cardsby zhangzhonghe

v2.2.0-alpha.7

Release date: 2026-07-09

🎉 New Features

[AI employees]
- Add OrcaRouter as an LLM provider (#10003)by jinhaosong-source
- Added structured AI usage records for usage statistics (#10004)by 2013xile
[Workflow: Approval] Add approval initiation and todo blocks for v2 pagesby zhangzhonghe

🚀 Improvements

[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
[AI employees] Improved AI employee web search to reduce unnecessary model reasoning and better use provider-specific thinking controls. (#9996)by cgyrock
[Data visualization] Improved chart event scripts so custom event handlers can clean up safely (#10034)by 2013xile
[Workflow] Remove arithmetic operators for condition node (#10019)by mytharcher
[Data source manager] Hide deprecated v2 main data source collection templates from the create collection menu. (#10009)by katherinehhh
[Block: Comment] Improved comment submit actions and fixed related comment/user form submission issues. (#10002)by jiannx

🐛 Bug Fixes

[client-v2]
- Fixed client runtime asset base URL normalization when __webpack_public_path__ is injected without a trailing slash, and added coverage for that edge case. (#10040)by chenos
- Fixed v2 ScanInput recognition for Safari QR images selected from the upload path. (#10011)by katherinehhh
- Fix association fields showing the default operator setting in filter forms (#10025)by zhangzhonghe
- Fix mobile popup spacing for table quick edit and select fields (#10020)by zhangzhonghe
- Fixed an issue where Quick Edit could fail to switch dropdown options when navigating between pages. (#10007)by gchust
- Fixed Vditor asset loading in production by resolving plugin CDN paths from the effective webpack public path. (#10008)by chenos
- Fixed stale linkage field states when switching records in runtime edit popups. (#10010)by katherinehhh
- Fixed an issue where association field default values in filter forms could not be cleared. (#10022)by gchust
- Fixed an issue where v2 workflow assigned fields could still be edited in read-only executed workflow versions. (#10014)by katherinehhh
[cli] Fixed NocoBase CLI default value issues for image registry fallback, built-in database images, env info display, and prompt initialization. (#10027)by chenos
[flow-engine] Fixed an issue where popup configuration became inconsistent when toggling design modes. (#10005)by gchust
[Collection: Tree] Fixed tree path collection creation to avoid passing internal field model metadata into collection options. (#10035)by cgyrock
[Public forms] Fix the issue where public forms can still be configured when UI Editor is off (#10036)by zhangzhonghe
[Flow engine] Fixed an issue where using a local AI agent to configure linkage rules could trigger rendering errors. (#10023)by gchust
[Authentication] Fix the issue where reset password links open the sign-in page (#10006)by zhangzhonghe
[Data visualization] Fixed chart click interactions that could stop working after chart rerendering (#10031)by 2013xile
[Workflow]
- 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 untranslated workflow result labels and oversized CC configuration dialogs (#9977)by zhangzhonghe
- Fix display and detail loading issues in the workflow v2 task center (#10001)by zhangzhonghe
[Data source manager] Hide the historical attachment field interface from the V2 data table Add field menu. (#10018)by katherinehhh
[File manager]
- Reject active-content filenames during file upload unless the configured storage MIME type rule explicitly allows them. (#10021)by mytharcher Reference: Local storage, Security guide
- Reject active-content filenames during file upload unless the configured storage MIME type rule explicitly allows them. (#9994)by mytharcher Reference: Local storage, Security guide
- Fixed missing Attachment field interface in v2 data table management, and fixed image upload preflight checks for public form file relationship fields. (#10012)by katherinehhh
[Embed NocoBase] Fixed an issue where tokens could be polluted when embedding NocoBase pages. (#9948)by gchust
[AI employees] Fix unnecessary login-required requests on V2 public form pages (#10013)by zhangzhonghe
[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 MariaDB] Fix Add all collections toggle in MySQL, MSSQL, and MariaDB external data source settings.by katherinehhh
[plugin-service-platform] Disabled the service platform plugin download endpoint.by jiannx
[Workflow: Subflow] Fixed workflow title search in the subflow node configuration selector.by mytharcher
[Migration manager] Fixed an issue where migration could leave an app stuck on the repair screenby 2013xile
[Workflow: Approval]
- Fix approval assignee sorting and hide unsupported legacy configuration entriesby zhangzhonghe
- Fix the error when configuring approval workflow conditionsby zhangzhonghe
- Fix missing processed approval details in v2 task detail popupsby zhangzhonghe
- Fix approval task form and action issues in the workflow v2 task centerby zhangzhonghe
[App supervisor] Fixed app JWT secret isolation so main app tokens are no longer accepted by sub apps after an independent secret is enabledby 2013xile

Build an Interactive Operations Dashboard with NocoBase

NocoBase — Fri, 10 Jul 2026 07:28:47 +0000

Originally published at https://www.nocobase.com/en/blog/build-interactive-operations-dashboard-with-nocobase

This article uses an operations dashboard for a ticketing system as an example. It shows how to combine NocoBase chart blocks, filter blocks, and JS blocks to build a data dashboard that supports linked filters, chart drilldowns, and custom styling.

Although the example comes from a ticketing scenario, the same approach also applies to CRM, equipment maintenance, project management, approval workflows, customer success, and other business systems.

💡 The point of this article is not to show how to write a large dashboard with a JS block. Instead, it explains how to combine NocoBase native blocks with JS blocks: native blocks handle standard capabilities, while JS blocks fill in the personalized experience.

Scenario Goal

We want to build an Operations dashboard that helps operations or service teams quickly understand the current workload:

How many tickets are still open
Which tickets have SLA risks
How new ticket volume is trending
How tickets are distributed by status and priority
How to view matching records after clicking a chart

The page can be roughly divided into four layers:

Top filter area: time, service group, request type, priority, and SLA status
KPI area: Open backlog, Unassigned, SLA warning, and more
Chart analysis area: trends, status distribution, SLA distribution, and priority mix
Drilldown detail area: show matching records after a chart click

Start with the Right Building Approach

When building a data dashboard, it is easy to turn the problem into a binary choice.

Either you use only NocoBase native blocks, which are easy to configure but may feel less flexible in styling and interaction; or you write a large JS block and control queries, charts, filters, and drilldowns yourself, which means losing much of the convenience that low-code configuration provides.

A better approach is to combine the two.

In this Operations dashboard, we do not write the entire page as one large JS dashboard. Instead, we split responsibilities:

The top filters use NocoBase’s built-in filter block.
Trend charts, status distribution, and SLA distribution use native chart blocks.
KPI cards and drilldown details use JS blocks.
The filter block affects both chart blocks and JS blocks.
After a chart click, the drilldown condition is passed to the JS detail block below.

The benefit is clear: standard statistics and filtering still keep NocoBase’s configuration capabilities, while personalized display and complex interactions are handled by JS blocks. The page is neither “configuration only” nor “all code.” Configuration and code each handle what they are good at.

1. How to Customize Chart Block Styles

In a NocoBase chart block, you can first define the aggregation logic with Query builder, and then adjust the style with a custom ECharts option.

Using “ticket status statistics” as an example, Query builder can be configured as follows:

Data table: tickets
Metric: id count, alias ticketCount
Dimension: status

The key point is that when customizing the style, you do not need to rewrite the query. You only need to process the chart display based on ctx.data.objects.

const rows = Array.isArray(ctx.data?.objects) ? ctx.data.objects : [];

This line reads the chart query result. Then define the status labels and colors:

const labels = {
  new: ctx.t('New'),
  open: ctx.t('Open'),
  pending_customer: ctx.t('Pending customer'),
  resolved: ctx.t('Resolved'),
  closed: ctx.t('Closed'),
};

const colors = {
  new: '#1677ff',
  open: '#22a06b',
  pending_customer: '#f59f00',
  resolved: '#13c2c2',
  closed: '#8c8c8c',
};

It is recommended to use ctx.t() for all visible text so that multilingual support can be added later.

When generating chart data, you can attach drilldown information to each chart data point:

const data = rows.map((row) => ({
  value: Number(row.ticketCount || 0),
  itemStyle: {
    color: colors[row.status] || '#8c8c8c',
    borderRadius: [6, 6, 0, 0],
  },
  ticketingDrilldown: {
    label: ctx.t('Status') + ': ' + (labels[row.status] || row.status),
    filter: { status: { $eq: row.status } },
  },
}));

The most important part here is ticketingDrilldown. It is not a standard ECharts field. It is business context that we put into the data ourselves, and it will be used later when the user clicks the chart.

Finally, return the ECharts option:

return {
  grid: { top: 28, right: 22, bottom: 48, left: 42 },
  tooltip: { trigger: 'axis', axisPointer: { type: 'shadow' } },
  xAxis: {
    type: 'category',
    data: rows.map((row) => labels[row.status] || row.status),
  },
  yAxis: {
    type: 'value',
    minInterval: 1,
  },
  series: [
    {
      name: ctx.t('Tickets'),
      type: 'bar',
      barWidth: 36,
      data,
    },
  ],
};

The core idea of this part is:

Query builder is responsible for statistical data.
Custom option is responsible for visual expression.
Custom fields carry drilldown context.

2. Make the System Filter Block the Observation Scope for the Whole Page

The filter area in an operations dashboard should not be an isolated form. It represents the current observation scope of the entire page.

For example, when a user selects a service group, a request type, and a creation time range, the KPI cards, trend chart, status distribution, and drilldown details should all be displayed under the same conditions. Otherwise, numbers from different blocks may conflict with each other, making it hard for users to know which result belongs to the current scope.

Here, we directly use NocoBase’s built-in filter block instead of writing a custom filter component. The native filter block can be naturally bound to chart blocks, allowing the Chart block to continue using Query builder, permissions, refresh, and filtering mechanisms.

The top Dashboard scope can include these filter fields:

Created at
Service group
Request type
Priority
SLA status

For JS blocks, you only need to read the same set of filter conditions in code and convert them into a query filter. This allows KPI cards and drilldown details to stay consistent with native charts.

The filter combination can be wrapped as a small function:

function combineFilters(...filters) {
  const parts = filters.filter(Boolean);
  if (!parts.length) return undefined;
  if (parts.length === 1) return parts[0];
  return { $and: parts };
}

Count records by filter condition:

async function countTickets(filter) {
  const resource = ctx.makeResource('MultiRecordResource');
  resource.setResourceName('tickets');
  resource.setPageSize(1);

  if (filter) {
    resource.setFilter(filter);
  }

  await resource.refresh();

  const meta = resource.getMeta?.() || {};
  return Number(meta.count || meta.total || 0);
}

The key lines are:

resource.setFilter(filter);
await resource.refresh();

JS blocks query business data through resource instead of directly writing SQL. This makes it easier to stay aligned with NocoBase permissions, data sources, and page runtime behavior.

3. Use JS Blocks to Display KPI Cards

KPI cards are better suited to JS blocks, because a KPI is usually not a single query. It is often a combination of several business metrics, such as unfinished tickets, unassigned tickets, SLA warning, SLA breached, new tickets, and resolved tickets.

A JS block can re-query data according to the current filter scope and render the results as statistic cards.

const { Card, Col, Row, Statistic, Tag } = ctx.libs.antd;

const scopeFilter = getDashboardScopeFilter();

const openBacklog = await countTickets(
  combineFilters(scopeFilter, {
    status: { $notIn: ['resolved', 'closed', 'cancelled'] },
  }),
);

ctx.render(
  <Row gutter={[12, 12]}>
    <Col span={6}>
      <Card size="small">
        <Tag color="blue">{ctx.t('Active')}</Tag>
        <Statistic title={ctx.t('Open backlog')} value={openBacklog} />
      </Card>
    </Col>
  </Row>,
);

The key points for JS blocks are:

Use ctx.makeResource() to query data.
Use ctx.libs.antd to render the UI.
Use ctx.render() to output content.
Re-render the JS block after filters change.

On a real page, filter and reset buttons can be configured with event flows. After they complete the native filter action, they can also refresh the KPI JS block and the drilldown JS block. This way, one click updates both the charts and the custom content under the same scope.

4. Link Chart Blocks with a JS Block for Drilldown

Chart drilldown is a very useful dashboard interaction.

In a ticketing scenario, when the user clicks the “Status: Open” bar, the detail area below shows all Open tickets. When the user clicks “SLA breached,” the detail area shows all overdue tickets.

The implementation idea is:

Attach ticketingDrilldown to chart data points.
Read the drilldown information from the chart event.
Write the drilldown information into the target JS block context.
Trigger the target JS block to re-render.

The key code in the chart event is shown below. First, locate the drilldown JS block:

const DRILLDOWN_TARGET_UID = 'v7mioopm6rm';

function getDrilldownTarget() {
  if (typeof ctx.getModel === 'function') {
    return ctx.getModel(DRILLDOWN_TARGET_UID);
  }

  const engine = ctx.model?.flowEngine || ctx.model?.context?.flowEngine || ctx.engine;
  return engine?.getModel?.(DRILLDOWN_TARGET_UID);
}

Then write the drilldown condition from the chart click into the target block:

function applyDrilldown(drilldown) {
  if (!drilldown?.filter) return;

  const target = getDrilldownTarget();
  if (!target?.context?.defineProperty) return;

  target.context.defineProperty('ticketingDashboardDrilldown', {
    value: drilldown,
  });

  target.rerender?.();
}

The most important lines are:

target.context.defineProperty('ticketingDashboardDrilldown', { value: drilldown });
target.rerender?.();

The first line passes the drilldown condition to the JS block, and the second line triggers the JS block to refresh.

Finally, bind the chart click event:

const clickHandler = (params) => {
  applyDrilldown(params?.data?.ticketingDrilldown);
};

chart.on('click', clickHandler);

return () => chart.off('click', clickHandler);

It is strongly recommended to return a cleanup function:

return () => chart.off('click', clickHandler);

This cleans up old events when the chart is reconfigured or re-rendered, avoiding duplicate event bindings.

The chart click event code above applies to v2.2.0-beta.10 and later. For earlier versions, refer to:

chart.off('click');
chart.on('click', clickHandler);

5. How the Drilldown JS Block Displays Details

The drilldown JS block reads the ticketingDashboardDrilldown written earlier, and then queries data based on its filter.

const drilldown = ctx.model?.context?.ticketingDashboardDrilldown;

if (!drilldown) {
  ctx.render(
    <Alert
      type="info"
      showIcon
      message={ctx.t('Select a chart segment to inspect matching tickets')}
    />,
  );
  return;
}

If the user has not clicked a chart yet, a prompt is displayed. After a click, tickets are queried according to drilldown.filter:

const resource = ctx.makeResource('MultiRecordResource');
resource.setResourceName('tickets');
resource.setFilter(drilldown.filter);
resource.setPageSize(10);
await resource.refresh();

const rows = resource.getData?.() || [];

Then render the table:

const { Table, Typography } = ctx.libs.antd;

ctx.render(
  <>
    <Typography.Title level={5}>
      {ctx.t('Drilldown')}: {drilldown.label}
    </Typography.Title>

    <Table
      size="small"
      rowKey="id"
      dataSource={rows}
      pagination={false}
      columns={[
        { title: ctx.t('Ticket No'), dataIndex: 'ticketNo' },
        { title: ctx.t('Title'), dataIndex: 'title' },
        { title: ctx.t('Status'), dataIndex: 'status' },
        { title: ctx.t('Priority'), dataIndex: 'priority' },
      ]}
    />
  </>,
);

To clear the drilldown condition, you can refer to:

function clearChartDrilldown() {
  if (ctx.model?.context?.defineProperty) {
    ctx.model.context.defineProperty('ticketingDashboardDrilldown', { value: null });
  }
  if (typeof ctx.model?.rerender === 'function') {
    ctx.model.rerender();
  }
}

The key points here are:

The chart only passes the filter.
The JS block is responsible for querying and displaying details.
The same drilldown block can be reused by clicks from different charts.

Practical Recommendations

1. Do Not Rush to Code the Whole Complex Page

The most important lesson from this page is: do not treat native capabilities and JS capabilities as opposites.

If a capability is already native to NocoBase, such as filtering, chart queries, table display, permission control, use the native block first. This allows you to continue configuring fields, filter conditions, and chart metrics in the interface later.

JS blocks are better for parts that native blocks are not good at, such as combining multiple metrics into KPI cards, applying special card styles, showing custom details after a chart click, or passing business context between different blocks.

In other words, native blocks handle “configurable standard capabilities,” while JS blocks handle “business-specific personalized experiences.” This is the most reusable building approach from this dashboard.

2. Use Chart Block Query Builder First for Simple Statistics

This preserves NocoBase’s standard query, permission, filtering, and refresh capabilities. Only use a custom ECharts option for visual optimization when the default chart style cannot express the business emphasis clearly.

3. Use JS Blocks First for KPI Cards

KPIs usually need multiple queries, condition combinations, and custom layouts, so JS blocks are more flexible. This is especially clear when KPIs need to respond to the same set of system filter conditions.

4. Return Cleanup for Chart Events

Recommended pattern:

const handler = (params) => {
  // handle click
};

chart.on('click', handler);

return () => chart.off('click', handler);

Do not directly use chart.off('click') to clear all click events, because this may accidentally remove listeners used by the chart block or configuration panel.

Let AI Help You Build It

This type of dashboard is very suitable for AI-assisted generation, because it involves data models, statistical definitions, chart styling, and page interactions at the same time. You can give this article to an AI tool and ask questions based on the prompt below.

You can ask:

I am building an operations dashboard for a ticketing system with NocoBase.
Please use the ticketing scenario as an example and help me design an Operations dashboard.

The tickets table contains:
ticketNo, title, status, priority, slaStatus,
requestType, serviceGroup, assignee, createdAt, updatedAt.

The page needs:
1. Top filters: Created at, Service group, Request type, Priority, SLA status.
2. KPI cards: Open backlog, Unassigned, SLA warning, SLA breached, New tickets, Resolved tickets.
3. Charts: Created tickets trend, Ticket status, SLA status, Priority mix.
4. After a chart click, the JS block below displays a matching Ticket drilldown table.
5. The chart style should fit an operations dashboard, with clear colors and a compact layout.
6. All JS text should use ctx.t().
7. Chart events should use chart.on and return a cleanup function.
8. Prefer NocoBase native filter blocks and chart blocks. Use JS blocks only for KPIs, drilldown details, special styling, and cross-block interactions. Do not write the whole page as one large JS block.

Please provide the configuration approach for each block and mark the key JS code.

If you already have a page, you can also ask AI to optimize it:

This is my current NocoBase dashboard design:
The top area is a filter block, the middle area has four charts, and the bottom area has a drilldown JS block.
Please help me optimize it from the perspective of operations staff:
1. Which KPIs should be displayed?
2. Do the charts need to be linked?
3. Which columns should be shown in drilldown details?
4. How should JS blocks and chart events be organized?
5. Which code should be placed in the chart custom option, and which code should be placed in the JS block?

This helps the AI generate content that is closer to real business scenarios instead of isolated code snippets.

If you choose to let AI help you build, back up the project with Backup Manager before you start.

Reference Documentation

What Is AI No-Code? A Practical Guide to No-Code Platforms in the AI Era

NocoBase — Thu, 09 Jul 2026 09:04:41 +0000

Originally published at https://www.nocobase.com/en/blog/what-is-ai-no-code

Introduction

Do you also think no-code belongs to the “pre-AI era”?

Now that AI can write code, generate applications, and automate workflows, do no-code platforms still need to exist?

The answer is yes.

Google Trends shows that search interest in “AI no code” has risen quickly over the past year.

People are not giving up on no-code. They are understanding it in a new way: not just dragging components to build pages, but using AI, natural language, and visual platforms to build applications, automate workflows, and create internal business systems faster.

The problem is that many products can now be called AI no-code.

Lovable, Zapier, and NocoBase all fall under the broader category of AI no-code, but they solve very different problems and suit very different users.

This article will answer two questions:

What is AI no-code?
How do you choose the right AI no-code tool?

What Is AI No-Code?

At the most basic level, AI no-code refers to tools or platforms that combine AI capabilities with no-code development methods. Users do not need to write code from scratch. Instead, they can use natural language, visual configuration, prebuilt components, workflow orchestration, and similar methods to build applications, automate processes, or let AI participate in specific business tasks.

But this definition only explains part of the picture.

Today, “AI no-code” is no longer a product category with clear boundaries. Many tools can be related to AI no-code, but their product logic can be completely different.

No-code platforms are adding AI to help users build pages, forms, data models, and business workflows faster.
Low-code platforms are using AI to help developers generate code, configure APIs, and extend systems.
AI app builders let users generate pages, components, or application prototypes directly from prompts.
AI automation tools connect multiple tools and use AI to summarize, classify, judge, and trigger actions.

These categories also continue to overlap. An AI app builder may offer a database. An automation tool may support simple pages. A no-code platform may connect to AI Agents and workflows.

It can get confusing.

A clearer way to think about it is this: stop asking whether a tool is truly AI no-code or where its category boundary sits.

Instead, ask what problem it helps you solve. Once you look at it this way, the choices become much easier.

Need 1: Build a Working Application Quickly

This is one of the most common needs.

AI can write code quickly and well. If you ask ChatGPT, Claude, or another AI coding tool to “build a customer management page,” they can generate HTML, React components, or even a full block of frontend code.

But the issue is that code is not the same as an application.

After AI generates code, you still need to handle many things yourself:

Put the code into a project.
Configure the development environment.
Manage dependencies and errors.
Connect a database.
Adjust page interactions.
Deploy the application.
Make it accessible for others to test.

For developers, these may be routine tasks. For product managers, designers, founders, and business users, they are still a lot of work.

This is where this type of AI no-code tool becomes valuable.

These tools do more than “generate code.” They combine generation, preview, editing, running, and deployment. Users only need to describe what they want, and the platform can generate the application interface, provide online preview, support interaction changes, and help with deployment.

Typical products include:

v0

UI and Frontend Interface Generation

You can describe the page you want in natural language, and v0 generates the corresponding interface and components. It is useful for quickly creating product interfaces, admin panels, landing pages, or interactive prototypes.

Lovable

Generate a Complete Web App From a Prompt

Lovable does not only focus on pages. It also tries to generate application structure, interaction logic, and basic features, making it suitable for turning a product idea into a working MVP quickly.

Bolt

Generate and Run Full-Stack Applications Online

Users can describe requirements, generate code, install dependencies, run projects, and debug applications in the browser, without first setting up a complex local development environment.

Replit

Develop and Deploy Applications Online

Replit is an online development environment. With AI, it can help users generate code, debug projects, and run and publish applications directly.

Need 2: Build Business Systems That Can Run Long Term

The second major need appears in enterprise scenarios.

The question becomes: Can I use AI and no-code to build a business system that a company can truly use over the long term?

For example:

I want to build a CRM to manage customers, contacts, opportunities, and follow-up records.
I want to build a ticketing system so customer issues can be submitted, assigned, handled, and tracked.
I want to build an approval system for leave requests, reimbursements, procurement, contracts, and other processes.
I want to build an inventory or asset management system where data, status, owners, and operation records are clear and traceable.
I want to build an internal operations system where different roles collaborate in the same system.

The core of this need is: how to combine data, pages, permissions, workflows, and AI capabilities into a business system that can keep running.

This is where enterprise business-system AI no-code platforms are needed.

They usually provide data modeling, page building, permission control, workflows, automation, audit logs, API integration, plugin extension, private deployment, and other capabilities. AI is not a standalone application here. It participates in system building and business operations.

NocoBase

An Open-Source, Self-Hosted, Extensible AI No-Code Platform for Enterprise Business Systems

NocoBase provides the core capabilities needed for enterprise business systems, including data models, page building, permission control, workflows, plugin extension, and private deployment. It gives AI a platform foundation for real business scenarios. AI understands requirements, assists generation, and improves efficiency. NocoBase carries the data, permissions, processes, audits, and long-term iteration.

This is why NocoBase is better suited as a first choice for applying AI in real enterprise scenarios. It does not only give AI a generation entry point. It gives AI a business system foundation that can run for the long term, continue to evolve, keep permissions under control, and protect business data.

Retool

An Internal Tool Builder for Development Teams

Retool can quickly connect databases, APIs, and internal services to build admin panels, data operation interfaces, and enterprise internal tools. It also provides AI-related capabilities for assisted building and automation.

Appsmith

An Open-Source Low-Code Platform for Internal Tools

Like NocoBase, Appsmith is also open source. It is suitable for developers and IT teams building dashboards, admin panels, and internal applications. It supports database and API connections and can also be self-hosted.

Budibase

An Open-Source Platform for Business Applications and Internal Tools

Budibase is suitable for building forms, approvals, operations systems, and internal management tools. It supports data source connections, automation, and self-hosting.

Need 3: Let Multiple Tools Work Together Automatically

After AI appeared, many people assumed automation would become simple.

For example, you can ask AI to summarize emails, extract form information, generate replies, and judge customer intent. Viewed separately, AI can indeed complete these tasks.

But in real work, tasks usually do not happen in isolation.

A customer lead may come from a website form, then need to be synced to a CRM, notify sales, and create a follow-up task.

A user feedback email may need to be summarized by AI, classified by issue type, and assigned to the right team.

A contract or invoice may need key information extracted, written into a spreadsheet or system, and then trigger an approval workflow.

Letting AI participate in a full business process, while different tools work together automatically, is the value of AI workflow automation tools.

These tools are not mainly for generating application pages. They connect different systems, place AI inside workflow nodes, and let data, messages, and tasks move automatically.

Typical products include:

Zapier

Automation Between SaaS Tools

Zapier supports a large number of common applications. It is suitable for connecting tools such as Gmail, Slack, HubSpot, Airtable, and Google Sheets to automate notifications, syncing, task creation, AI processing, and more.

Make

Visual Multi-Step Automation Workflows

Make is suitable for more complex conditional logic, data transformation, and multi-application collaboration. Users can design automation tasks in a flowchart-style interface.

n8n

Self-Hosted and Extensible Workflow Automation

As a popular GitHub project, n8n is suitable for technical teams and enterprise users who need to connect APIs, databases, internal systems, and AI services to build more controllable automation workflows.

Activepieces

Open-Source Automation and Business Process Connections

Activepieces is suitable for teams that want to use open-source solutions to build automation workflows. It can also handle data movement and AI tasks across common SaaS tools.

Need 4: Build AI Applications or AI Agents

The last type of need is to build an AI application directly.

For example:

I want to build an enterprise knowledge-base Q&A bot.
I want to build a RAG application that reads documents and answers questions.
I want to build a customer service Agent that understands user questions and calls tools.
I want to combine multiple models, prompts, knowledge bases, and workflows.

The core of this need is: how to package large model capabilities into a usable AI application.

This is where AI application building platforms and AI Agent platforms become valuable.

They usually provide prompt orchestration, model selection, knowledge base integration, RAG, tool calling, Agent workflows, API publishing, and similar capabilities. Users can build Chatbots, AI Workflows, or Agent applications without writing everything from scratch.

Typical products include:

Dify

LLM Application Development Platform

Dify is suitable for building Chatbots, RAG applications, Agent workflows, and enterprise knowledge-base Q&A. It provides model integration, prompt orchestration, knowledge bases, workflows, and application publishing.

Flowise

Visual Builder for LangChain Applications

Flowise is suitable for developers and AI application teams. It uses a node-based interface to orchestrate LLMs, tools, memory, vector databases, and Agent flows.

LangFlow

Visual AI Workflow and Agent Orchestration

LangFlow is suitable for building complex LLM call chains, RAG workflows, and Agent prototypes. Users can combine AI applications through a component-based approach.

Product Decision Table

The table below lists all products discussed in this article. You can quickly compare their characteristics, open-source status, and best-fit scenarios.

Product	Type	Open Source	Typical Use Cases	Target Users	Core Capabilities
NocoBase	Enterprise business-system AI no-code platform	✅ Open source	CRM, tickets, approvals, inventory, asset management, internal business systems	Enterprise IT, development teams, software agencies, business teams	Data models, page building, permissions, workflows, plugins, self-hosting, AI-assisted building
Retool	Enterprise business-system AI no-code platform	Closed source	Internal tools, admin panels, database operation interfaces	Development teams, enterprise IT	Internal tool building, database connections, component library, workflows, AI features
Appsmith	Enterprise business-system AI no-code platform	✅ Open source	Internal tools, admin panels, data operation apps	Developers, IT teams	Open-source low-code, UI components, database/API connections, self-hosting
Budibase	Enterprise business-system AI no-code platform	✅ Open source	Internal tools, approvals, forms, operations systems	IT teams, SMBs, developers	App building, data source connections, automation, self-hosting
Lovable	AI prototype generation tool	Closed source	MVPs, Web App prototypes, lightweight apps	Founders, product teams, indie developers	Prompt-based app generation, frontend/backend generation, fast deployment
Bolt	AI prototype generation tool	Closed source	Full-stack app generation, demos, small tools	Developers, founders, product teams	Natural-language code generation, online development environment, app preview
Zapier	AI workflow automation tool	Closed source	Cross-SaaS automation, lead routing, notifications, data sync	Operations, marketing, sales, business teams	SaaS integrations, triggers, automation workflows, AI steps
Make	AI workflow automation tool	Closed source	Multi-step automation, data processing, cross-tool workflows	Operations teams, automation specialists, growth teams	Visual workflow orchestration, API integration, conditional logic
n8n	AI workflow automation tool	✅ Open source	Self-hosted automation, AI workflows, system integration	Technical teams, automation engineers, enterprise IT	Workflow orchestration, self-hosting, API integration, AI nodes
Activepieces	AI workflow automation tool	✅ Open source	Open-source automation, business process connections, AI automation	Technical teams, operations teams, SMBs	Visual automation, open-source deployment, app connectors
Dify	AI application / Agent platform	✅ Open source	Chatbots, RAG applications, AI Agents, enterprise knowledge-base Q&A	AI application developers, technical teams, enterprise IT	LLM application development, prompt orchestration, RAG, Agent workflows
Flowise	AI application / Agent platform	✅ Open source	Visual LangChain orchestration, RAG, Agent prototypes	AI developers, technical teams	Visual AI flows, LangChain integration, node-based orchestration
LangFlow	AI application / Agent platform	✅ Open source	AI Workflow, RAG, model call flows	AI engineers, developers, research teams	Visual LLM orchestration, component-based flows, Agent building

FAQ

1. What Is the Difference Between AI No-Code and Traditional No-Code?

Traditional no-code mainly relies on drag-and-drop interfaces, forms, components, and visual configuration. AI no-code further introduces natural language, AI generation, intelligent automation, and AI Agent capabilities.

However, AI no-code is not simply adding an AI button to a traditional no-code platform. Valuable AI no-code tools need to bring AI into specific application building, business processes, and data processing scenarios.

2. What Is the Difference Between an AI App Builder and an AI No-Code Platform?

AI app builders focus more on quickly generating application prototypes, while AI no-code platforms focus more on building applications or business systems that can be used continuously.

AI app builders such as v0, Lovable, and Bolt are strong in generation speed, making them suitable for MVPs, demos, product prototypes, and lightweight applications.

AI no-code platforms such as NocoBase pay more attention to data models, pages, permissions, workflows, audit logs, plugin extension, and private deployment, making them more suitable for long-term enterprise use.

So the key is whether you need a prototype or a real system that supports business operations.

3. How Should Enterprises Choose AI No-Code Tools?

Enterprises should first clarify their goal: are they building a prototype, automation, an AI Agent, or a long-running business system?

If the goal is to build a system that the enterprise will use long term, focus on data models, permission control, workflows, audit logs, extensibility, private deployment, and security.

4. What Are the Advantages of Open-Source AI No-Code Tools?

Open-source AI no-code tools offer more control, extensibility, and self-hosting capabilities, especially for scenarios involving enterprise data, permissions, workflows, and long-term maintenance.

In AI scenarios, tools often touch customer data, business processes, internal knowledge bases, ticket content, approval records, and employee information. Enterprises care more about where data is stored, how models are called, whether the system can be privately deployed, and whether it can be extended or migrated in the future.

The closer a tool gets to core enterprise business systems, the more important open source, self-hosting, and extensibility become.

5. What Type of AI No-Code Tool Is NocoBase?

NocoBase is an enterprise business-system AI no-code platform, suitable for building long-running internal tools and business systems.

It can be used to build real business systems such as CRM, ticketing, approvals, inventory, asset management, expense reimbursement, and customer portals.

NocoBase is better suited for teams that want to apply AI to real enterprise scenarios.

Conclusion

Back to the question at the beginning: Does no-code still matter after AI?

The clearer answer is: no-code has not been replaced by AI. It has entered a new stage because of AI.

AI makes software building faster, but enterprises still need systems that are maintainable, extensible, permission-controlled, secure, and able to run over the long term.

That is the real value of no-code platforms in the AI era.

If this article helped you better understand AI no-code, feel free to share it with friends who are choosing AI tools, no-code platforms, or internal business system solutions.

Related reading:

Weekly Updates: Add Mistral AI as an LLM Provider

NocoBase — Tue, 07 Jul 2026 08:35: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.1.19

Release date: 2026-07-03

🐛 Bug Fixes

[cli] Fixed revision creation events failing on RabbitMQ brokers that reject : and @ in queue names. (#9989) by cgyrock
[client-v2]
- Fixed iframe sanitization for v2 Markdown rendering and editing. (#9986) by katherinehhh
- Fixed routed popup creation forms losing prefilled field values such as Calendar V2 start and end dates. (#9874) by jiannx
- Fixed V2 table data scope filters so missing URL query parameters no longer block table data queries. (#9869) by jiannx
- Fixed an issue where multiline text field values could not be set via ctx.setFormValues. (#9959) by gchust
[AI employees]
- Fixed AI checkpoint cleanup failures in underscored database environments. (#9982) by cgyrock
- Fixed AI employee workflow nodes failing to resume correctly in loops after a previous AI employee tool call. (#9980) by cgyrock
[File manager] Hidden the file manager attachments list API and return 404 when it is requested. (#9978) by mytharcher
[Workflow] Fixed an issue where workflow execution node results could remain stuck in a loading state. (#9991) by mytharcher
[Backup manager]
- Fixed PostgreSQL and Kingbase backup restore command execution when paths or arguments contain spaces or special characters. (#9946) by cgyrock
- Fixed an issue where newly created backup files could not be uploaded to cloud storage. (#9981) by gchust
[Data visualization] Fixed an issue where chart blocks would trigger unnecessary refreshes when closing a popup. (#9970) by gchust
[UI templates] Fixed an issue where the field template menu was incorrectly displayed in subforms. (#9960) by gchust
[Mobile (deprecated)] Fix responsive v1 admin pages so view actions open as subpages and select fields use mobile popups (#9974) by zhangzhonghe
[Version control] Fixed version-control revision creation on RabbitMQ brokers that reject : and @ in queue names. by cgyrock
[Workflow: Approval] Fix the error that may occur when opening approval details without configuration permissions by zhangzhonghe

v2.1.18

Release date: 2026-07-02

🚀 Improvements

[cli] Support manual Nginx/Caddy proxy config generation, allow Docker deployments without bundled Nginx, and align proxy and CDN-related runtime configuration. (#9943) by chenos
[undefined] Clarified the security guidance for PDF previews using external storage. (#9901) by mytharcher Reference: File Preview
[utils] Added warnings for server-side outbound requests that target potential SSRF-risk addresses when SERVER_REQUEST_WHITELIST is not configured. (#9966) by mytharcher Reference: Environment Variables, Global Environment Variables
[AI: Knowledge base] Added ZIP filename encoding options for knowledge base document uploads to avoid garbled filenames in ZIP archives created with non-UTF-8 encodings. by cgyrock

🐛 Bug Fixes

[client-v2] Fix the issue where route subpages are blank or use incorrect spacing after refresh (#9961) by zhangzhonghe
[Workflow] Reduced unnecessary workflow dispatcher DB fetch retries under concurrent queue processing. (#9953) by mytharcher
[Action: Export records] Fixed XLSX exports so text-like field values that start with formula characters are escaped before being opened in Excel. (#9973) by mytharcher
[AI employees] Fixed LLM providers falling back to their default Base URL when the custom Base URL field is cleared. (#9958) by cgyrock
[Data source: External NocoBase] Fixed external NocoBase attachment uploads and updates in attachment fields by 2013xile

v2.1.17

Release date: 2026-07-01

🐛 Bug Fixes

[flow-engine] Fixed an issue where ctx.auth.user would not update after switching users. (#9964) by gchust
[Mobile (deprecated)] Fix the issue where mobile pages and public forms cannot be scrolled on mobile devices (#9898) by zhangzhonghe

v2.1.15

Release date: 2026-06-30

🐛 Bug Fixes

[undefined] Fixed the Version control documentation in non-Chinese languages so the Professional Edition label is displayed. (#9944) by cgyrock
[AI employees] Fixed workflow AI employee tasks failing after repeated tool calls reached the graph recursion limit. (#9945) by cgyrock
[Action: Custom request] Fixed custom requests allowing runtime options to override the saved request target. (#9904) by mytharcher
[Data source manager] Fixed v2 collection field management so template-protected fields cannot be deleted and inherited fields support view / override behavior consistent with v1. (#9940) by katherinehhh
[Migration manager] Fixed garbled text that could occur when migrating MySQL data with non-ASCII content by 2013xile
[Workflow: Approval] Fix the error when adding Original application content to approval nodes by zhangzhonghe

v2.1.14

Release date: 2026-06-29

🎉 New Features

[AI employees] Added Mistral AI as an LLM provider for AI services. (#9925) by cgyrock

🚀 Improvements

[cli] support OAuth device authorization flow (#9922) by chenos

🐛 Bug Fixes

[client-v2]
- Fixed long selected labels in record select fields so they truncate cleanly without squeezing the select control. (#9939) by katherinehhh
- Fixed table datetime columns losing their configured time display after pagination or refresh. (#9935) by katherinehhh
[Users] Removed the default password from the add-user form in Users & Permissions. (#9915) by jiannx
[Data source: External NocoBase] Fixed NocoBase external data sources failing to load when connection options include runtime objects by 2013xile
[Record history] Fixed external NocoBase data source loading failure when record history is enabled by 2013xile
[App supervisor] Fixed the app supervisor Applications tab registration in Client V2 by 2013xile

v2.2.0-beta.8

Release date: 2026-06-29

🚀 Improvements

[cli] Support OAuth device authorization flow (#9922) by chenos
[client-v2] Support configure js block should be wrapped by block card. (#9897) by gchust
[flow-engine] Automatically refreshed related data blocks when RunJS closes a popup after updating data through resource APIs (#9873) by gchust
[Form drafts] Migrate plugin form drafts to client v2. (#9910) by gchust

🐛 Bug Fixes

[client-v2]
- Fixed link actions becoming invisible on mobile embedded pages when icon-only mode is enabled but no icon is configured. (#9921) by katherinehhh
- Fixed a brief no-pages prompt flash when refreshing in UI Editor mode. (#9918) by katherinehhh
- Fixed v2 form submit success redirects so they can reference the saved response record. (#9907) 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 v2 table row action buttons changing row height. (#9866) by jiannx
- Fixed table blocks failing when a configured drag sorting field has been deleted, and allowed clearing the drag sorting field setting. (#9867) by jiannx
[flow-engine]
- Fix the issue where mobile popups with long content cannot scroll (#9871) by zhangzhonghe
- Fixed an issue where some parameters of ctx.openView in RunJS would not take effect. (#9883) by gchust
[cli] support pnpm and yarn global self update (#9912) by chenos
[client] Corrected several copy and typo issues across locales, related UI text, and documentation. (#9905) by Molunerfinn
[Flow engine] Fixed the issue where mobile page can't be created by flow surface api. (#9911) by gchust
[AI employees]
- Fixed the AI datasource card list so it adapts responsively to different viewport widths. (#9924) by cgyrock
- Fixed AI employee chat failures caused by replaying malformed tool calls. (#9900) by cgyrock
[Backup manager] Fixed inconsistent bold labels on the v2 Backup manager settings page. (#9908) by katherinehhh
[Block: iframe] Fixed 403 errors for normal users when viewing v2 iframe blocks in HTML mode. (#9889) by jiannx
[Data source: External NocoBase] Fixed NocoBase external data sources failing to load when connection options include runtime objects by 2013xile
[AI: Knowledge base] Fixed layout overflow in version control and knowledge base document lists when content or viewport size is constrained. by cgyrock
[Migration manager] Fixed migration rules for database-synced collections by 2013xile
[Record history]
- Fixed an issue where record history could fail to save changes for some collections by 2013xile
- Fixed external NocoBase data source loading failure when record history is enabled by 2013xile
[App supervisor] Fixed the app supervisor Applications tab registration in Client V2 by 2013xile
[WeCom] Fixed a blank flash when switching route menu items with the WeCom plugin enabled in Client V2 by 2013xile

develop

v2.2.0-alpha.6

Release date: 2026-07-05

🚀 Improvements

[cli] Refactor CLI setup startup to reuse nb app start, normalize API base path redirects, persist shared env proxy defaults, and rebuild Docker proxy containers when published ports change. (#9997) by chenos

v2.2.0-alpha.5

Release date: 2026-07-04

🎉 New Features

[client-v2] Added configurable App and Portal entry support for V2 action panels and the left-top app switcher. (#9893) by katherinehhh
[Portal manager] Added configurable App and Portal entries for the V2 action panel and app switcher. by katherinehhh

🚀 Improvements

[cli] Improved the Docker CLI setup by supporting configurable default NocoBase image registry/variant, fixing proxy and no-nginx image port compatibility, and adding Docker Nginx/Caddy installation guides. (#9972) by chenos
[undefined]
- Clarified the security guidance for PDF previews using external storage. (#9901) by mytharcher Reference: File Preview
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9942) by sembaev-a-a
[utils] Added warnings for server-side outbound requests that target potential SSRF-risk addresses when SERVER_REQUEST_WHITELIST is not configured. (#9966) by mytharcher
Reference: Environment Variables, Global Environment Variables
[AI employees]
- 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
[Data source manager] Display unsupported external data source fields in V2 Configure fields, and align backup restore form label styles. (#9983) by katherinehhh
[Users] Improve client-v2 test coverage for the users plugin. (#9975) by jiannx
[AI: Knowledge base]
- Added ZIP filename encoding options for knowledge base document uploads to avoid garbled filenames in ZIP archives created with non-UTF-8 encodings. 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
[Email manager] 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

🐛 Bug Fixes

[cli] Fixed revision creation events failing on RabbitMQ brokers that reject : and @ in queue names. (#9989) by cgyrock
[client-v2]
- Fixed iframe sanitization for v2 Markdown rendering and editing. (#9986) by katherinehhh
- Fixed V2 table data scope filters so missing URL query parameters no longer block table data queries. (#9869) by jiannx
- Fix the issue where opening an empty V2 Group menu item shows 404 (#9896) by zhangzhonghe
- Fixed an issue where multiline text field values could not be set via ctx.setFormValues. (#9959) by gchust
- Fixed routed popup creation forms losing prefilled field values such as Calendar V2 start and end dates. (#9874) by jiannx
- Fix the issue where route subpages are blank or use incorrect spacing after refresh (#9961) by zhangzhonghe
[Action: Export records]
- Fixed a crash when dragging v2 exportable fields after selecting relation fields. (#9995) by katherinehhh
- Fixed XLSX exports so text-like field values that start with formula characters are escaped before being opened in Excel. (#9973) by mytharcher
[Workflow]
- Fixed an issue where workflow execution node results could remain stuck in a loading state. (#9991) by mytharcher
- Reduced unnecessary workflow dispatcher DB fetch retries under concurrent queue processing. (#9953) by mytharcher
[Backup manager]
- Fixed an issue where newly created backup files could not be uploaded to cloud storage. (#9981) by gchust
- Fixed PostgreSQL and Kingbase backup restore command execution when paths or arguments contain spaces or special characters. (#9946) by cgyrock
[AI employees]
- Fixed AI employee workflow nodes failing to resume correctly in loops after a previous AI employee tool call. (#9980) by cgyrock
- Fixed AI checkpoint cleanup failures in underscored database environments. (#9982) by cgyrock
[UI templates] Fixed an issue where the field template menu was incorrectly displayed in subforms. (#9960) by gchust
[File manager] Hidden the file manager attachments list API and return 404 when it is requested. (#9978) by mytharcher
[Block: Comment] Adjusted the default action order for new Comment blocks. (#9976) by jiannx
[Data visualization] Fixed an issue where chart blocks would trigger unnecessary refreshes when closing a popup. (#9970) by gchust
[Mobile (deprecated)] Fix responsive v1 admin pages so view actions open as subpages and select fields use mobile popups (#9974) by zhangzhonghe
[Version control] Fixed version-control revision creation on RabbitMQ brokers that reject : and @ in queue names. by cgyrock
[Data source: External NocoBase] Fixed external NocoBase attachment uploads and updates in attachment fields by 2013xile
[Workflow: Approval] Fix the error that may occur when opening approval details without configuration permissions by zhangzhonghe

v2.2.0-alpha.4

Release date: 2026-07-01

🎉 New Features

[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
[AI employees] Added Mistral AI as an LLM provider for AI services. (#9925) by cgyrock
[Record history] Added client v2 support for the record history plugin. by jiannx

🚀 Improvements

[cli] Support manual Nginx/Caddy proxy config generation, allow Docker deployments without bundled Nginx, and align proxy and CDN-related runtime configuration. (#9943) by chenos
[Workflow: JavaScript] Aligned v2 workflow request and mailer node configuration fields with legacy layout and attachment variable behavior. (#9952) 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
[Block: Comment] Added the new comment block plugin to the NocoBase preset and marked the legacy comments plugin as deprecated. (#9936) by jiannx
[Logger] Added the Logger settings page to the client v2 runtime. (#9933) by jiannx
[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

🐛 Bug Fixes

[flow-engine] Fixed an issue where ctx.auth.user would not update after switching users. (#9964) by gchust
[client-v2]
- 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 table datetime columns losing their configured time display after pagination or refresh. (#9935) by katherinehhh
- Fixed long selected labels in record select fields so they truncate cleanly without squeezing the select control. (#9939) by katherinehhh
- Fixed V2 admin group routes showing 404 when the group has no available child menu page. (#9932) by katherinehhh
[undefined] Fixed the Version control documentation in non-Chinese languages so the Professional Edition label is displayed. (#9944) by cgyrock
[AI employees]
- Fixed LLM providers falling back to their default Base URL when the custom Base URL field is cleared. (#9958) by cgyrock
- Fixed workflow AI employee tasks failing after repeated tool calls reached the graph recursion limit. (#9945) by cgyrock
[Action: Custom request] Fixed custom requests allowing runtime options to override the saved request target. (#9904) by mytharcher
[Mobile (deprecated)] Fix the issue where mobile pages and public forms cannot be scrolled on mobile devices (#9898) by zhangzhonghe
[Notification manager] Fix incorrect workflow variables shown in CC configuration (#9937) by zhangzhonghe
[Workflow]
- 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
[Data source manager] Fixed v2 collection field management so template-protected fields cannot be deleted and inherited fields support view / override behavior consistent with v1. (#9940) by katherinehhh
[Authentication] Fixed incorrect redirects after SSO login in v2 sub applications (#9927) by 2013xile
[Users] Removed the default password from the add-user form in Users & Permissions. (#9915) by jiannx
[Flow engine] Fixed the issue where mobile page can't be created by flow surface api. (#9911) by gchust
[App SSO] Fixed incorrect App SSO redirects in v2 sub applications by 2013xile
[AI: Knowledge base] Fixed layout overflow in version control and knowledge base document lists when content or viewport size is constrained. by cgyrock
[Data source: External NocoBase] Fixed NocoBase external data sources failing to load when connection options include runtime objects by 2013xile
[Migration manager] Fixed garbled text that could occur when migrating MySQL data with non-ASCII content by 2013xile
[Record history] Fixed external NocoBase data source loading failure when record history is enabled by 2013xile
[Workflow: Approval]
- Fix the error when opening CC node settings by zhangzhonghe
- Fix the error when adding Original application content to approval nodes by zhangzhonghe
- Fix the issue where approval tables appear in the block data source list by zhangzhonghe
- Fix issues involved by migrating to client v2 by mytharcher
[App supervisor]
- Fixed app visit links losing the v2 path in sub applications by 2013xile
- Fixed the app supervisor Applications tab registration in Client V2 by 2013xile