Parametrize HTTP request method and endpoint in web connection process action?

Question

Hi all,

I’m using the web connection process action to interact with a third party API.

There are two issues I run into:

“Path” is a fixed property, requiring me to define many endpoints for the web connection;
“Method” is a fixed property for the endpoint, but not part of the key for that record. It does not allow multiple methods per endpoint.

For the path there are two ways I tried to work around this:

defining “Path” as {path} in order to turn it into a parameter
defining `url_path` as a parameter to the web connection.

The method is a domain with elements in the endpoint definition, not allowing to enter {method} as “Method”. I did define `http_request_method` as parameter to the web connection.

I was not able to get either option to work as I intended.

Does the web connection process action support this kind of abstraction? Should I model this as a custom / message protocol independent flow?

Boudewijn-202 · Accepted Answer

Is there a workaround that would allow me to use a web connection for a specific end, for a POST as well for a DELETE action?

My previously prepared post got lost in a Windows surprise reboot :-(

TL;DR:

I conflated endpoint name with endpoint path
Creating an identical endpoint with a new name allowed me to set the same endpoint path with an alternative HTTP request method

This solves my primary problem of alternate actions per endpoint.

Nathan · Answer

​Hi ​@Boudewijn-202,To echo your findings back at you; the Web Connection process action operates based on a structuredmodel-driven approach thatdoes not allow dynamic overriding of the http methods, and it also does notallow the complete replacement of the path via parameters, although it does supports parameterizing path segments with variable syntax. To use this as intended, you will need to use multiple explicitly configured endpoints. I had a look to see if anyone else was experiencing similar issues as you to gauge if there is a possible need here, but compared to other community posts, your request is more unique.You could use a workaround such as using the HTTP connector, or whichever other workaround gets the job done if the dynamic nature of your solution is absolutely necessary and the rigidness of the Web Connection model blocks you from meeting your integration requirements, but I must add that its recommended to use Web Connection action over the HTTP Connector as it has some mentioned benefits:Process flow connectors | Thinkwise DocumentationI hope this helps​

Sign up

Login to the Thinkwise Software Community

Scanning file for viruses.

This file cannot be downloaded