@nocobase/plugin-flow-engine 2.1.0-beta.17 → 2.1.0-beta.19

package/dist/server/flow-surfaces/support-matrix.d.ts

@@ -6,7 +6,7 @@
  * This project is dual-licensed under AGPL-3.0 and NocoBase Commercial License.
  * For more information, please refer to: https://www.nocobase.com/agreement.
  */
-export type FormalFlowSurfaceBlockKey = 'js-block' | 'table' | 'calendar' | 'create-form' | 'edit-form' | 'details' | 'filter-form' | 'list' | 'grid-card' | 'markdown' | 'iframe' | 'map' | 'chart' | 'comments' | 'action-panel';
+export type FormalFlowSurfaceBlockKey = 'js-block' | 'table' | 'calendar' | 'kanban' | 'create-form' | 'edit-form' | 'details' | 'filter-form' | 'list' | 'grid-card' | 'markdown' | 'iframe' | 'map' | 'chart' | 'comments' | 'action-panel';
 export type FlowSurfaceBlockSupportEntry = {
     key: string;
     formalKey?: FormalFlowSurfaceBlockKey;

package/dist/server/flow-surfaces/support-matrix.js

@@ -72,6 +72,18 @@ const FLOW_SURFACE_BLOCK_SUPPORT_MATRIX = [
     readbackSupported: true,
     createSupported: true
   },
+  {
+    key: "kanban",
+    formalKey: "kanban",
+    label: "Kanban",
+    modelUse: "KanbanBlockModel",
+    ownerPlugin: "@nocobase/plugin-kanban",
+    topLevelAddable: true,
+    formalBuiltin: true,
+    fixtureCaptured: true,
+    readbackSupported: true,
+    createSupported: true
+  },
   {
     key: "createForm",
     formalKey: "create-form",

package/dist/server/flow-surfaces/surface-context.js

@@ -48,6 +48,7 @@ var import_placement = require("./placement");
 const FILTER_TARGET_BLOCK_USES = /* @__PURE__ */ new Set([
   "TableBlockModel",
   "CalendarBlockModel",
+  "KanbanBlockModel",
   "DetailsBlockModel",
   "ListBlockModel",
   "GridCardBlockModel",
@@ -55,8 +56,10 @@ const FILTER_TARGET_BLOCK_USES = /* @__PURE__ */ new Set([
   "MapBlockModel",
   "CommentsBlockModel"
 ]);
-const LIST_LIKE_BLOCK_USES = /* @__PURE__ */ new Set(["ListBlockModel", "GridCardBlockModel"]);
-const LIST_LIKE_ITEM_USES = /* @__PURE__ */ new Set(["ListItemModel", "GridCardItemModel"]);
+const DETAILS_CARD_BLOCK_USES = /* @__PURE__ */ new Set(["ListBlockModel", "GridCardBlockModel", "KanbanBlockModel"]);
+const DETAILS_CARD_ITEM_USES = /* @__PURE__ */ new Set(["ListItemModel", "GridCardItemModel", "KanbanCardItemModel"]);
+const RECORD_ACTION_ITEM_USES = /* @__PURE__ */ new Set(["ListItemModel", "GridCardItemModel"]);
+const BLOCK_ACTION_CONTAINER_USES = /* @__PURE__ */ new Set(["ListBlockModel", "GridCardBlockModel", "KanbanBlockModel"]);
 function getDefaultGridUse(ownerUse, fallbackUse) {
   return (0, import_approval.getApprovalDefaultGridUse)(ownerUse) || fallbackUse;
 }
@@ -257,7 +260,7 @@ class FlowSurfaceContextResolver {
         wrapperUse: getFieldWrapperUse(use, "DetailsItemModel")
       };
     }
-    if (LIST_LIKE_BLOCK_USES.has(use)) {
+    if (DETAILS_CARD_BLOCK_USES.has(use)) {
       const itemUid = (_f = (_e = node.subModels) == null ? void 0 : _e.item) == null ? void 0 : _f.uid;
       if (!itemUid) {
         (0, import_errors.throwBadRequest)(`flowSurfaces addField target '${use}' is missing its item subtree`);
@@ -271,7 +274,7 @@ class FlowSurfaceContextResolver {
         wrapperUse: "DetailsItemModel"
       };
     }
-    if (LIST_LIKE_ITEM_USES.has(use)) {
+    if (DETAILS_CARD_ITEM_USES.has(use)) {
       return {
         ownerUid: node.uid,
         ownerUse: use,
@@ -331,7 +334,7 @@ class FlowSurfaceContextResolver {
     var _a;
     const resolved = await this.locator.resolve(target, { transaction });
     const node = resolved.node || await this.repository.findModelById(resolved.uid, { transaction, includeAsyncNode: true });
-    if (["TableBlockModel", "CalendarBlockModel", "TableActionsColumnModel"].includes(node == null ? void 0 : node.use) || (node == null ? void 0 : node.use) === "ActionPanelBlockModel" || LIST_LIKE_BLOCK_USES.has(node == null ? void 0 : node.use) || LIST_LIKE_ITEM_USES.has(node == null ? void 0 : node.use)) {
+    if (["TableBlockModel", "CalendarBlockModel", "TableActionsColumnModel"].includes(node == null ? void 0 : node.use) || (node == null ? void 0 : node.use) === "ActionPanelBlockModel" || BLOCK_ACTION_CONTAINER_USES.has(node == null ? void 0 : node.use) || RECORD_ACTION_ITEM_USES.has(node == null ? void 0 : node.use)) {
       return {
         parentUid: node.uid,
         subKey: "actions",

package/dist/swagger/flow-surfaces.examples.d.ts

@@ -180,6 +180,45 @@ export declare const flowSurfaceExamples: {
             }[];
         }[];
     };
+    applyBlueprintCalendar: {
+        version: string;
+        mode: string;
+        navigation: {
+            item: {
+                title: string;
+            };
+        };
+        page: {
+            title: string;
+            documentTitle: string;
+        };
+        tabs: {
+            key: string;
+            title: string;
+            blocks: {
+                key: string;
+                type: string;
+                collection: string;
+                defaultFilter: {
+                    logic: string;
+                    items: {
+                        path: string;
+                        operator: string;
+                        value: string;
+                    }[];
+                };
+                settings: {
+                    title: string;
+                    titleField: string;
+                    colorField: string;
+                    startField: string;
+                    endField: string;
+                    defaultView: string;
+                };
+                actions: string[];
+            }[];
+        }[];
+    };
     applyApprovalBlueprintInitiator: {
         version: string;
         surface: string;

package/dist/swagger/flow-surfaces.examples.js

@@ -297,6 +297,53 @@ const flowSurfaceExamples = {
       }
     ]
   },
+  applyBlueprintCalendar: {
+    version: "1",
+    mode: "create",
+    navigation: {
+      item: {
+        title: "Calendar"
+      }
+    },
+    page: {
+      title: "Calendar",
+      documentTitle: "Team calendar"
+    },
+    tabs: [
+      {
+        key: "schedule",
+        title: "Schedule",
+        blocks: [
+          {
+            key: "eventsCalendar",
+            type: "calendar",
+            collection: "calendar_events",
+            defaultFilter: makePublicBlockDefaultFilter([
+              {
+                path: "title",
+                operator: "$includes",
+                value: ""
+              },
+              {
+                path: "status",
+                operator: "$eq",
+                value: "planned"
+              }
+            ]),
+            settings: {
+              title: "Team events",
+              titleField: "title",
+              colorField: "status",
+              startField: "startsAt",
+              endField: "endsAt",
+              defaultView: "week"
+            },
+            actions: ["filter", "addNew", "refresh", "today", "turnPages", "title", "selectView"]
+          }
+        ]
+      }
+    ]
+  },
   applyApprovalBlueprintInitiator: {
     version: "1",
     surface: "initiator",

package/dist/swagger/flow-surfaces.js

@@ -43,8 +43,9 @@ const FILTER_GROUP_EXAMPLE = {
   logic: "$and",
   items: []
 };
-const PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION = "Supported only on direct `table`, `list`, or `gridCard` blocks. Backfills the default `filter` action `settings.defaultFilter` when that action exists or is auto-created. If the filter action already provides `settings.defaultFilter`, the action-level value wins.";
-const DIRECT_ADD_DEFAULT_FILTER_COMPAT_DESCRIPTION = "Public block-level `defaultFilter` is supported on direct `table` / `list` / `gridCard` creates. Legacy `defaultActionSettings.filter.defaultFilter` remains supported for compatibility and wins when both are provided.";
+const PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION = 'Supported only on direct `table`, `list`, `gridCard`, `calendar`, or `kanban` blocks. The backend runtime keeps this input optional and compatibility-tolerant: omitted, `{}`, `null`, or `{ logic: "$and", items: [] }` normalize to the empty filter group. When a non-empty value is provided, it backfills the default `filter` action `settings.defaultFilter` when that action exists or is auto-created. If the filter action already provides `settings.defaultFilter`, the action-level value wins.';
+const APPLY_BLUEPRINT_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION = "Supported only on direct `table`, `list`, `gridCard`, `calendar`, or `kanban` blocks, and must contain at least one concrete filter item. Backfills the default `filter` action `settings.defaultFilter` when that action exists or is auto-created. If the filter action already provides `settings.defaultFilter`, the action-level value wins.";
+const DIRECT_ADD_DEFAULT_FILTER_COMPAT_DESCRIPTION = "Public block-level `defaultFilter` is supported on direct `table` / `list` / `gridCard` / `calendar` / `kanban` creates. Backend runtime compatibility is preserved: omitted or empty values remain accepted and normalize to the empty filter group. Legacy `defaultActionSettings.filter.defaultFilter` remains supported for compatibility and wins when both are provided.";
 const STRING_OR_INTEGER_SCHEMA = {
   oneOf: [{ type: "string" }, { type: "integer" }]
 };
@@ -119,6 +120,8 @@ const RECORD_ACTION_TYPE_ENUM = [
 ];
 const APPLY_BLUEPRINT_BLOCK_TYPE_ENUM = [
   "table",
+  "calendar",
+  "kanban",
   "createForm",
   "editForm",
   "details",
@@ -468,7 +471,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Apply a page blueprint to create or replace one Modern page",
     description: valuesCompatibilityNote(
-      'Accepts one simplified JSON page blueprint and compiles it to internal flow-surface operations. The public blueprint describes page structure (`create` or `replace`, page metadata, ordered tabs, blocks, fields, actions, inline popups, optional reusable assets) and optional top-level `reaction.items[]` for whole-page interaction authoring. Each reaction item targets an explicit local key / bind key produced by the same blueprint run. Only explicitly listed reaction items are written. `rules: []` clears the targeted slot. Repeating the same `(type, target)` reaction slot in one blueprint is invalid. In `replace`, reaction targets always bind to the newly produced blueprint result, not historical nodes from the previous page version; if a slot must exist in the resulting surface, include it explicitly instead of relying on omission. Localized reaction edits on an existing surface should use `getReactionMeta` + `set*Rules` instead of applying a whole page blueprint again. The request body is that page-document JSON object itself and must not be JSON-stringified. Wrong: `{ "requestBody": "{\\"version\\":\\"1\\"}" }`. Internal planning details stay hidden. In `create`, `navigation.group.routeId` is the preferred way to target an existing menu group. It is exact-targeting only and cannot be mixed with existing-group metadata such as `icon`, `tooltip`, or `hideInMenu`; applyBlueprint create mode does not mutate existing group metadata, so callers should use `updateMenu` separately when that is required. When only `navigation.group.title` is provided, applyBlueprint reuses one existing same-title group when it is unique, creates a new group when none exists, and rejects ambiguous multi-match cases. Same-title reuse is title-only; if an existing group\'s metadata must change, use low-level `updateMenu` instead of applyBlueprint create. `replace` uses `target.pageSchemaUid`, updates only the explicit page-level fields provided in `page`, maps blueprint tabs to existing route-backed tab slots by index, rewrites each slot in order, removes trailing old tabs, and appends extra new tabs when needed. Tab and block keys are optional in the public blueprint; omit them unless custom layout or cross-block targeting needs a stable in-document identifier. `layout` is only allowed on tabs and inline popup documents; blocks themselves do not accept a `layout` property. Public applyBlueprint blocks do not support generic `form`; use `editForm` or `createForm`. Direct `table` / `list` / `gridCard` blocks may also provide block-level `defaultFilter`, which backfills the default `filter` action `settings.defaultFilter`; explicit filter-action `settings.defaultFilter` still wins. Inline popup documents may set `popup.tryTemplate=true` to ask the backend for the best compatible popup template before falling back to local popup content. Inline popup documents may also combine `popup.tryTemplate` with `popup.saveAsTemplate={ name, description, local? }`: a hit binds the matched template immediately and lets later inline popups in the same blueprint reuse that final bound template through `popup.template={ local, mode }`, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved and reused. Custom `edit` popups that provide `popup.blocks` must include exactly one `editForm` block; that `editForm` may omit `resource` and then inherits the opener\'s current-record context. When layout is omitted, applyBlueprint auto-generates a simple top-to-bottom layout. When a `replace` run expands a page to multiple tabs while the current page still has `enableTabs=false`, callers must set `page.enableTabs=true` explicitly. The response hides execution internals and returns only the resolved page target and final surface readback.'
+      'Accepts one simplified JSON page blueprint and compiles it to internal flow-surface operations. The public blueprint describes page structure (`create` or `replace`, page metadata, ordered tabs, blocks, fields, actions, inline popups, optional reusable assets) and optional top-level `reaction.items[]` for whole-page interaction authoring. Each reaction item targets an explicit local key / bind key produced by the same blueprint run. Only explicitly listed reaction items are written. `rules: []` clears the targeted slot. Repeating the same `(type, target)` reaction slot in one blueprint is invalid. In `replace`, reaction targets always bind to the newly produced blueprint result, not historical nodes from the previous page version; if a slot must exist in the resulting surface, include it explicitly instead of relying on omission. Localized reaction edits on an existing surface should use `getReactionMeta` + `set*Rules` instead of applying a whole page blueprint again. The request body is that page-document JSON object itself and must not be JSON-stringified. Wrong: `{ "requestBody": "{\\"version\\":\\"1\\"}" }`. Internal planning details stay hidden. In `create`, `navigation.group.routeId` is the preferred way to target an existing menu group. It is exact-targeting only and cannot be mixed with existing-group metadata such as `icon`, `tooltip`, or `hideInMenu`; applyBlueprint create mode does not mutate existing group metadata, so callers should use `updateMenu` separately when that is required. When only `navigation.group.title` is provided, applyBlueprint reuses one existing same-title group when it is unique, creates a new group when none exists, and rejects ambiguous multi-match cases. Same-title reuse is title-only; if an existing group\'s metadata must change, use low-level `updateMenu` instead of applyBlueprint create. `replace` uses `target.pageSchemaUid`, updates only the explicit page-level fields provided in `page`, maps blueprint tabs to existing route-backed tab slots by index, rewrites each slot in order, removes trailing old tabs, and appends extra new tabs when needed. Tab and block keys are optional in the public blueprint; omit them unless custom layout or cross-block targeting needs a stable in-document identifier. `layout` is only allowed on tabs and inline popup documents; blocks themselves do not accept a `layout` property. Public applyBlueprint blocks do not support generic `form`; use `editForm` or `createForm`. Direct `table` / `list` / `gridCard` / `calendar` / `kanban` blocks may also provide non-empty block-level `defaultFilter`, which backfills the default `filter` action `settings.defaultFilter`; explicit filter-action `settings.defaultFilter` still wins. Inline popup documents may set `popup.tryTemplate=true` to ask the backend for the best compatible popup template before falling back to local popup content. Inline popup documents may also combine `popup.tryTemplate` with `popup.saveAsTemplate={ name, description, local? }`: a hit binds the matched template immediately and lets later inline popups in the same blueprint reuse that final bound template through `popup.template={ local, mode }`, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved and reused. Custom `edit` popups that provide `popup.blocks` must include exactly one `editForm` block; that `editForm` may omit `resource` and then inherits the opener\'s current-record context. When layout is omitted, applyBlueprint auto-generates a simple top-to-bottom layout. When a `replace` run expands a page to multiple tabs while the current page still has `enableTabs=false`, callers must set `page.enableTabs=true` explicitly. The response hides execution internals and returns only the resolved page target and final surface readback.'
     ),
     requestBody: {
       required: true,
@@ -484,6 +487,10 @@ const actionDocs = {
             replacePage: {
               summary: "Replace one existing Modern page by pageSchemaUid",
               value: import_flow_surfaces.flowSurfaceExamples.applyBlueprintReplace
+            },
+            calendarPage: {
+              summary: "Create a direct calendar block with block-level defaultFilter",
+              value: import_flow_surfaces.flowSurfaceExamples.applyBlueprintCalendar
             }
           }
         }
@@ -526,7 +533,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Compose blocks, fields, actions and simple layout under an existing surface",
     description: valuesCompatibilityNote(
-      'Organizes content under an existing page/tab/grid/popup using the public block/action/field semantics as a low-level building primitive. The caller does not need to pass raw `use`, `fieldUse`, or `stepParams`. Blocks, fields, and actions can declare stable `key` values, and the compose result returns the same keys so later orchestration can reference nested popup or form nodes deterministically. Direct `table` / `list` / `gridCard` blocks may provide block-level `defaultFilter`, which backfills the default `filter` action `settings.defaultFilter`; explicit filter-action `settings.defaultFilter` still wins. Blocks may be created from `template`, and form templates can set `template.usage="fields"` to import only their grid fields. Popup-capable actions and fields may reuse `popup.template`, set `popup.tryTemplate=true` to ask the backend for one compatible popup template before falling back to local/default popup behavior, or combine `popup.tryTemplate` with `popup.saveAsTemplate={ name, description, local? }`: a hit binds the matched template immediately and lets later popup-capable fields/actions in the same compose call reuse that final bound template through `popup.template={ local, mode }`, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved and reused. For collection blocks under a popup, check `catalog.blocks[].resourceBindings` first. The `select / subForm / bulkEditForm` scene is currently recognized only, and popup collection block creation is not supported in that scene. For approval surfaces, use `applyApprovalBlueprint` first to bootstrap or replace the bound approval root; use `compose` only after that root already exists.'
+      'Organizes content under an existing page/tab/grid/popup using the public block/action/field semantics as a low-level building primitive. The caller does not need to pass raw `use`, `fieldUse`, or `stepParams`. Blocks, fields, and actions can declare stable `key` values, and the compose result returns the same keys so later orchestration can reference nested popup or form nodes deterministically. Direct `table` / `list` / `gridCard` / `calendar` / `kanban` blocks may provide block-level `defaultFilter`; backend runtime compatibility remains compatibility-tolerant for omitted or empty values, and any provided value backfills the default `filter` action `settings.defaultFilter`. Explicit filter-action `settings.defaultFilter` still wins. Blocks may be created from `template`, and form templates can set `template.usage="fields"` to import only their grid fields. Popup-capable actions and fields may reuse `popup.template`, set `popup.tryTemplate=true` to ask the backend for one compatible popup template before falling back to local/default popup behavior, or combine `popup.tryTemplate` with `popup.saveAsTemplate={ name, description, local? }`: a hit binds the matched template immediately and lets later popup-capable fields/actions in the same compose call reuse that final bound template through `popup.template={ local, mode }`, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved and reused. For collection blocks under a popup, check `catalog.blocks[].resourceBindings` first. The `select / subForm / bulkEditForm` scene is currently recognized only, and popup collection block creation is not supported in that scene. For approval surfaces, use `applyApprovalBlueprint` first to bootstrap or replace the bound approval root; use `compose` only after that root already exists.'
     ),
     requestBody: {
       required: true,
@@ -766,7 +773,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add a block under a surface or grid container",
     description: valuesCompatibilityNote(
-      'Creates a block by catalog key or an explicitly supported block use. It can also create from `template`, using `mode="reference"` or `mode="copy"`. Form templates may set `template.usage="fields"` to create a fresh host block and import only its grid fields. Popup-capable host nodes automatically receive the popup shell. For collection blocks under a popup, check `catalog.blocks[].resourceBindings` first, then pass the semantic `resource.binding`. The lower-level `resourceInit` is still accepted for compatibility, but the server validates it against popup semantics. `resource` and `resourceInit` are mutually exclusive. Direct `table` / `list` / `gridCard` creation may also provide block-level `defaultFilter`, which backfills the auto-created default filter action. Legacy `defaultActionSettings.filter.defaultFilter` is still supported for compatibility and wins when both are provided. The `select / subForm / bulkEditForm` scene is currently recognized only, and popup collection block creation is not supported in that scene. Direct add does not accept raw `props` / `decoratorProps` / `stepParams` / `flowRegistry`. Use `settings` and reuse the public configuration semantics from `configure.changes` plus the catalog item/node `configureOptions`. Approval block keys are only exposed under approval grids and do not auto-create an approval root; bootstrap approval surfaces with `applyApprovalBlueprint` first.'
+      'Creates a block by catalog key or an explicitly supported block use. It can also create from `template`, using `mode="reference"` or `mode="copy"`. Form templates may set `template.usage="fields"` to create a fresh host block and import only its grid fields. Popup-capable host nodes automatically receive the popup shell. For collection blocks under a popup, check `catalog.blocks[].resourceBindings` first, then pass the semantic `resource.binding`. The lower-level `resourceInit` is still accepted for compatibility, but the server validates it against popup semantics. `resource` and `resourceInit` are mutually exclusive. Direct `table` / `list` / `gridCard` / `calendar` / `kanban` creation may also provide block-level `defaultFilter`; backend runtime compatibility remains tolerant of omitted or empty values, and any provided value backfills the auto-created default filter action. Legacy `defaultActionSettings.filter.defaultFilter` is still supported for compatibility and wins when both are provided. The `select / subForm / bulkEditForm` scene is currently recognized only, and popup collection block creation is not supported in that scene. Direct add does not accept raw `props` / `decoratorProps` / `stepParams` / `flowRegistry`. Use `settings` and reuse the public configuration semantics from `configure.changes` plus the catalog item/node `configureOptions`. Approval block keys are only exposed under approval grids and do not auto-create an approval root; bootstrap approval surfaces with `applyApprovalBlueprint` first.'
     ),
     requestBody: {
       required: true,
@@ -934,7 +941,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add multiple blocks sequentially under the same target",
     description: valuesCompatibilityNote(
-      "Creates multiple blocks sequentially under the same target. Each item may include `settings`, `defaultFilter`, `defaultActionSettings`, or `template`, but raw `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. Direct `table` / `list` / `gridCard` items may use block-level `defaultFilter` to backfill the auto-created default filter action. Legacy `defaultActionSettings.filter.defaultFilter` is still supported for compatibility and wins when both are provided. Partial-success semantics apply: a failure in one item does not roll back the others. Results are returned in input order as `index/key/ok/result/error`, and each `error` always includes `message/type/code/status`."
+      "Creates multiple blocks sequentially under the same target. Each item may include `settings`, `defaultFilter`, `defaultActionSettings`, or `template`, but raw `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. Direct `table` / `list` / `gridCard` / `calendar` / `kanban` items may use block-level `defaultFilter` to backfill the auto-created default filter action; backend runtime compatibility remains tolerant of omitted or empty values. Legacy `defaultActionSettings.filter.defaultFilter` is still supported for compatibility and wins when both are provided. Partial-success semantics apply: a failure in one item does not roll back the others. Results are returned in input order as `index/key/ok/result/error`, and each `error` always includes `message/type/code/status`."
     ),
     requestBody: requestBody("FlowSurfaceAddBlocksRequest", import_flow_surfaces.flowSurfaceExamples.addBlocks),
     responses: responses("FlowSurfaceAddBlocksResult")
@@ -2431,7 +2438,7 @@ const schemas = {
       },
       actions: {
         type: "array",
-        description: "Block-level actions. For table/list/gridCard, prefer block-wide collection actions here.",
+        description: "Block-level actions. For table/list/gridCard/calendar/kanban, prefer block-wide collection actions here.",
         items: ref("FlowSurfaceComposeActionSpec")
       },
       recordActions: {
@@ -3477,7 +3484,7 @@ const schemas = {
       settings: ANY_OBJECT_SCHEMA,
       defaultFilter: {
         allOf: [ref("FlowSurfaceFilterGroup")],
-        description: PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION
+        description: APPLY_BLUEPRINT_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION
       },
       fields: {
         type: "array",

package/package.json

@@ -4,7 +4,7 @@
   "displayName.zh-CN": "前端流引擎",
   "description": "",
   "description.zh-CN": "",
-  "version": "2.1.0-beta.17",
+  "version": "2.1.0-beta.19",
   "main": "./dist/server/index.js",
   "license": "Apache-2.0",
   "devDependencies": {
@@ -24,5 +24,5 @@
     "@nocobase/test": "2.x",
     "@nocobase/utils": "2.x"
   },
-  "gitHead": "227d625e47174ab7b3a90170e7c6c67bbdf36e23"
+  "gitHead": "d89ab08dbcb25877de69827d5bad6823c27b2cbb"
 }