Skip to content

Fix output variable naming format in documentation #12154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NicoletaComan merged 1 commit into from
Oct 29, 2026
Merged

Fix output variable naming format in documentation #12154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/deployment/general/mendix-pipelines/configuring-post-get-steps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading