@celigo/api-specs 0.2.199 → 0.2.200

package/dist/import.yml

@@ -4160,10 +4160,17 @@ components:
                       - string
                       - 'null'
                     description: |
-                      Path in the source record to extract the value from.
-                      Use dot notation for nested fields (e.g., "address.city").
-                      The platform stores `null` here on fields driven by
-                      `hardCodedValue` instead of an extract path.
+                      Path in the source record to extract the value from, in
+                      dot notation for nested fields (e.g., "address.city").
+                      A bare string is always read as a path, never as a
+                      constant — a path that matches no field sets the
+                      destination field to an empty string (""), written,
+                      not omitted and not the path text, and `discardIfEmpty`
+                      is what skips it; constants belong in `hardCodedValue`,
+                      and the platform stores `null` here on fields driven by
+                      it. A Handlebars template (contains `{{`) reads the
+                      record's fields by bare name; `{{record.<field>}}`
+                      renders an empty string, not the value.
                     examples:
                       - address.city
                   generate:
@@ -4410,9 +4417,14 @@ components:
                             Path from the source record root that produces
                             the value for this sublist column. Paths are
                             always anchored at the source record root —
-                            never relative to a pre-iterated row. The
+                            never relative to a pre-iterated row — and a
+                            bare string is always read as a path, never as a
+                            constant: a path that matches no field leaves the
+                            column absent from every line (unlike a body
+                            field, which is set to ""), never the text
+                            itself. Constants belong in `hardCodedValue`; the
                             platform stores `null` here on fields driven by
-                            `hardCodedValue` instead of an extract path.
+                            it.
                           x-celigo-ai-guidance:
                             - |-
                               Two extract patterns, often mixed in the same

package/dist/tool.yml

@@ -16229,10 +16229,17 @@ components:
                       - string
                       - 'null'
                     description: |
-                      Path in the source record to extract the value from.
-                      Use dot notation for nested fields (e.g., "address.city").
-                      The platform stores `null` here on fields driven by
-                      `hardCodedValue` instead of an extract path.
+                      Path in the source record to extract the value from, in
+                      dot notation for nested fields (e.g., "address.city").
+                      A bare string is always read as a path, never as a
+                      constant — a path that matches no field sets the
+                      destination field to an empty string (""), written,
+                      not omitted and not the path text, and `discardIfEmpty`
+                      is what skips it; constants belong in `hardCodedValue`,
+                      and the platform stores `null` here on fields driven by
+                      it. A Handlebars template (contains `{{`) reads the
+                      record's fields by bare name; `{{record.<field>}}`
+                      renders an empty string, not the value.
                     examples:
                       - address.city
                   generate:
@@ -16479,9 +16486,14 @@ components:
                             Path from the source record root that produces
                             the value for this sublist column. Paths are
                             always anchored at the source record root —
-                            never relative to a pre-iterated row. The
+                            never relative to a pre-iterated row — and a
+                            bare string is always read as a path, never as a
+                            constant: a path that matches no field leaves the
+                            column absent from every line (unlike a body
+                            field, which is set to ""), never the text
+                            itself. Constants belong in `hardCodedValue`; the
                             platform stores `null` here on fields driven by
-                            `hardCodedValue` instead of an extract path.
+                            it.
                           x-celigo-ai-guidance:
                             - |-
                               Two extract patterns, often mixed in the same

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "3676e0c6",
-		"generatedAt": "2026-10-27"
+		"iasCommit": "72f30fe4",
+		"generatedAt": "2026-10-28"
 	},
 	"roots": {
 		"aiagent": 128,