Hi, With current version of Utility HTTP, we get response body. Is there a reusable VBO in BP to return back response headers and response code as well along with body?
@ewilson - Kindly share the link for the same. Might be possible I have older version of VBO. Does that include response code as well? Also I have seen when API end point is not reachable from blue prism, it gives some code stage error of object not referenced, ideally there should be a more specific errors from VBO code code stage for various exception scenarios possible when calling an API. Can you ask someone from your engineering team to work a bit on it and have a new version of it released on DX portal that we can download.
The current VBO is available on the DX. It does not include a separate output parameter for the HTTP response code, but we can look at getting that added.
We'll look into the exception messaging.
Cheers,
------------------------------ Eric Wilson Director, Partner Integrations for Digital Exchange Blue Prism ------------------------------
I just uploaded v3 of the HTTP utility VBO. It now includes an output parameter called "Status Code" that contains the numeric HTTP status code associated with a request.
Cheers,
------------------------------ Eric Wilson Director, Partner Integrations for Digital Exchange Blue Prism ------------------------------
@ewilson - Thanks a lot for your quick response as always, very helpful. I will try this. Meanwhile want to check if you were able to handle the exception in a better way when API end point is not reachable from BP machine so that we get a more specific message. Its very tough to understand the issue from code stage when it gives general object related error message
@ewilson - lot of times we face issues when API works smooth and quick with postman passing simple headers and body. However when we call it from blue prism http we get errors. The exact cause of error will help a lot applying fix accordingly.
@Mayank Goyal - Just uploaded v3.1 of the VBO. This has improved exception messaging. If an exception is encountered when trying to reach a site you should receive the actual exception message and associated HTTP status code (ex. 404) depending on what caused the exception. Previously, the object error you were seeing was due to the way the code was assuming that a WebResponse object would be included in the WebException object. That's not always the case.
Cheers,
------------------------------ Eric Wilson Director, Partner Integrations for Digital Exchange Blue Prism ------------------------------