Hi,
I have a process variable (token) and I want to use its value inside request body of integration node.
So while I tries to use it with pv! (like pv!token), it gives error "Expression evaluation error in field ’Body’: Could not find variable 'pv!token'".
I also tried to pass the process variable on input and tries to access that new variable with ac!, but still gets the error.
Please explain how can I use the process variable inside request body.
Discussion posts and replies are publicly visible
hi ranjan,
ranjank0001 said:body of integration node.
Are you using the "call integration" smart service?perhaps this article supports you?
docs.appian.com/.../Call_Integration_Smart_Service.html
Yes I am using Call Integration Smart Service
Can you explain, what kind of rule inputs your integration has and what you really configured? You even can insert screenshots here with the "insert" dropdown" below the comment box.
Actually I figured it out now, but now I am facing the issue to convert my request body data into url encoded string.Please explain how to convert the array into url encoded string.
do you mean something like base 64 encoding?
No. Actually my request body Content-Type is "application/x-www-form-urlencoded". So I need to send the data as url encoded string in request body.like this"amount=10000¤cy=inr&source=tok_1HmgWqFeYHDv9w7bMNeYo6te&description=test"
I have the impression you mean perhaps the URL you call? This looks like you need "query parameters". Bodys are in json format for example and working a bit different compared to your exampleCheck: docs.appian.com/.../Create_an_Integration.htmlSuggestion: try to insert a rule input per necessary query parameter.They will be attached like "?name1=value1’"
When I send the request like this(url encoded string)....it works fine.But when I tries to send the request like this:
it gives the error. So I need a method to convert my array into url encoded string.
This helps already to understand it better.
can you post the body of the request on the right side of this screenshot as well (for both scenarios) ? It is cut off.
Hi Richard, I figured it out. Actually all I need to do was to send the data through query parameters. So now its working fine.Huge thanks to you for helping me out throughout the entire conversation.Thanks!