@nocobase/plugin-flow-engine 2.1.0-beta.23 → 2.1.0-beta.25

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

@@ -129,13 +129,6 @@ declare const _default: {
                             };
                             description: string;
                         };
-                        selectorFields: {
-                            type: string;
-                            items: {
-                                type: string;
-                            };
-                            description: string;
-                        };
                         titleField: {
                             type: string;
                         };
@@ -197,7 +190,6 @@ declare const _default: {
                         fieldPath?: undefined;
                         fieldType?: undefined;
                         fields?: undefined;
-                        selectorFields?: undefined;
                         titleField?: undefined;
                         openMode?: undefined;
                         popupSize?: undefined;
@@ -2083,13 +2075,6 @@ declare const _default: {
                             };
                             description: string;
                         };
-                        selectorFields: {
-                            type: string;
-                            items: {
-                                type: string;
-                            };
-                            description: string;
-                        };
                         titleField: {
                             type: string;
                         };
@@ -3409,13 +3394,6 @@ declare const _default: {
                         };
                         description: string;
                     };
-                    selectorFields: {
-                        type: string;
-                        items: {
-                            type: string;
-                        };
-                        description: string;
-                    };
                     titleField: {
                         type: string;
                     };
@@ -3715,13 +3693,6 @@ declare const _default: {
                         };
                         description: string;
                     };
-                    selectorFields: {
-                        type: string;
-                        items: {
-                            type: string;
-                        };
-                        description: string;
-                    };
                     titleField: {
                         type: string;
                     };

package/dist/swagger/flow-surfaces.js

@@ -156,12 +156,7 @@ const RELATION_FIELD_TYPE_SCHEMA = {
 const RELATION_TARGET_FIELDS_SCHEMA = {
   type: "array",
   items: { type: "string" },
-  description: "Relation target record fields used as sub-table columns or embedded sub-form/detail fields."
-};
-const RELATION_SELECTOR_FIELDS_SCHEMA = {
-  type: "array",
-  items: { type: "string" },
-  description: "Record picker selector table fields. Do not mix with fields on the same field object."
+  description: "Relation target record fields. For picker fields, these become selector table columns; for nested relation fields, these become sub-table columns or embedded sub-form/detail fields."
 };
 const ADD_CHILD_TREE_TABLE_NOTE = "`addChild` is only valid when the live target `catalog.recordActions` exposes it, which normally means a table bound to a tree collection with `treeTable` enabled.";
 const APPLY_BLUEPRINT_ADD_CHILD_NOTE = "`addChild` is not auto-promoted from `actions`; author it only under `recordActions`, and only when the live target `catalog.recordActions` exposes it for a tree table.";
@@ -498,7 +493,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` / `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.'
+      '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` has the highest priority when targeting an existing menu group. If `routeId` is present, applyBlueprint ignores `title`, `icon`, `tooltip`, and `hideInMenu` on `navigation.group`; applyBlueprint create mode does not mutate existing group metadata, so callers should use `updateMenu` separately when that is required. When `routeId` is omitted and `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. Metadata such as `icon`, `tooltip`, and `hideInMenu` is used only when a new group is created and is ignored when an existing group is reused. `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,
@@ -838,7 +833,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. Relation fields can request a public `fieldType` such as `picker`, `subTable`, or `popupSubTable`, with optional flat `fields`, `selectorFields`, and `titleField`. Direct add does not accept raw `wrapperProps` / `fieldProps` / `props` / `decoratorProps` / `stepParams` / `flowRegistry` or internal field model keys. 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`."
+      "Automatically derives the wrapper/inner-field combination from the container use and the field interface. Relation fields can request a public `fieldType` such as `picker`, `subTable`, or `popupSubTable`, with optional flat `fields` and `titleField`. For picker fields, `fields` configures selector table columns; for nested relation fields, `fields` configures nested fields/columns. Direct add does not accept raw `wrapperProps` / `fieldProps` / `props` / `decoratorProps` / `stepParams` / `flowRegistry` or internal field model keys. 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,
@@ -2153,7 +2148,6 @@ const schemas = {
           },
           fieldType: RELATION_FIELD_TYPE_SCHEMA,
           fields: RELATION_TARGET_FIELDS_SCHEMA,
-          selectorFields: RELATION_SELECTOR_FIELDS_SCHEMA,
           titleField: { type: "string" },
           openMode: { type: "string", example: "drawer" },
           popupSize: { type: "string", example: "medium" },
@@ -3421,7 +3415,6 @@ const schemas = {
           type: { type: "string" },
           fieldType: RELATION_FIELD_TYPE_SCHEMA,
           fields: RELATION_TARGET_FIELDS_SCHEMA,
-          selectorFields: RELATION_SELECTOR_FIELDS_SCHEMA,
           titleField: { type: "string" },
           openMode: { type: "string", example: "drawer" },
           popupSize: { type: "string", example: "medium" },
@@ -3579,23 +3572,23 @@ const schemas = {
     properties: {
       routeId: {
         ...STRING_OR_INTEGER_SCHEMA,
-        description: "Preferred existing menu-group route id for exact targeting. Do not mix it with title/icon/tooltip/hideInMenu. applyBlueprint create mode does not mutate existing group metadata; use low-level updateMenu separately when needed."
+        description: "Preferred existing menu-group route id. When present, routeId has the highest priority and title/icon/tooltip/hideInMenu are ignored. applyBlueprint create mode does not mutate existing group metadata; use low-level updateMenu separately when needed."
       },
       title: {
         type: "string",
-        description: "Group title for create mode. When `routeId` is omitted, applyBlueprint reuses a same-title group if the match is unique, creates one when no group 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."
+        description: "Group title for create mode. When `routeId` is omitted, applyBlueprint reuses a same-title group if the match is unique, creates one when no group exists, and rejects ambiguous multi-match cases. If an existing group is reused, group metadata is ignored; use low-level updateMenu to change existing group metadata."
       },
       icon: {
         type: "string",
-        description: "Group icon used only when create mode actually creates a new menu group. Not allowed together with routeId."
+        description: "Group icon used only when create mode actually creates a new menu group. Ignored when routeId is present or when title resolves to an existing group."
       },
       tooltip: {
         type: "string",
-        description: "Group tooltip used only when create mode actually creates a new menu group. Not allowed together with routeId."
+        description: "Group tooltip used only when create mode actually creates a new menu group. Ignored when routeId is present or when title resolves to an existing group."
       },
       hideInMenu: {
         type: "boolean",
-        description: "Group hidden-state used only when create mode actually creates a new menu group. Not allowed together with routeId."
+        description: "Group hidden-state used only when create mode actually creates a new menu group. Ignored when routeId is present or when title resolves to an existing group."
       }
     },
     additionalProperties: false
@@ -4425,7 +4418,6 @@ const schemas = {
       },
       fieldType: RELATION_FIELD_TYPE_SCHEMA,
       fields: RELATION_TARGET_FIELDS_SCHEMA,
-      selectorFields: RELATION_SELECTOR_FIELDS_SCHEMA,
       titleField: { type: "string" },
       openMode: { type: "string", example: "drawer" },
       popupSize: { type: "string", example: "medium" },
@@ -4656,7 +4648,6 @@ const schemas = {
       },
       fieldType: RELATION_FIELD_TYPE_SCHEMA,
       fields: RELATION_TARGET_FIELDS_SCHEMA,
-      selectorFields: RELATION_SELECTOR_FIELDS_SCHEMA,
       titleField: { type: "string" },
       openMode: { type: "string", example: "drawer" },
       popupSize: { type: "string", example: "medium" },

package/dist/swagger/index.d.ts

@@ -129,13 +129,6 @@ declare const _default: {
                             };
                             description: string;
                         };
-                        selectorFields: {
-                            type: string;
-                            items: {
-                                type: string;
-                            };
-                            description: string;
-                        };
                         titleField: {
                             type: string;
                         };
@@ -197,7 +190,6 @@ declare const _default: {
                         fieldPath?: undefined;
                         fieldType?: undefined;
                         fields?: undefined;
-                        selectorFields?: undefined;
                         titleField?: undefined;
                         openMode?: undefined;
                         popupSize?: undefined;
@@ -2083,13 +2075,6 @@ declare const _default: {
                             };
                             description: string;
                         };
-                        selectorFields: {
-                            type: string;
-                            items: {
-                                type: string;
-                            };
-                            description: string;
-                        };
                         titleField: {
                             type: string;
                         };
@@ -3409,13 +3394,6 @@ declare const _default: {
                         };
                         description: string;
                     };
-                    selectorFields: {
-                        type: string;
-                        items: {
-                            type: string;
-                        };
-                        description: string;
-                    };
                     titleField: {
                         type: string;
                     };
@@ -3715,13 +3693,6 @@ declare const _default: {
                         };
                         description: string;
                     };
-                    selectorFields: {
-                        type: string;
-                        items: {
-                            type: string;
-                        };
-                        description: string;
-                    };
                     titleField: {
                         type: string;
                     };

package/package.json

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