Skip to content

Conversation

@adeel2023
Copy link
Contributor

@adeel2023 adeel2023 commented Aug 20, 2025

Updates Limitations for Consumed Rest Service in refguids (10 and 11).
Executes action item from: https://mendix.atlassian.net/browse/REST-93

@aimiliatheologimendix
Copy link
Contributor

@quinntracy could you maybe take a look?

* It is currently not possible to configure parameters in the Query Parameters tab
* It is currently not possible to configure parameters in the Query Parameters tab.
* Streaming responses from APIs are currently not supported.
* Implicit response-mapping is performed only for responses with status code `200`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked the docs MR and I would also suggest something different I think, because we never mention the term implicit mapping in the docs. Another example can be:

When the Send REST request action is executed in a microflow and the statusCode is in 2xx range, but different than 200, you can use the latestHttpResponse to get the StatusCode and Content of the request that was made

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could these two points be combined? For example, "Implicit response mapping is performed only for responses with status code 200. If the Send REST request action is executed in a microflow and the status code is in 2xx range, but different than 200, use the latestHttpResponse to get the status code and response content."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They could be, but implicit mapping is not a term that the customer knows 🐒

We could combine them but maybe change the first sentence to: Response can be mapped in a microflow only for responses with status code 200. etc....

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh sorry, I misread! Yes, this should work. If you agree, I can update both docs with this and then get it merged today.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that would be great!

* To use the request response to create a data structure automatically in your domain model, the response data should be in JSON format. It is possible to process other formats, such as XML or raw text, but you will need to extract the data you are looking for in a microflow.
* It is currently not possible to configure parameters in the Query Parameters tab.
* Streaming responses from APIs are currently not supported.
* Implicit response-mapping is performed only for responses with status code `200`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as my comment above

@quinntracy quinntracy self-assigned this Aug 21, 2025
@quinntracy
Copy link
Collaborator

@aimiliatheologimendix No problem. Is this for the 11.2 release, or can it be merged after review?

@aimiliatheologimendix
Copy link
Contributor

@quinntracy this will be nice to get merged asap. It's not really related to a specific release but these are limitations that we found out adding them to the docs will help the users

@quinntracy quinntracy merged commit b84d460 into mendix:development Aug 21, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants