From 9b8b94b1557f23abf046f6eb51b92df6fac730b9 Mon Sep 17 00:00:00 2001 From: MxTushar Date: Thu, 29 Oct 2026 13:15:31 +0530 Subject: [PATCH] Fix output variable naming format in documentation --- .../general/mendix-pipelines/configuring-post-get-steps.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/deployment/general/mendix-pipelines/configuring-post-get-steps.md b/content/en/docs/deployment/general/mendix-pipelines/configuring-post-get-steps.md index 879529eb9f3..11b7f02d9e8 100644 --- a/content/en/docs/deployment/general/mendix-pipelines/configuring-post-get-steps.md +++ b/content/en/docs/deployment/general/mendix-pipelines/configuring-post-get-steps.md @@ -162,8 +162,8 @@ Each output slot is populated by a [jq-style expression](https://jqlang.org/manu Output variables are automatically named and you cannot assign custom name or change the names. Mendix Pipelines exposes extracted values using a fixed naming pattern such as: -* `{{GET Request.Output_1}}` -* `{{POST Request.Output_2}}` +* `{{GET_Request.Output_1}}` +* `{{POST_Request.Output_2}}` {{% alert color="warning" %}} Mendix Pipelines does not validate whether an extraction expression matches the response, nor does it provide tooling to inspect the response structure interactively.