Http POST method

RE: Http POST method

Tier1app — Tue, 24 Sep 2019 10:52:12 GMT

Hi all,

As part of continuous integration it’s highly encouraged to execute performance tests. Thread dumps/GC Logs should be captured and it can be analyzed using the API. If API reports any problems, then build can be failed. In this way, you can catch the performance degradation right during code commit time instead of catching it in performance labs or production.

Please have a look here: How to invoke Garbage collection log analysis API?

RE: Http POST method

Arun Theja Muthyalu — Tue, 07 Nov 2017 22:06:58 GMT

Hi xingc,

When you use HTTP Query Smart Service to communicate with another system, you are actually making a HTTP Transaction in the background which contains a Request and a Response.

To put it simply, Headers are nothing key value pairs which gives information about the data that you are sending in the request(or the data that you are receiving in the response). For example, the most commonly used header field, "Content-Type", tells about the type of the data(XML/Json/Text/etc.,) that you are sending in the Request(or receiving in the Response).

a!httpWrite() returns the Writer and that is why it should be used with the bind() function. Because bind() lets you bind a getter and setter rule or function to a variable such that when that variable is read, the getter method is called and when it is saved into, the writer returned by the setter method is called. Please go through the below link for further information.

docs.appian.com/.../fnc_evaluation_bind.html

Hope this answers your questions.

Thank you,
Arun

RE: Http POST method

xingc — Tue, 07 Nov 2017 21:15:58 GMT

Thanks for the help. I was able to get the POST working the HTTP Query Smart Service. I do have some questions though. I didn't input any values for Headers and Parameters. 1) what exactly are those fields for? 2) what is the purpose of bind() when using httpwrite()?

RE: Http POST method

Dan Lluhi — Tue, 07 Nov 2017 20:36:33 GMT

Note that the HTTP Query Smart Service was deprecated in 17.3 as well, so I definitely recommend looking into Integrations as an alternative.

RE: Http POST method

Colton Beck — Tue, 07 Nov 2017 20:36:00 GMT

If you're on an older version of Appian, check out the a!httpWrite() function. Otherwise, look into using the new Integration Objects to fulfill the requirement.

RE: Http POST method

aloks0189 — Tue, 07 Nov 2017 20:34:43 GMT

Hi xingc a!httpquery() is meant for servicing GET specific calls only. You can use a!httpwrite() function to invoke POST call and send the data through Body.

But if you are working with Appian 17.x version, they have introduced Integration object, which is quick to configure and execute. But if you are working with lower version of Appian then in such case you can go for a!httpwrite()

But httpwrite() or Integration object must be executed on saveInto by the use of bind() on load, for example within interface.

But if you want to execute POST call using process model node such as Script Task, then you can go for HTTP Query Smart Service, where method will be set to POST

Hope this will help you.

RE: Http POST method

Dan Lluhi — Tue, 07 Nov 2017 20:32:14 GMT

Hi,

Unfortunately a!httpQuery() doesn't support POST, as it's supposed to be used exclusively for retrieving information. It's also worth nothing that a!httpQuery() was recently deprecated (in version 17.2 I believe), and will be removed in a future version of Appian. It's recommended that instead you start using Integrations (docs.appian.com/.../Integration_Object.html), which do have options that support POST.

Thanks,
Dan