@nocobase/plugin-flow-engine 2.1.0-alpha.18 → 2.1.0-alpha.19

package/dist/swagger/flow-surfaces.js

@@ -30,6 +30,7 @@ __export(flow_surfaces_exports, {
 });
 module.exports = __toCommonJS(flow_surfaces_exports);
 var import_constants = require("../server/flow-surfaces/constants");
+var import_catalog_specs = require("../server/flow-surfaces/approval/catalog-specs");
 var import_flow_surfaces = require("./flow-surfaces.examples");
 var import_flow_surfaces2 = require("./flow-surfaces.template-action-docs");
 var import_flow_surfaces3 = require("./flow-surfaces.template-schemas");
@@ -45,7 +46,7 @@ const FILTER_GROUP_EXAMPLE = {
 const STRING_OR_INTEGER_SCHEMA = {
   oneOf: [{ type: "string" }, { type: "integer" }]
 };
-const ACTION_TYPE_ENUM = [
+const BASE_ACTION_TYPE_ENUM = [
   "filter",
   "addNew",
   "popup",
@@ -74,8 +75,10 @@ const ACTION_TYPE_ENUM = [
   "reset",
   "collapse"
 ];
-const APPLY_BLUEPRINT_ACTION_TYPE_ENUM = ACTION_TYPE_ENUM.filter((item) => item !== "addChild");
-const NON_RECORD_ACTION_TYPE_ENUM = [
+const ACTION_TYPE_ENUM = [...BASE_ACTION_TYPE_ENUM, ...import_catalog_specs.APPROVAL_ACTION_PUBLIC_KEYS];
+const APPLY_BLUEPRINT_ACTION_TYPE_ENUM = BASE_ACTION_TYPE_ENUM.filter((item) => item !== "addChild");
+const APPROVAL_BLUEPRINT_ACTION_TYPE_ENUM = [...import_catalog_specs.APPROVAL_ACTION_PUBLIC_KEYS];
+const BASE_NON_RECORD_ACTION_TYPE_ENUM = [
   "filter",
   "addNew",
   "popup",
@@ -98,6 +101,7 @@ const NON_RECORD_ACTION_TYPE_ENUM = [
   "reset",
   "collapse"
 ];
+const NON_RECORD_ACTION_TYPE_ENUM = [...BASE_NON_RECORD_ACTION_TYPE_ENUM, ...import_catalog_specs.APPROVAL_ACTION_PUBLIC_KEYS];
 const RECORD_ACTION_TYPE_ENUM = [
   "popup",
   "js",
@@ -125,12 +129,16 @@ const APPLY_BLUEPRINT_BLOCK_TYPE_ENUM = [
   "actionPanel",
   "jsBlock"
 ];
+const APPROVAL_BLUEPRINT_BLOCK_TYPE_ENUM = [...import_catalog_specs.APPROVAL_BLOCK_PUBLIC_KEYS];
+const COMPOSE_BLOCK_TYPE_ENUM = [...APPLY_BLUEPRINT_BLOCK_TYPE_ENUM, ...import_catalog_specs.APPROVAL_BLOCK_PUBLIC_KEYS];
 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.";
 const REACTION_FINGERPRINT_DESCRIPTION = "Optional optimistic-concurrency fingerprint from `getReactionMeta.capabilities[].fingerprint`. When provided, the write fails with HTTP 409 if the current slot fingerprint no longer matches.";
 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.";
 function ref(name) {
   return {
     $ref: `#/components/schemas/${name}`
@@ -225,6 +233,54 @@ function buildReactionWriteRequestSchema(ruleSchemaName) {
     additionalProperties: false
   };
 }
+function buildFlowSurfaceRequestPopupSchema() {
+  return {
+    type: "object",
+    anyOf: [
+      {
+        required: ["template"]
+      },
+      {
+        required: ["tryTemplate"]
+      },
+      {
+        required: ["defaultType"]
+      },
+      {
+        anyOf: [{ required: ["title"] }, { required: ["mode"] }, { required: ["blocks"] }, { required: ["layout"] }]
+      }
+    ],
+    properties: {
+      title: {
+        type: "string"
+      },
+      template: ref("FlowSurfaceRequestPopupTemplateRef"),
+      tryTemplate: {
+        type: "boolean",
+        description: REQUEST_POPUP_TRY_TEMPLATE_DESCRIPTION
+      },
+      defaultType: {
+        type: "string",
+        enum: ["view", "edit"],
+        description: "When popup content is omitted, asks the backend to prefer a compatible popup template first and otherwise auto-generate a default relation popup. Defaults to `view` for field popups."
+      },
+      saveAsTemplate: {
+        allOf: [ref("FlowSurfaceRequestPopupSaveAsTemplate")],
+        description: REQUEST_POPUP_SAVE_AS_TEMPLATE_DESCRIPTION
+      },
+      mode: {
+        type: "string",
+        enum: ["append", "replace"]
+      },
+      blocks: {
+        type: "array",
+        items: ref("FlowSurfaceComposeBlockSpec")
+      },
+      layout: ref("FlowSurfaceComposeLayout")
+    },
+    additionalProperties: false
+  };
+}
 function buildReactionWriteResultSchema(ruleSchemaName) {
   return {
     type: "object",
@@ -408,7 +464,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`. 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`. 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.'
     ),
     requestBody: {
       required: true,
@@ -431,12 +487,42 @@ const actionDocs = {
     },
     responses: responses("FlowSurfaceApplyBlueprintResponse")
   },
+  applyApprovalBlueprint: {
+    tags: [FLOW_SURFACES_TAG],
+    summary: "Apply an approval blueprint to initiator, approver, or task-card surfaces",
+    description: valuesCompatibilityNote(
+      "Builds workflow-approval configuration surfaces through the existing flowSurfaces orchestration layer instead of a separate approval resource. This is the preferred whole-surface bootstrap / replace entry for approval initiator, approver, and task-card UIs. Unlike route-backed `applyBlueprint`, this action targets approval-bound FlowModel roots stored on approval workflow trigger config (`workflow.config.approvalUid` / `workflow.config.taskCardUid`) or approval node config (`node.config.approvalUid` / `node.config.taskCardUid`). The backend creates or reuses the correct approval root automatically, rewrites the binding uid, applies a `replace` blueprint to that root, and reconciles approval runtime config derived from approval actions such as withdraw / approve / reject / return / delegate / add-assignee. `surface='initiator'` requires `workflowId` and writes page-like `blocks + layout` into `TriggerChildPageModel -> TriggerChildPageTabModel -> TriggerBlockGridModel`. `surface='approver'` requires `nodeId` and writes page-like `blocks + layout` into `ApprovalChildPageModel -> ApprovalChildPageTabModel -> ApprovalBlockGridModel`. `surface='taskCard'` requires exactly one of `workflowId` or `nodeId` and writes `fields + layout` into `ApplyTaskCardDetailsModel` or `ApprovalTaskCardDetailsModel`. This v1 action does not cover legacy schema-config wiring; it focuses on approval FlowModel construction, binding persistence, and approval runtime-config synchronization. When `layout` is omitted, the backend generates a simple top-to-bottom layout for the resulting blocks or fields."
+    ),
+    requestBody: {
+      required: true,
+      content: {
+        "application/json": {
+          schema: ref("FlowSurfaceApplyApprovalBlueprintRequest"),
+          examples: {
+            initiator: {
+              summary: "Replace an approval initiator surface on the workflow trigger",
+              value: import_flow_surfaces.flowSurfaceExamples.applyApprovalBlueprintInitiator
+            },
+            approver: {
+              summary: "Replace an approval approver surface on one approval node",
+              value: import_flow_surfaces.flowSurfaceExamples.applyApprovalBlueprintApprover
+            },
+            taskCard: {
+              summary: "Replace an approval task-card surface on one approval node",
+              value: import_flow_surfaces.flowSurfaceExamples.applyApprovalBlueprintTaskCard
+            }
+          }
+        }
+      }
+    },
+    responses: responses("FlowSurfaceApplyApprovalBlueprintResponse")
+  },
   ...templateActionDocs,
   compose: {
     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`. 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.'
+      '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.'
     ),
     requestBody: {
       required: true,
@@ -482,7 +568,7 @@ const actionDocs = {
     tags: [FLOW_SURFACES_TAG],
     summary: "Apply simple semantic changes to a page, tab, block, field or action",
     description: valuesCompatibilityNote(
-      "Uses simple `changes` to update high-frequency settings such as page/tab titles, table pageSize, field clickToOpen, and action openView/confirm without requiring the caller to know internal paths. For advanced reaction authoring, prefer `getReactionMeta` + `set*Rules`; the raw `assignRules` / `linkageRules` examples here are compatibility-only. Check `catalog.node.configureOptions` together with the relevant catalog item `configureOptions` before calling this action."
+      "Uses simple `changes` to update high-frequency settings such as page/tab titles, table pageSize, field clickToOpen, and action openView/confirm without requiring the caller to know internal paths. For advanced reaction authoring, prefer `getReactionMeta` + `set*Rules`; the raw `assignRules` / `linkageRules` examples here are compatibility-only. Check `catalog.node.configureOptions` together with the relevant catalog item `configureOptions` before calling this action. On approval action nodes, this route also accepts approval-specific keys such as `approvalReturn` and `assigneesScope`, and flowSurfaces persists the matching approval runtime config. It does not replace `applyApprovalBlueprint` for whole-surface approval bootstrap."
     ),
     requestBody: {
       required: true,
@@ -676,7 +762,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`.'
+      '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.'
     ),
     requestBody: {
       required: true,
@@ -710,7 +796,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. 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."
+      "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`."
     ),
     requestBody: {
       required: true,
@@ -737,6 +823,18 @@ const actionDocs = {
             popupTemplate: {
               summary: "Create a bound field that reuses a saved popup template",
               value: import_flow_surfaces.flowSurfaceExamples.addFieldPopupTemplate
+            },
+            autoPopupTemplate: {
+              summary: "Create a bound field and let the backend auto-select a compatible popup template",
+              value: import_flow_surfaces.flowSurfaceExamples.addFieldAutoPopupTemplate
+            },
+            defaultEditPopup: {
+              summary: "Create a relation field and let the backend auto-complete a default edit popup when no explicit popup content is provided",
+              value: import_flow_surfaces.flowSurfaceExamples.addFieldDefaultEditPopup
+            },
+            savePopupTemplate: {
+              summary: "Create a bound field and immediately save its explicit local popup as a popup template",
+              value: import_flow_surfaces.flowSurfaceExamples.addFieldSavePopupTemplate
             }
           }
         }
@@ -748,7 +846,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. When `popup.template` is present, `popup.title` still applies, while local `popup.mode` / `popup.blocks` / `popup.layout` are accepted but ignored."
+      "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."
     ),
     requestBody: {
       required: true,
@@ -771,6 +869,14 @@ const actionDocs = {
             jsItem: {
               summary: "Create a form JS item action under a create/edit/form action container",
               value: import_flow_surfaces.flowSurfaceExamples.addJsItemAction
+            },
+            autoPopupTemplate: {
+              summary: "Create a popup-capable action and let the backend auto-select a compatible popup template",
+              value: import_flow_surfaces.flowSurfaceExamples.addAutoPopupAction
+            },
+            savePopupTemplate: {
+              summary: "Create a popup-capable action and immediately save its explicit local popup as a popup template",
+              value: import_flow_surfaces.flowSurfaceExamples.addSavePopupAction
             }
           }
         }
@@ -782,7 +888,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. 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. \`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.`
     ),
     requestBody: {
       required: true,
@@ -801,6 +907,14 @@ const actionDocs = {
             js: {
               summary: "Create a JS record action under a details block owner target",
               value: import_flow_surfaces.flowSurfaceExamples.addRecordJsAction
+            },
+            autoPopupTemplate: {
+              summary: "Create a view/edit-like record action and let the backend auto-select a compatible popup template",
+              value: import_flow_surfaces.flowSurfaceExamples.addRecordAutoPopupTemplate
+            },
+            savePopupTemplate: {
+              summary: "Create a view/edit-like record action and immediately save its explicit local popup as a popup template",
+              value: import_flow_surfaces.flowSurfaceExamples.addRecordSavePopupTemplate
             }
           }
         }
@@ -821,7 +935,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. 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. `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`."
     ),
     requestBody: requestBody("FlowSurfaceAddFieldsRequest", import_flow_surfaces.flowSurfaceExamples.addFields),
     responses: responses("FlowSurfaceAddFieldsResult")
@@ -830,7 +944,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. 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. `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`."
     ),
     requestBody: requestBody("FlowSurfaceAddActionsRequest", import_flow_surfaces.flowSurfaceExamples.addActions),
     responses: responses("FlowSurfaceAddActionsResult")
@@ -839,7 +953,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. 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. \`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\`.`
     ),
     requestBody: {
       required: true,
@@ -1586,6 +1700,7 @@ const schemas = {
       use: {
         type: "string"
       },
+      popup: ref("FlowSurfaceApplyNodePopup"),
       props: ANY_OBJECT_SCHEMA,
       decoratorProps: ANY_OBJECT_SCHEMA,
       stepParams: ANY_OBJECT_SCHEMA,
@@ -1605,9 +1720,26 @@ const schemas = {
     },
     additionalProperties: false
   },
+  FlowSurfaceApplyNodePopup: {
+    type: "object",
+    properties: {
+      template: ref("FlowSurfacePopupTemplateRef"),
+      tryTemplate: {
+        type: "boolean",
+        description: "Apply-only popup shortcut for popup-capable field/action child nodes. When true and no explicit template is provided, the backend tries the same auto-selection rule as add/compose popup inputs."
+      },
+      defaultType: {
+        type: "string",
+        enum: ["view", "edit"],
+        description: "When popup content is omitted, asks the backend to prefer a compatible popup template first and otherwise auto-generate a default relation popup of the requested type."
+      }
+    },
+    additionalProperties: false
+  },
   FlowSurfaceApplySpec: {
     type: "object",
     properties: {
+      popup: ref("FlowSurfaceApplyNodePopup"),
       props: ANY_OBJECT_SCHEMA,
       decoratorProps: ANY_OBJECT_SCHEMA,
       stepParams: ANY_OBJECT_SCHEMA,
@@ -1969,7 +2101,7 @@ const schemas = {
             description: "Reference to another compose block key, typically used by filter-form fields."
           },
           settings: ANY_OBJECT_SCHEMA,
-          popup: ref("FlowSurfaceComposeFieldPopup")
+          popup: ref("FlowSurfaceComposeRequestFieldPopup")
         },
         additionalProperties: false
       },
@@ -2031,18 +2163,88 @@ const schemas = {
   FlowSurfacePopupTemplateRef: {
     allOf: [ref("FlowSurfaceTemplateRef")]
   },
+  FlowSurfacePopupSaveAsTemplate: {
+    type: "object",
+    required: ["name", "description"],
+    properties: {
+      name: {
+        type: "string",
+        description: "Template name saved immediately from explicit local popup content."
+      },
+      description: {
+        type: "string",
+        description: "Template description saved immediately from explicit local popup content."
+      }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceRequestPopupTemplateRef: {
+    type: "object",
+    oneOf: [{ required: ["uid"] }, { required: ["local"] }],
+    properties: {
+      uid: {
+        type: "string",
+        description: "Saved template uid."
+      },
+      local: {
+        type: "string",
+        description: "Request-scoped popup template alias produced earlier by `popup.saveAsTemplate.local` in the same compose/applyBlueprint call. The alias itself is not persisted."
+      },
+      mode: {
+        type: "string",
+        enum: ["reference", "copy"],
+        default: "reference"
+      }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceRequestPopupSaveAsTemplate: {
+    type: "object",
+    required: ["name", "description"],
+    properties: {
+      name: {
+        type: "string",
+        description: "Template name saved immediately from explicit local popup content."
+      },
+      description: {
+        type: "string",
+        description: "Template description saved immediately from explicit local popup content."
+      },
+      local: {
+        type: "string",
+        description: "Optional request-scoped alias that later `popup.template.local` references can consume within the same compose/applyBlueprint call. The alias itself is not persisted."
+      }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceComposeRequestActionPopup: buildFlowSurfaceRequestPopupSchema(),
+  FlowSurfaceComposeRequestFieldPopup: buildFlowSurfaceRequestPopupSchema(),
   FlowSurfaceComposeActionPopup: {
     type: "object",
-    oneOf: [
+    anyOf: [
       {
         required: ["template"]
       },
       {
-        anyOf: [{ required: ["mode"] }, { required: ["blocks"] }, { required: ["layout"] }]
+        required: ["tryTemplate"]
+      },
+      {
+        anyOf: [{ required: ["title"] }, { required: ["mode"] }, { required: ["blocks"] }, { required: ["layout"] }]
       }
     ],
     properties: {
+      title: {
+        type: "string"
+      },
       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."
+      },
+      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`."
+      },
       mode: {
         type: "string",
         enum: ["append", "replace"]
@@ -2057,16 +2259,38 @@ const schemas = {
   },
   FlowSurfaceComposeFieldPopup: {
     type: "object",
-    oneOf: [
+    anyOf: [
       {
         required: ["template"]
       },
       {
-        anyOf: [{ required: ["mode"] }, { required: ["blocks"] }, { required: ["layout"] }]
+        required: ["tryTemplate"]
+      },
+      {
+        required: ["defaultType"]
+      },
+      {
+        anyOf: [{ required: ["title"] }, { required: ["mode"] }, { required: ["blocks"] }, { required: ["layout"] }]
       }
     ],
     properties: {
+      title: {
+        type: "string"
+      },
       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."
+      },
+      defaultType: {
+        type: "string",
+        enum: ["view", "edit"],
+        description: "When popup content is omitted, the backend prefers a compatible popup template first and otherwise auto-generates a default relation popup of the requested type."
+      },
+      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`."
+      },
       mode: {
         type: "string",
         enum: ["append", "replace"]
@@ -2096,6 +2320,30 @@ const schemas = {
             enum: NON_RECORD_ACTION_TYPE_ENUM
           },
           settings: ANY_OBJECT_SCHEMA,
+          popup: ref("FlowSurfaceComposeRequestActionPopup")
+        },
+        additionalProperties: false
+      }
+    ]
+  },
+  FlowSurfaceApprovalBlueprintActionSpec: {
+    oneOf: [
+      {
+        type: "string",
+        enum: APPROVAL_BLUEPRINT_ACTION_TYPE_ENUM
+      },
+      {
+        type: "object",
+        required: ["type"],
+        properties: {
+          key: {
+            type: "string"
+          },
+          type: {
+            type: "string",
+            enum: APPROVAL_BLUEPRINT_ACTION_TYPE_ENUM
+          },
+          settings: ANY_OBJECT_SCHEMA,
           popup: ref("FlowSurfaceComposeActionPopup")
         },
         additionalProperties: false
@@ -2119,7 +2367,7 @@ const schemas = {
             enum: RECORD_ACTION_TYPE_ENUM
           },
           settings: ANY_OBJECT_SCHEMA,
-          popup: ref("FlowSurfaceComposeActionPopup")
+          popup: ref("FlowSurfaceComposeRequestActionPopup")
         },
         additionalProperties: false
       }
@@ -2135,20 +2383,7 @@ const schemas = {
       },
       type: {
         type: "string",
-        enum: [
-          "table",
-          "createForm",
-          "editForm",
-          "details",
-          "filterForm",
-          "list",
-          "gridCard",
-          "markdown",
-          "iframe",
-          "chart",
-          "actionPanel",
-          "jsBlock"
-        ]
+        enum: COMPOSE_BLOCK_TYPE_ENUM
       },
       template: ref("FlowSurfaceBlockTemplateRef"),
       resource: ref("FlowSurfaceBlockResourceInput"),
@@ -2170,6 +2405,30 @@ const schemas = {
     },
     additionalProperties: false
   },
+  FlowSurfaceApprovalBlueprintBlockSpec: {
+    type: "object",
+    required: ["key", "type"],
+    properties: {
+      key: {
+        type: "string"
+      },
+      type: {
+        type: "string",
+        enum: APPROVAL_BLUEPRINT_BLOCK_TYPE_ENUM
+      },
+      resource: ref("FlowSurfaceBlockResourceInput"),
+      settings: ANY_OBJECT_SCHEMA,
+      fields: {
+        type: "array",
+        items: ref("FlowSurfaceComposeFieldSpec")
+      },
+      actions: {
+        type: "array",
+        items: ref("FlowSurfaceApprovalBlueprintActionSpec")
+      }
+    },
+    additionalProperties: false
+  },
   FlowSurfaceComposeRequest: {
     type: "object",
     required: ["target"],
@@ -2281,20 +2540,7 @@ const schemas = {
       },
       type: {
         type: "string",
-        enum: [
-          "table",
-          "createForm",
-          "editForm",
-          "details",
-          "filterForm",
-          "list",
-          "gridCard",
-          "markdown",
-          "iframe",
-          "chart",
-          "actionPanel",
-          "jsBlock"
-        ]
+        enum: COMPOSE_BLOCK_TYPE_ENUM
       },
       uid: {
         type: "string"
@@ -3053,7 +3299,20 @@ const schemas = {
         type: "string",
         enum: ["append", "replace"]
       },
-      template: ref("FlowSurfacePopupTemplateRef"),
+      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."
+      },
+      defaultType: {
+        type: "string",
+        enum: ["view", "edit"],
+        description: "When popup content is omitted, applyBlueprint prefers a compatible popup template first and otherwise auto-generates a default relation popup of the requested type."
+      },
+      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."
+      },
       blocks: {
         type: "array",
         description: "Inline popup blocks. For custom `edit` popups, provide exactly one `editForm` block plus any optional sibling blocks.",
@@ -3336,6 +3595,87 @@ const schemas = {
     },
     additionalProperties: false
   },
+  FlowSurfaceApprovalBlueprintSurface: {
+    type: "string",
+    enum: ["initiator", "approver", "taskCard"]
+  },
+  FlowSurfaceApplyApprovalBlueprintBinding: {
+    type: "object",
+    required: ["resourceName", "filterByTk", "configPath"],
+    properties: {
+      resourceName: {
+        type: "string",
+        enum: ["workflows", "flow_nodes"]
+      },
+      filterByTk: STRING_OR_INTEGER_SCHEMA,
+      configPath: {
+        type: "string"
+      }
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyApprovalBlueprintTarget: {
+    type: "object",
+    required: ["uid"],
+    properties: {
+      uid: {
+        type: "string"
+      },
+      workflowId: STRING_OR_INTEGER_SCHEMA,
+      nodeId: STRING_OR_INTEGER_SCHEMA
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyApprovalBlueprintRequest: {
+    type: "object",
+    required: ["surface"],
+    description: "Simplified approval-surface blueprint request for workflow approval UIs. This is the preferred bootstrap / replace route for approval initiator, approver, and task-card surfaces. `version` may be omitted and defaults to '1'. `mode` may be omitted and defaults to `replace`; v1 only supports `replace`. Runtime validation enforces binding rules: `initiator` requires `workflowId`, `approver` requires `nodeId`, and `taskCard` requires exactly one of `workflowId` or `nodeId`. Page-like surfaces (`initiator`, `approver`) accept `blocks + layout`; `taskCard` accepts `fields + layout`. This route does not perform schema wiring, but it does persist binding fields and reconcile approval runtime config from approval actions.",
+    properties: {
+      version: {
+        type: "string",
+        enum: ["1"]
+      },
+      mode: {
+        type: "string",
+        enum: ["replace"],
+        default: "replace"
+      },
+      surface: ref("FlowSurfaceApprovalBlueprintSurface"),
+      workflowId: STRING_OR_INTEGER_SCHEMA,
+      nodeId: STRING_OR_INTEGER_SCHEMA,
+      blocks: {
+        type: "array",
+        items: ref("FlowSurfaceApprovalBlueprintBlockSpec"),
+        description: "Page-like approval content for `initiator` and `approver` surfaces."
+      },
+      fields: {
+        type: "array",
+        items: ref("FlowSurfaceComposeFieldSpec"),
+        description: "Task-card field list for `taskCard` surfaces."
+      },
+      layout: ref("FlowSurfaceComposeLayout")
+    },
+    additionalProperties: false
+  },
+  FlowSurfaceApplyApprovalBlueprintResponse: {
+    type: "object",
+    required: ["version", "mode", "surfaceType", "target", "binding", "surface"],
+    properties: {
+      version: {
+        type: "string",
+        enum: ["1"]
+      },
+      mode: {
+        type: "string",
+        enum: ["replace"]
+      },
+      surfaceType: ref("FlowSurfaceApprovalBlueprintSurface"),
+      target: ref("FlowSurfaceApplyApprovalBlueprintTarget"),
+      binding: ref("FlowSurfaceApplyApprovalBlueprintBinding"),
+      surface: ref("FlowSurfaceGetResponse")
+    },
+    additionalProperties: false
+  },
   FlowSurfaceConfigureRequest: {
     type: "object",
     required: ["target", "changes"],
@@ -3809,20 +4149,7 @@ const schemas = {
       target: ref("FlowSurfaceWriteTarget"),
       type: {
         type: "string",
-        enum: [
-          "table",
-          "createForm",
-          "editForm",
-          "details",
-          "filterForm",
-          "list",
-          "gridCard",
-          "markdown",
-          "iframe",
-          "chart",
-          "actionPanel",
-          "jsBlock"
-        ]
+        enum: COMPOSE_BLOCK_TYPE_ENUM
       },
       use: {
         type: "string"
@@ -4086,20 +4413,7 @@ const schemas = {
       },
       type: {
         type: "string",
-        enum: [
-          "table",
-          "createForm",
-          "editForm",
-          "details",
-          "filterForm",
-          "list",
-          "gridCard",
-          "markdown",
-          "iframe",
-          "chart",
-          "actionPanel",
-          "jsBlock"
-        ]
+        enum: COMPOSE_BLOCK_TYPE_ENUM
       },
       use: {
         type: "string"