Solved

Bug in new Web Connection (duplicated Base url)


Userlevel 2
Badge +1

We have created this week multiple API functionalities and we tried to do them with the new web connection.

We encountered multiple times for it in HTTP Connector to work just fine but in this with the same parameters to not work at all.

It worked from what we saw just for endpoint that didn't have parameters in their url, for those that had it was not working and in most of the cases we just got EMPTY as result (this is very annoying).

This happend until we reached an endpoint which was able to tell us that what we want to access does not exist and that when we used a regex to output our results, because first we tried with json and it failed without knowing why.

This is the base setted up in web connection.

And this is the endpoint setted up before we knew the problem, you can say it looks just fine, but in reality it is not.

Those are the parameters

And this is the response that we were able to see in process flow monitor

It basically ignore the first part of the url and the last part of it that is before the endpoint. Is doing some weird combination.

Anyway, if we set it as below (with duplicated base)

It is working just fine and we got the response.

Please investigate what's going on, also as a suggestion, it happened to us to use an API from OneDrive where in order to proceed we gotten an URL from it where we needed to do the calls, for that to work you are always required to put a base and a endpoint, but what if you have the URL as parameter, it should be more flexible and also give more informations about the calls that you make.

I feel that this Web Connection is very useful, but should be improved with: more details about the calls that you make, you simply don't get enough informations in case something is wrong (just an unknown error which is not helping) and more flexibility from the point of customizing the url.

icon

Best answer by Dick van den Brink 7 June 2024, 15:10

View original

4 replies

Userlevel 4
Badge +2

I believe the issue with the base path is already fixed.

Are you using Indicium version 2024.2.11.0?

Your last point about debugging the WebConnector, that is a valid point. We are looking into ways to make it easier to see what is going on. This might take some time to finish though, but is definitely on our radar.

Userlevel 2
Badge +1

We are still at version 10, I will come up with an update after we do the update later this week. This may be the cause also for this one: 

 

Userlevel 2
Badge +1

The problem was resolved with version 11. Thanks!

Badge +2

Your last point about debugging the WebConnector, that is a valid point. We are looking into ways to make it easier to see what is going on. This might take some time to finish though, but is definitely on our radar.

@Dick van den Brink Should we also create a new idea for that one?

Reply