@nocobase/plugin-flow-engine 2.1.0-alpha.20 → 2.1.0-alpha.22

package/dist/swagger/flow-surfaces.js

@@ -43,6 +43,8 @@ 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 STRING_OR_INTEGER_SCHEMA = {
   oneOf: [{ type: "string" }, { type: "integer" }]
 };
@@ -137,8 +139,10 @@ const REACTION_FINGERPRINT_DESCRIPTION = "Optional optimistic-concurrency finger
 const REACTION_RULES_REPLACE_DESCRIPTION = "Full replacement payload for the resolved reaction slot. Pass `[]` to clear all rules from that slot.";
 const REACTION_LOCALIZED_FORM_TARGET_DESCRIPTION = "Reaction write target. Use the live block/action uid for localized edits. For form field-value and form field-linkage writes, keep passing the outer form block uid; the backend resolves the inner form-grid slot automatically.";
 const REACTION_OUTER_FORM_TARGET_NOTE = "Pass the outer form block uid, not the inner form-grid uid.";
-const REQUEST_POPUP_TRY_TEMPLATE_DESCRIPTION = "When true and no explicit popup.template is provided, the backend tries to auto-select one compatible popup template. Non-relation scenes only match non-relation templates. Relation scenes prefer same-relation templates first, then compatible non-relation templates. When no candidate matches, the request silently falls back to local/default popup behavior.";
-const REQUEST_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION = "Immediately saves explicit local popup blocks as a popup template and converts the created popup to that template reference. Requires local `popup.blocks` and cannot be combined with `popup.template` or `popup.tryTemplate`. When `popup.saveAsTemplate.local` is provided, later `popup.template.local` references in the same compose/applyBlueprint call can reuse that saved popup template.";
+const REQUEST_POPUP_TRY_TEMPLATE_DESCRIPTION = "When true and no explicit popup.template is provided, the backend tries to auto-select one compatible popup template. Non-relation scenes only match non-relation templates. Relation scenes prefer same-relation templates first, then compatible non-relation templates. When no candidate matches, the request falls back to local/default popup behavior. If popup.saveAsTemplate is also provided, a hit reuses the matched template directly, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved as a template.";
+const REQUEST_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION = "Immediately saves explicit local popup blocks as a popup template and converts the created popup to that template reference. It cannot be combined with `popup.template`. When combined with `popup.tryTemplate`, a hit binds the matched template without creating a new one, and `popup.saveAsTemplate.local` resolves to that final bound template uid. When `popup.tryTemplate` misses, explicit local `popup.blocks` are required so the fallback popup can be saved. Later `popup.template.local` references in the same compose/applyBlueprint call reuse that final bound template uid.";
+const APPLY_BLUEPRINT_POPUP_TRY_TEMPLATE_DESCRIPTION = "When true and no explicit popup.template is provided, applyBlueprint asks the backend to auto-select one compatible popup template. Non-relation scenes only match non-relation templates. Relation scenes prefer same-relation templates first, then compatible non-relation templates. When no candidate matches, inline popup blocks/layout still act as the fallback if present. If popup.saveAsTemplate is also provided, a hit reuses the matched template directly, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved as a template.";
+const APPLY_BLUEPRINT_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION = "Immediately saves explicit local popup blocks as a popup template and converts the created popup to that template reference. It cannot be combined with `popup.template`. When combined with `popup.tryTemplate`, a hit binds the matched template without creating a new one, and `popup.saveAsTemplate.local` resolves to that final bound template uid. When `popup.tryTemplate` misses, explicit local `popup.blocks` are required so the fallback popup can be saved. Later `popup.template.local` references in the same blueprint reuse that final bound template uid.";
 function ref(name) {
   return {
     $ref: `#/components/schemas/${name}`
@@ -464,7 +468,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`. 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 set `popup.saveAsTemplate={ name, description, local? }` to convert the newly created local popup into a saved popup template immediately, and later inline popups in the same blueprint may reuse that freshly created template through `popup.template={ local, mode }`. 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` 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.'
     ),
     requestBody: {
       required: true,
@@ -522,7 +526,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. 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 set `popup.saveAsTemplate={ name, description, local? }` to immediately save newly created local popup content as a popup template reference. Later popup-capable fields and actions in the same compose call may reuse that freshly created template through `popup.template={ local, mode }`. 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` 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.'
     ),
     requestBody: {
       required: true,
@@ -762,7 +766,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. 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` 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.'
     ),
     requestBody: {
       required: true,
@@ -785,6 +789,10 @@ const actionDocs = {
             jsBlock: {
               summary: "Create a JS block directly under a page/tab/grid container",
               value: import_flow_surfaces.flowSurfaceExamples.addJsBlock
+            },
+            tableDefaultFilters: {
+              summary: "Create a table and configure the auto-created default filter action",
+              value: import_flow_surfaces.flowSurfaceExamples.addTableBlockWithDefaultFilters
             }
           }
         }
@@ -796,7 +804,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add a field wrapper and inner field under a field container",
     description: valuesCompatibilityNote(
-      "Automatically derives the wrapper/inner-field combination from the container use and the field interface. It can also import a form template through `template`, using `reference` or `copy` mode for the target form grid. `fieldUse` is only kept as a compatibility check and is no longer an arbitrary creation entry. Direct add does not accept raw `wrapperProps` / `fieldProps` / `props` / `decoratorProps` / `stepParams` / `flowRegistry`. Use `settings` and reuse the public configuration semantics from `configure.changes` plus the catalog item/node `configureOptions`. Popup-capable fields can also pass `popup` directly to append a local popup subtree or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. `popup.saveAsTemplate={ name, description }` saves explicit local popup blocks as a popup template and converts the created popup to that reference immediately. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. If local openView is enabled but no popup content is provided, the server fills in the popup page/tab/grid shell automatically. Under approval forms, direct field creation preserves the `PatternFormFieldModel` inner node semantics and does not allow standalone `jsItem`."
+      "Automatically derives the wrapper/inner-field combination from the container use and the field interface. It can also import a form template through `template`, using `reference` or `copy` mode for the target form grid. `fieldUse` is only kept as a compatibility check and is no longer an arbitrary creation entry. Direct add does not accept raw `wrapperProps` / `fieldProps` / `props` / `decoratorProps` / `stepParams` / `flowRegistry`. Use `settings` and reuse the public configuration semantics from `configure.changes` plus the catalog item/node `configureOptions`. Popup-capable fields can also pass `popup` directly to append a local popup subtree or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. It may be combined with `popup.saveAsTemplate={ name, description }`: a hit reuses the matched template directly, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved as a template reference. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. If local openView is enabled but no popup content is provided, the server fills in the popup page/tab/grid shell automatically. Under approval forms, direct field creation preserves the `PatternFormFieldModel` inner node semantics and does not allow standalone `jsItem`."
     ),
     requestBody: {
       required: true,
@@ -846,7 +854,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add a non-record action under an allowed block/form/filter-form/action-panel container",
     description: valuesCompatibilityNote(
-      "Only non-record actions that are public in the catalog and visible in the current container may be created. Typical cases include table block actions, form submit, filter-form reset, and action-panel actions. Use `addRecordAction` for record actions. Direct add does not accept raw `props` / `decoratorProps` / `stepParams` / `flowRegistry`. Use `settings` and reuse `configure.changes` plus the catalog item/node `configureOptions`. Popup-capable actions may also include `popup` directly to append a popup subtree or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. `popup.saveAsTemplate={ name, description }` saves explicit local popup blocks as a popup template and converts the created popup to that reference immediately. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. Approval action keys are singleton within one approval form or process form, and flowSurfaces reconciles the related workflow/node runtime config after successful writes."
+      "Only non-record actions that are public in the catalog and visible in the current container may be created. Typical cases include table block actions, form submit, filter-form reset, and action-panel actions. Use `addRecordAction` for record actions. Direct add does not accept raw `props` / `decoratorProps` / `stepParams` / `flowRegistry`. Use `settings` and reuse `configure.changes` plus the catalog item/node `configureOptions`. Popup-capable actions may also include `popup` directly to append a popup subtree or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. It may be combined with `popup.saveAsTemplate={ name, description }`: a hit reuses the matched template directly, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved as a template reference. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. Approval action keys are singleton within one approval form or process form, and flowSurfaces reconciles the related workflow/node runtime config after successful writes."
     ),
     requestBody: {
       required: true,
@@ -888,7 +896,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add a record action under a record-capable owner target",
     description: valuesCompatibilityNote(
-      `Only record actions that are public in the catalog and visible in the current container may be created. The public target must be a record-capable owner target such as table/details/list/gridCard. Do not pass internal container uids such as a table actions column or a list/gridCard item. ${ADD_CHILD_TREE_TABLE_NOTE} Direct add does not accept raw \`props\` / \`decoratorProps\` / \`stepParams\` / \`flowRegistry\`. Use \`settings\` and reuse \`configure.changes\` plus the catalog item/node \`configureOptions\`. Popup-capable actions may also include \`popup\` directly to append a popup subtree or \`popup.template\` to reuse a saved popup template in \`reference\` / \`copy\` mode. \`popup.tryTemplate=true\` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. \`popup.saveAsTemplate={ name, description }\` saves explicit local popup blocks as a popup template and converts the created popup to that reference immediately. When \`popup.template\` is present, \`popup.title\` still applies, while local \`popup.mode\` / \`popup.blocks\` / \`popup.layout\` are accepted but ignored.`
+      `Only record actions that are public in the catalog and visible in the current container may be created. The public target must be a record-capable owner target such as table/details/list/gridCard. Do not pass internal container uids such as a table actions column or a list/gridCard item. ${ADD_CHILD_TREE_TABLE_NOTE} Direct add does not accept raw \`props\` / \`decoratorProps\` / \`stepParams\` / \`flowRegistry\`. Use \`settings\` and reuse \`configure.changes\` plus the catalog item/node \`configureOptions\`. Popup-capable actions may also include \`popup\` directly to append a popup subtree or \`popup.template\` to reuse a saved popup template in \`reference\` / \`copy\` mode. \`popup.tryTemplate=true\` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. It may be combined with \`popup.saveAsTemplate={ name, description }\`: a hit reuses the matched template directly, while a miss requires explicit local \`popup.blocks\` so the fallback popup can be saved as a template reference. When \`popup.template\` is present, \`popup.title\` still applies, while local \`popup.mode\` / \`popup.blocks\` / \`popup.layout\` are accepted but ignored.`
     ),
     requestBody: {
       required: true,
@@ -926,7 +934,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` or `template`, but raw `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. 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` 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`."
     ),
     requestBody: requestBody("FlowSurfaceAddBlocksRequest", import_flow_surfaces.flowSurfaceExamples.addBlocks),
     responses: responses("FlowSurfaceAddBlocksResult")
@@ -935,7 +943,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add multiple fields sequentially under the same target",
     description: valuesCompatibilityNote(
-      "Creates multiple fields sequentially under the same target. The request may either import one shared `template` or create explicit `fields[]`. Each item may include `settings`, and popup-capable fields may also include `popup` directly for local popup content or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. `popup.saveAsTemplate={ name, description }` saves explicit local popup blocks as a popup template and converts the created popup to that reference immediately. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. Raw `wrapperProps` / `fieldProps` / `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. 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 fields sequentially under the same target. The request may either import one shared `template` or create explicit `fields[]`. Each item may include `settings`, and popup-capable fields may also include `popup` directly for local popup content or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. It may be combined with `popup.saveAsTemplate={ name, description }`: a hit reuses the matched template directly, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved as a template reference. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. Raw `wrapperProps` / `fieldProps` / `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. 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("FlowSurfaceAddFieldsRequest", import_flow_surfaces.flowSurfaceExamples.addFields),
     responses: responses("FlowSurfaceAddFieldsResult")
@@ -944,7 +952,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add multiple non-record actions sequentially under the same target",
     description: valuesCompatibilityNote(
-      "Creates multiple non-record actions sequentially under the same target. Each item may include `settings`, and popup-capable actions may also include `popup` directly for local popup content or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. `popup.saveAsTemplate={ name, description }` saves explicit local popup blocks as a popup template and converts the created popup to that reference immediately. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. Raw `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. Partial-success semantics apply. Record actions do not belong to this entry and should use `addRecordActions` instead. Each failed item always returns an `error` with `message/type/code/status`."
+      "Creates multiple non-record actions sequentially under the same target. Each item may include `settings`, and popup-capable actions may also include `popup` directly for local popup content or `popup.template` to reuse a saved popup template in `reference` / `copy` mode. `popup.tryTemplate=true` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. It may be combined with `popup.saveAsTemplate={ name, description }`: a hit reuses the matched template directly, while a miss requires explicit local `popup.blocks` so the fallback popup can be saved as a template reference. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored. Raw `props` / `decoratorProps` / `stepParams` / `flowRegistry` are not accepted. Partial-success semantics apply. Record actions do not belong to this entry and should use `addRecordActions` instead. Each failed item always returns an `error` with `message/type/code/status`."
     ),
     requestBody: requestBody("FlowSurfaceAddActionsRequest", import_flow_surfaces.flowSurfaceExamples.addActions),
     responses: responses("FlowSurfaceAddActionsResult")
@@ -953,7 +961,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Add multiple record actions sequentially under the same record-capable owner target",
     description: valuesCompatibilityNote(
-      `Creates multiple record actions sequentially under the same target. The target must be a record-capable owner target, and the server resolves the canonical record-action container automatically. Do not pass internal container uids such as a table actions column or a list/gridCard item. ${ADD_CHILD_TREE_TABLE_NOTE} Each item may include \`settings\`, and popup-capable actions may also include \`popup\` directly for local popup content or \`popup.template\` to reuse a saved popup template in \`reference\` / \`copy\` mode. \`popup.tryTemplate=true\` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. \`popup.saveAsTemplate={ name, description }\` saves explicit local popup blocks as a popup template and converts the created popup to that reference immediately. When \`popup.template\` is present, \`popup.title\` still applies, while local \`popup.mode\` / \`popup.blocks\` / \`popup.layout\` are accepted but ignored. Raw \`props\` / \`decoratorProps\` / \`stepParams\` / \`flowRegistry\` are not accepted. Partial-success semantics apply: a failure in one item does not roll back the others. Each failed item always returns an \`error\` with \`message/type/code/status\`.`
+      `Creates multiple record actions sequentially under the same target. The target must be a record-capable owner target, and the server resolves the canonical record-action container automatically. Do not pass internal container uids such as a table actions column or a list/gridCard item. ${ADD_CHILD_TREE_TABLE_NOTE} Each item may include \`settings\`, and popup-capable actions may also include \`popup\` directly for local popup content or \`popup.template\` to reuse a saved popup template in \`reference\` / \`copy\` mode. \`popup.tryTemplate=true\` asks the backend to auto-select a compatible popup template first, preferring the same relation when one exists and otherwise falling back to a compatible non-relation template. It may be combined with \`popup.saveAsTemplate={ name, description }\`: a hit reuses the matched template directly, while a miss requires explicit local \`popup.blocks\` so the fallback popup can be saved as a template reference. When \`popup.template\` is present, \`popup.title\` still applies, while local \`popup.mode\` / \`popup.blocks\` / \`popup.layout\` are accepted but ignored. Raw \`props\` / \`decoratorProps\` / \`stepParams\` / \`flowRegistry\` are not accepted. Partial-success semantics apply: a failure in one item does not roll back the others. Each failed item always returns an \`error\` with \`message/type/code/status\`.`
     ),
     requestBody: {
       required: true,
@@ -1318,6 +1326,27 @@ const schemas = {
     additionalProperties: false,
     example: FILTER_GROUP_EXAMPLE
   },
+  FlowSurfaceDefaultFilterActionSettings: {
+    type: "object",
+    properties: {
+      filterableFieldNames: {
+        type: "array",
+        items: {
+          type: "string"
+        }
+      },
+      defaultFilter: ref("FlowSurfaceFilterGroup")
+    },
+    additionalProperties: true
+  },
+  FlowSurfaceDefaultActionSettings: {
+    type: "object",
+    description: DIRECT_ADD_DEFAULT_FILTER_COMPAT_DESCRIPTION,
+    properties: {
+      filter: ref("FlowSurfaceDefaultFilterActionSettings")
+    },
+    additionalProperties: false
+  },
   FlowSurfaceEventCapabilities: {
     type: "object",
     properties: {
@@ -2239,11 +2268,11 @@ const schemas = {
       template: ref("FlowSurfacePopupTemplateRef"),
       tryTemplate: {
         type: "boolean",
-        description: "When true and no explicit popup.template is provided, the backend tries to auto-select one compatible popup template. Non-relation scenes only match non-relation templates. Relation scenes prefer same-relation templates first, then compatible non-relation templates. When no candidate matches, the request silently falls back to local/default popup behavior."
+        description: REQUEST_POPUP_TRY_TEMPLATE_DESCRIPTION
       },
       saveAsTemplate: {
         allOf: [ref("FlowSurfacePopupSaveAsTemplate")],
-        description: "Immediately saves explicit local popup blocks as a popup template and converts the created popup to that template reference. Requires local `popup.blocks` and cannot be combined with `popup.template` or `popup.tryTemplate`."
+        description: REQUEST_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION
       },
       mode: {
         type: "string",
@@ -2280,7 +2309,7 @@ const schemas = {
       template: ref("FlowSurfacePopupTemplateRef"),
       tryTemplate: {
         type: "boolean",
-        description: "When true and no explicit popup.template is provided, the backend tries to auto-select one compatible popup template. Non-relation scenes only match non-relation templates. Relation scenes prefer same-relation templates first, then compatible non-relation templates. When no candidate matches, the request silently falls back to local/default popup behavior."
+        description: REQUEST_POPUP_TRY_TEMPLATE_DESCRIPTION
       },
       defaultType: {
         type: "string",
@@ -2289,7 +2318,7 @@ const schemas = {
       },
       saveAsTemplate: {
         allOf: [ref("FlowSurfacePopupSaveAsTemplate")],
-        description: "Immediately saves explicit local popup blocks as a popup template and converts the created popup to that template reference. Requires local `popup.blocks` and cannot be combined with `popup.template` or `popup.tryTemplate`."
+        description: REQUEST_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION
       },
       mode: {
         type: "string",
@@ -2388,6 +2417,10 @@ const schemas = {
       template: ref("FlowSurfaceBlockTemplateRef"),
       resource: ref("FlowSurfaceBlockResourceInput"),
       settings: ANY_OBJECT_SCHEMA,
+      defaultFilter: {
+        allOf: [ref("FlowSurfaceFilterGroup")],
+        description: PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION
+      },
       fields: {
         type: "array",
         items: ref("FlowSurfaceComposeFieldSpec")
@@ -3308,7 +3341,7 @@ const schemas = {
       template: ref("FlowSurfaceRequestPopupTemplateRef"),
       tryTemplate: {
         type: "boolean",
-        description: "When true and no explicit popup.template is provided, applyBlueprint asks the backend to auto-select one compatible popup template. Non-relation scenes only match non-relation templates. Relation scenes prefer same-relation templates first, then compatible non-relation templates. When no candidate matches, inline popup blocks/layout still act as the fallback if present."
+        description: APPLY_BLUEPRINT_POPUP_TRY_TEMPLATE_DESCRIPTION
       },
       defaultType: {
         type: "string",
@@ -3317,7 +3350,7 @@ const schemas = {
       },
       saveAsTemplate: {
         allOf: [ref("FlowSurfaceRequestPopupSaveAsTemplate")],
-        description: "Immediately saves explicit local popup blocks as a popup template and converts the created popup to that template reference. Requires local `popup.blocks` and cannot be combined with `popup.template` or `popup.tryTemplate`. When `popup.saveAsTemplate.local` is provided, later `popup.template.local` references in the same blueprint can reuse that saved popup template."
+        description: APPLY_BLUEPRINT_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION
       },
       blocks: {
         type: "array",
@@ -3442,6 +3475,10 @@ const schemas = {
       resource: ref("FlowSurfaceBlockResourceInput"),
       template: ref("FlowSurfaceBlockTemplateRef"),
       settings: ANY_OBJECT_SCHEMA,
+      defaultFilter: {
+        allOf: [ref("FlowSurfaceFilterGroup")],
+        description: PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION
+      },
       fields: {
         type: "array",
         items: ref("FlowSurfaceApplyBlueprintFieldSpec")
@@ -3550,10 +3587,82 @@ const schemas = {
     },
     additionalProperties: false
   },
+  FlowSurfaceApplyBlueprintDefaultFieldGroup: {
+    type: "object",
+    required: ["title", "fields"],
+    description: "Collection-level candidate field group used only for backend-generated default popup content. Scenario-specific filtering may remove fields or whole groups.",
+    properties: {
+      key: { type: "string" },
+      title: { type: "string" },
+      fields: {
+        type: "array",
+        minItems: 1,
+        items: { type: "string" }
+      }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyBlueprintDefaultPopupName: {
+    type: "object",
+    required: ["name", "description"],
+    description: "Default popup metadata with required `name` and `description`. Do not place blocks, fields, fieldGroups, layout, or other content here.",
+    properties: {
+      name: { type: "string" },
+      description: { type: "string" }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyBlueprintDefaultPopupActionMap: {
+    type: "object",
+    properties: {
+      view: ref("FlowSurfaceApplyBlueprintDefaultPopupName"),
+      addNew: ref("FlowSurfaceApplyBlueprintDefaultPopupName"),
+      edit: ref("FlowSurfaceApplyBlueprintDefaultPopupName")
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyBlueprintDefaultPopups: {
+    type: "object",
+    description: "Popup defaults with required `name` and `description` metadata. Use `associations`, not `relations`, for source-collection association field popup names.",
+    properties: {
+      view: ref("FlowSurfaceApplyBlueprintDefaultPopupName"),
+      addNew: ref("FlowSurfaceApplyBlueprintDefaultPopupName"),
+      edit: ref("FlowSurfaceApplyBlueprintDefaultPopupName"),
+      associations: {
+        type: "object",
+        additionalProperties: ref("FlowSurfaceApplyBlueprintDefaultPopupActionMap")
+      }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyBlueprintDefaultCollection: {
+    type: "object",
+    description: "v1 collection-level defaults. Only `fieldGroups` and `popups` with required `name` and `description` metadata are supported; block-specific defaults are not supported.",
+    properties: {
+      fieldGroups: {
+        type: "array",
+        minItems: 1,
+        items: ref("FlowSurfaceApplyBlueprintDefaultFieldGroup")
+      },
+      popups: ref("FlowSurfaceApplyBlueprintDefaultPopups")
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyBlueprintDefaults: {
+    type: "object",
+    description: "Optional v1 applyBlueprint defaults. Supports only `collections`; do not send `defaults.blocks`.",
+    properties: {
+      collections: {
+        type: "object",
+        additionalProperties: ref("FlowSurfaceApplyBlueprintDefaultCollection")
+      }
+    },
+    additionalProperties: false
+  },
   FlowSurfaceApplyBlueprintRequest: {
     type: "object",
     required: ["mode", "tabs"],
-    description: "Simplified page-structure request object for applyBlueprint. `version` may be omitted and defaults to '1'. Runtime validation enforces mode-specific rules: create does not accept target, while replace requires target.pageSchemaUid and does not use navigation.",
+    description: "Simplified page-structure request object for applyBlueprint. `version` may be omitted and defaults to '1'. Runtime validation enforces mode-specific rules: create does not accept target, while replace requires target.pageSchemaUid and does not use navigation. `defaults.collections` may provide collection-level fieldGroups and popup metadata with required `name` and `description` for generated default popups; v1 does not support `defaults.blocks`.",
     properties: {
       version: {
         type: "string",
@@ -3566,6 +3675,7 @@ const schemas = {
       target: ref("FlowSurfaceApplyBlueprintTarget"),
       navigation: ref("FlowSurfaceApplyBlueprintNavigation"),
       page: ref("FlowSurfaceApplyBlueprintPage"),
+      defaults: ref("FlowSurfaceApplyBlueprintDefaults"),
       tabs: {
         type: "array",
         minItems: 1,
@@ -4167,7 +4277,12 @@ const schemas = {
       template: ref("FlowSurfaceBlockTemplateRef"),
       resource: ref("FlowSurfaceBlockResourceInput"),
       resourceInit: ref("FlowSurfaceResourceInit"),
-      settings: ANY_OBJECT_SCHEMA
+      settings: ANY_OBJECT_SCHEMA,
+      defaultFilter: {
+        allOf: [ref("FlowSurfaceFilterGroup")],
+        description: PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION
+      },
+      defaultActionSettings: ref("FlowSurfaceDefaultActionSettings")
     },
     additionalProperties: false
   },
@@ -4431,7 +4546,12 @@ const schemas = {
       template: ref("FlowSurfaceBlockTemplateRef"),
       resource: ref("FlowSurfaceBlockResourceInput"),
       resourceInit: ref("FlowSurfaceResourceInit"),
-      settings: ANY_OBJECT_SCHEMA
+      settings: ANY_OBJECT_SCHEMA,
+      defaultFilter: {
+        allOf: [ref("FlowSurfaceFilterGroup")],
+        description: PUBLIC_DATA_SURFACE_BLOCK_DEFAULT_FILTER_DESCRIPTION
+      },
+      defaultActionSettings: ref("FlowSurfaceDefaultActionSettings")
     },
     additionalProperties: false
   },

package/dist/swagger/index.d.ts

@@ -563,6 +563,12 @@ declare const _default: {
                         type: string;
                         additionalProperties: boolean;
                     };
+                    defaultFilter: {
+                        allOf: {
+                            $ref: string;
+                        }[];
+                        description: string;
+                    };
                     fields: {
                         type: string;
                         items: {
@@ -2170,6 +2176,12 @@ declare const _default: {
                         type: string;
                         additionalProperties: boolean;
                     };
+                    defaultFilter: {
+                        allOf: {
+                            $ref: string;
+                        }[];
+                        description: string;
+                    };
                     fields: {
                         type: string;
                         items: {
@@ -2326,6 +2338,108 @@ declare const _default: {
                 };
                 additionalProperties: boolean;
             };
+            FlowSurfaceApplyBlueprintDefaultFieldGroup: {
+                type: string;
+                required: string[];
+                description: string;
+                properties: {
+                    key: {
+                        type: string;
+                    };
+                    title: {
+                        type: string;
+                    };
+                    fields: {
+                        type: string;
+                        minItems: number;
+                        items: {
+                            type: string;
+                        };
+                    };
+                };
+                additionalProperties: boolean;
+            };
+            FlowSurfaceApplyBlueprintDefaultPopupName: {
+                type: string;
+                required: string[];
+                description: string;
+                properties: {
+                    name: {
+                        type: string;
+                    };
+                    description: {
+                        type: string;
+                    };
+                };
+                additionalProperties: boolean;
+            };
+            FlowSurfaceApplyBlueprintDefaultPopupActionMap: {
+                type: string;
+                properties: {
+                    view: {
+                        $ref: string;
+                    };
+                    addNew: {
+                        $ref: string;
+                    };
+                    edit: {
+                        $ref: string;
+                    };
+                };
+                additionalProperties: boolean;
+            };
+            FlowSurfaceApplyBlueprintDefaultPopups: {
+                type: string;
+                description: string;
+                properties: {
+                    view: {
+                        $ref: string;
+                    };
+                    addNew: {
+                        $ref: string;
+                    };
+                    edit: {
+                        $ref: string;
+                    };
+                    associations: {
+                        type: string;
+                        additionalProperties: {
+                            $ref: string;
+                        };
+                    };
+                };
+                additionalProperties: boolean;
+            };
+            FlowSurfaceApplyBlueprintDefaultCollection: {
+                type: string;
+                description: string;
+                properties: {
+                    fieldGroups: {
+                        type: string;
+                        minItems: number;
+                        items: {
+                            $ref: string;
+                        };
+                    };
+                    popups: {
+                        $ref: string;
+                    };
+                };
+                additionalProperties: boolean;
+            };
+            FlowSurfaceApplyBlueprintDefaults: {
+                type: string;
+                description: string;
+                properties: {
+                    collections: {
+                        type: string;
+                        additionalProperties: {
+                            $ref: string;
+                        };
+                    };
+                };
+                additionalProperties: boolean;
+            };
             FlowSurfaceApplyBlueprintRequest: {
                 type: string;
                 required: string[];
@@ -2348,6 +2462,9 @@ declare const _default: {
                     page: {
                         $ref: string;
                     };
+                    defaults: {
+                        $ref: string;
+                    };
                     tabs: {
                         type: string;
                         minItems: number;
@@ -3088,6 +3205,15 @@ declare const _default: {
                         type: string;
                         additionalProperties: boolean;
                     };
+                    defaultFilter: {
+                        allOf: {
+                            $ref: string;
+                        }[];
+                        description: string;
+                    };
+                    defaultActionSettings: {
+                        $ref: string;
+                    };
                 };
                 additionalProperties: boolean;
             };
@@ -3391,6 +3517,15 @@ declare const _default: {
                         type: string;
                         additionalProperties: boolean;
                     };
+                    defaultFilter: {
+                        allOf: {
+                            $ref: string;
+                        }[];
+                        description: string;
+                    };
+                    defaultActionSettings: {
+                        $ref: string;
+                    };
                 };
                 additionalProperties: boolean;
             };
@@ -4862,6 +4997,31 @@ declare const _default: {
                     items: any[];
                 };
             };
+            FlowSurfaceDefaultFilterActionSettings: {
+                type: string;
+                properties: {
+                    filterableFieldNames: {
+                        type: string;
+                        items: {
+                            type: string;
+                        };
+                    };
+                    defaultFilter: {
+                        $ref: string;
+                    };
+                };
+                additionalProperties: boolean;
+            };
+            FlowSurfaceDefaultActionSettings: {
+                type: string;
+                description: string;
+                properties: {
+                    filter: {
+                        $ref: string;
+                    };
+                };
+                additionalProperties: boolean;
+            };
             FlowSurfaceEventCapabilities: {
                 type: string;
                 properties: {

package/package.json

@@ -4,7 +4,7 @@
   "displayName.zh-CN": "前端流引擎",
   "description": "",
   "description.zh-CN": "",
-  "version": "2.1.0-alpha.20",
+  "version": "2.1.0-alpha.22",
   "main": "./dist/server/index.js",
   "license": "Apache-2.0",
   "devDependencies": {
@@ -24,5 +24,5 @@
     "@nocobase/test": "2.x",
     "@nocobase/utils": "2.x"
   },
-  "gitHead": "3d1535db6bf93ca23257faf474afee0d565f54c6"
+  "gitHead": "81ed83f158f172cca607b36beaf8428b14ba16ad"
 }