Home > Forum > General > REST Web service call - application integration action template - based on global constants

REST Web service call - application integration action template - based on global constants
0

Hi,

We try a REST Web service call like this:
- global constant for REST Web service base URL, as https://something.com
- global constant for REST request suffix, like api/webcon/action
- other global constants, for Bearer etc

- at app level we configure a template - Invoke REST Web service based on previous defined constants

We use those global constants just to have separate value sets for DEV / TEST / PROD.

The problem:
- the REST request suffix gets URI encoded, from api/webcon/action to api%2Fwebcon%2Faction, therefore the API call fails with 404
- if suffix gets a slash upfront, /api/webcon/action, it gets encoded to %2Fapi%2Fwebcon%2Faction, and API call fails with 401

The question: is there a way to have that global constant request suffix NOT ENCODED when concatenated with the server base URL? As it is part of the call address, not query params for the call.

Thanks,
Mihail

MVP

Hi Mihail,

if you are using REST actions you can store the values in a technical field and use this field in the REST action. If we are using fields we have the option to use a Raw mode. Y

There's also this user voice.
https://community.webcon.com/forum/thread/5645?messageid=5645

The mentioned workaround is only an option for REST actions but not for Rest data sources.
I've created a ticket for this because we simply cannot upgrade a customer because of this behavior.
We are getting data from the ERP system using the REST API and this encoding prevents us from creating a filter, which is working fine in 2022.
Without the filtering the user has to wait 5 or more seconds because all data is returned to WEBCON from the ERP system.

Best regards,
Daniel