@celigo/api-specs 0.2.231 → 0.2.232

package/dist/api.yml

@@ -13486,6 +13486,14 @@ components:
             - |-
               VAN mailbox identifier. Identifies the specific mailbox on the VAN provider
               that this connection sends to and receives from.
+            - |-
+              Never ask the user for a mailbox id or send one. Creating a VAN connection creates its
+              ECGrid mailbox and account (the VAN provider's portal) during the save and stores the
+              id here; the integrator.io account owner then receives the ECGrid login and setup steps
+              by email (EDI ID, trading partnership, AS2 test) — those steps configure the mailbox,
+              they do not produce the id. There is no provisioning wait: an empty value on a saved
+              connection is a connection with no mailbox attached, which is a Celigo Support
+              question, not a delay that resolves on its own.
         contentBasedFlowRouter:
           type: object
           description: |-

package/dist/connection.yml

@@ -9298,6 +9298,14 @@ components:
             - |-
               VAN mailbox identifier. Identifies the specific mailbox on the VAN provider
               that this connection sends to and receives from.
+            - |-
+              Never ask the user for a mailbox id or send one. Creating a VAN connection creates its
+              ECGrid mailbox and account (the VAN provider's portal) during the save and stores the
+              id here; the integrator.io account owner then receives the ECGrid login and setup steps
+              by email (EDI ID, trading partnership, AS2 test) — those steps configure the mailbox,
+              they do not produce the id. There is no provisioning wait: an empty value on a saved
+              connection is a connection with no mailbox attached, which is a Celigo Support
+              question, not a delay that resolves on its own.
         contentBasedFlowRouter:
           type: object
           description: |-

package/dist/enduser.yml

@@ -7323,6 +7323,14 @@ components:
             - |-
               VAN mailbox identifier. Identifies the specific mailbox on the VAN provider
               that this connection sends to and receives from.
+            - |-
+              Never ask the user for a mailbox id or send one. Creating a VAN connection creates its
+              ECGrid mailbox and account (the VAN provider's portal) during the save and stores the
+              id here; the integrator.io account owner then receives the ECGrid login and setup steps
+              by email (EDI ID, trading partnership, AS2 test) — those steps configure the mailbox,
+              they do not produce the id. There is no provisioning wait: an empty value on a saved
+              connection is a connection with no mailbox attached, which is a Celigo Support
+              question, not a delay that resolves on its own.
         contentBasedFlowRouter:
           type: object
           description: |-

package/dist/import.yml

@@ -9217,8 +9217,11 @@ components:
                   page's own text was valid.
                 - |-
                   The template renders against the page whatever `http.batchSize` says, and `http.body`
-                  plays no part in the file's content. The field's editor Preview does not run the
-                  generator, so judge the body by a run.
+                  plays no part in the file's content. The field's editor Preview renders the template
+                  against one sample page and uploads nothing, and warns — without blocking the save —
+                  when the template has no `{{#each batch_of_records}}` loop and when the evaluated
+                  text is not valid JSON; it does not run the page-combining generator, so how pages
+                  join under `aggregation.type: all` shows only in a flow run.
             resourcePath:
               type: string
               description: JSONPath expression to locate records within the JSON structure.
@@ -9249,13 +9252,18 @@ components:
                   scope (`batch_of_records.0.record.<field>` is the first record when a header needs
                   it). A body with no loop is rendered whole once per page — `<root>{{record.id}}</root>`
                   becomes `<root></root>` per page — and under `aggregation.type: all` the pages are
-                  concatenated into one multi-root file (`<root></root><root></root>`); the import
-                  form does not let a one-file-per-run XML template without an each block save,
-                  while an API save writes that file.
+                  concatenated into one multi-root file (`<root></root><root></root>`); for a
+                  one-file-per-run XML template without an each block the editor's Preview shows an
+                  error in place of its output, but the form still saves the template and the run
+                  writes that file — an API save never sees the check.
                 - |-
                   The template renders against the page whatever `http.batchSize` says, and on an
                   HTTP file-provider import `http.body` plays no part in the file's content. The
-                  field's editor Preview does not run the generator, so judge the body by a run.
+                  field's editor Preview renders the template against one sample page and uploads
+                  nothing, and warns — without blocking the save — when a one-file-per-page template
+                  has no record loop (the one-file-per-run case is the error above) and when the
+                  evaluated text is not valid XML; it does not run the page-combining generator, so
+                  how pages join under `aggregation.type: all` shows only in a flow run.
                 - |-
                   Saving `type: xml` without this field fails with 422 `missing_required_field`
                   ("required field, file.xml.body is missing.").

package/dist/mcp-server.yml

@@ -10371,6 +10371,14 @@ components:
             - |-
               VAN mailbox identifier. Identifies the specific mailbox on the VAN provider
               that this connection sends to and receives from.
+            - |-
+              Never ask the user for a mailbox id or send one. Creating a VAN connection creates its
+              ECGrid mailbox and account (the VAN provider's portal) during the save and stores the
+              id here; the integrator.io account owner then receives the ECGrid login and setup steps
+              by email (EDI ID, trading partnership, AS2 test) — those steps configure the mailbox,
+              they do not produce the id. There is no provisioning wait: an empty value on a saved
+              connection is a connection with no mailbox attached, which is a Celigo Support
+              question, not a delay that resolves on its own.
         contentBasedFlowRouter:
           type: object
           description: |-

package/dist/tool.yml

@@ -12853,6 +12853,14 @@ components:
             - |-
               VAN mailbox identifier. Identifies the specific mailbox on the VAN provider
               that this connection sends to and receives from.
+            - |-
+              Never ask the user for a mailbox id or send one. Creating a VAN connection creates its
+              ECGrid mailbox and account (the VAN provider's portal) during the save and stores the
+              id here; the integrator.io account owner then receives the ECGrid login and setup steps
+              by email (EDI ID, trading partnership, AS2 test) — those steps configure the mailbox,
+              they do not produce the id. There is no provisioning wait: an empty value on a saved
+              connection is a connection with no mailbox attached, which is a Celigo Support
+              question, not a delay that resolves on its own.
         contentBasedFlowRouter:
           type: object
           description: |-
@@ -21257,8 +21265,11 @@ components:
                   page's own text was valid.
                 - |-
                   The template renders against the page whatever `http.batchSize` says, and `http.body`
-                  plays no part in the file's content. The field's editor Preview does not run the
-                  generator, so judge the body by a run.
+                  plays no part in the file's content. The field's editor Preview renders the template
+                  against one sample page and uploads nothing, and warns — without blocking the save —
+                  when the template has no `{{#each batch_of_records}}` loop and when the evaluated
+                  text is not valid JSON; it does not run the page-combining generator, so how pages
+                  join under `aggregation.type: all` shows only in a flow run.
             resourcePath:
               type: string
               description: JSONPath expression to locate records within the JSON structure.
@@ -21289,13 +21300,18 @@ components:
                   scope (`batch_of_records.0.record.<field>` is the first record when a header needs
                   it). A body with no loop is rendered whole once per page — `<root>{{record.id}}</root>`
                   becomes `<root></root>` per page — and under `aggregation.type: all` the pages are
-                  concatenated into one multi-root file (`<root></root><root></root>`); the import
-                  form does not let a one-file-per-run XML template without an each block save,
-                  while an API save writes that file.
+                  concatenated into one multi-root file (`<root></root><root></root>`); for a
+                  one-file-per-run XML template without an each block the editor's Preview shows an
+                  error in place of its output, but the form still saves the template and the run
+                  writes that file — an API save never sees the check.
                 - |-
                   The template renders against the page whatever `http.batchSize` says, and on an
                   HTTP file-provider import `http.body` plays no part in the file's content. The
-                  field's editor Preview does not run the generator, so judge the body by a run.
+                  field's editor Preview renders the template against one sample page and uploads
+                  nothing, and warns — without blocking the save — when a one-file-per-page template
+                  has no record loop (the one-file-per-run case is the error above) and when the
+                  evaluated text is not valid XML; it does not run the page-combining generator, so
+                  how pages join under `aggregation.type: all` shows only in a flow run.
                 - |-
                   Saving `type: xml` without this field fails with 422 `missing_required_field`
                   ("required field, file.xml.body is missing.").

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.231",
+  "version": "0.2.232",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "854c2367",
+		"iasCommit": "fb204127",
 		"generatedAt": "2026-11-04"
 	},
 	"roots": {