IFS Workflow REST API Response Handling

Does the Response_ variables has any values? Also check the getCustLetterUrl variables content have any escape characters(As it is a url).

Hi Buddhi,

I verified the URL with the Postman and it works fine. As for the _Response variable I’m not able to check the value since it seems like the flow would not continue after the API call. I modified the variable as $._Response which I believe is the correct format but it seems like the issue right now is that after the API call everything comes to a halt.

@Buddhi Gunasekara I was able to modify the Workflow without using the REST Response, now it will work perfectly if the HTTP response is successful but I want the Workflow to continue and move on to the next step, even if I get an error response for the API call, it seems like using an output variable didn’t help because it would not continue to the gateway in case of a failure response to make use of the output variable. Do you have any suggestions on this?

@Buddhi Gunasekara Thank you! This worked for me.

@Buddhi Gunasekara I am having a similar issue that I’m hoping you may be able to help me with. I have two situations at the moment:

1. Valid Request
   1. “response” output key is populated with the JSON response.
   2. “ResponseCode” response variable is empty/undefined.

   3. 

2. Invalid Request
   1. “response” output key is empty/undefined.
   2. “ResponseCode” response variable is “400”.

   3. 

My issue is that I’d like the workflow to continue when there is an error code provided in the response, but I’d also like to access the response values so that I can display the error message to the user. Additionally, I’d like to have the ResponseCode when it is a successful request too so I can include different paths based on response type. Basically, I would like to have both values in both situations, as you would normally have in any web response. Is this possible?

Thanks in advance,

Dylan

@dritter Only the scenarios you described are implemented atm. If there’s an error code, rest call doesn’t assign the error message to a variable and for http status codes < 300, status code is not recorded into a variable. Please do a request to IFS if you feel this is a feature you like to see in future releases.

I will submit a request. I suppose in the meantime I will have to write the web requests in JavaScript so I can store both the response body and the response code into variables. Thank you for the help!

I would like to know how you write the web requests in JavaScript?  Would you mind sharing this if you get it to work?  I have the same need.  Thank you!

Also, if you made that request as an ‘Idea’ here in IFS Community, would you mind linking it in this thread so we can upvote it?  Again, thank you!

Hi @Mike The FSM TechnoGeek

I thought I’d be able to use fetch() or the XMLHttpRequest() object, but since the workflows run on the Nashorn engine, it doesn’t seem possible. We would have to edit the server-side Java to create an HTTP connection method, but I don’t think we have access to that.

I created an idea here. Please give it an upvote or a comment if you think it’s a good idea!

Thanks,

Dylan