The purpose of iPaas/low code platform is to allow citizen developer to built business applications for consumption by others using development and runtime environments sanctioned by corporate IT. A lot of the time these citizen developers might not have sufficient technical knowledge in a particular endpoints/3rd party systems and might requires step-to-step guide on achieving their goal.
After going through the webMethods.io guides, I do see there is a lack of how-to/step to step guides on connector/source to target system of guides available in the documentation.
It would be good if webMethods.io documentation also provides sufficient information on these as a guide to people who’s using webMethods.io platform to do such integration.
What you think the documentation of webMethods.io needs to further improve?
Hello,
When we make an integration flow in webMethods.io Integration platform and choose the option to invoke it over HTTP, it exposes it over the web using HTTP POST.
There is no way to change it to GET. In my use case i wanted to consume this end-point as a GET as it’s just a read only service to get data.
Please see if this can be improved. Expected behaviour is like what we have on webMethods on-prem IS, any service can be accessed via HTTP GET & POST depending upon input signature.
Hey Manoj, although from REST practices I understand that “GET” verb is recommended to invoke or provision read/get type of services, we can still achieve the same using POST too. In fact, using post we can send complex data structures as input to your READ service (if required) as opposed to URL Query Params via GET.
This query param restriction might be the primary reason why webMethods.io might have restricted the HTTP invocation to POST so that users can pass complex input data structures to services.
Hello Prasad,
I agree using POST we can achieve what GET does. However, my use case supports GET only and therefore thought about raising it as an improvement.
Use Case: Consume the integration developed as a data source in MashZone as a URL based Data Feed.
As a workaround, i developed a workflow with webhook as triggering point with sync response block sending the response.
I would suggest you to raise a support incident through Empower to SAG support to get R&D’s viewpoint against your use case, and also why they’ve such architecture design in wM.io. There should be a reason to that, and I’m pretty sure the R&D has done their investigation before they design it this way.
If you strongly believe that this is a valid use case, it’s also a good idea to just raise them through Brainstorm portal so that PM heard your voice and get back to you.
Did you tried API Development with Classic webMethods flow? This is also possible on webMethods.io Integration. This will let you develop with methods of your choice. For Even Driven use cases - use workflows, for Synchronous cases, API development cases use webMethods flows.
