Home > Forum > Actions > Problem with URL to REST Service after upgrade to 2025

Problem with URL to REST Service after upgrade to 2025
0

Hi,

After upgrading from the 2022 version to the latest 2025 version, I am experiencing an issue with the URL for REST services.

The address and API endpoint are stored as global constants.

For example, the URL: https://mock.webcon.bps:3317

For example, the endpoint: /domains/customercommunication/internal/v1/message

Webcon returns an error during the sending action due to an incorrect URL --> https://mock.webcon.bps:3317/%2Fdomains%2Fcustomercommunication%2Finternal%2Fv1%2Fmessage

In version 2022, it worked fine.
If I remove the address from the endpoint and put the entire value into the URL, it works correctly.

How can I solve this?

MVP

Hi,
Webcon at some point started encoding url's used by REST actions.
As a workaround you could use text attribute - for those you have an option to choose, that text shouldn't be url encoded.
See attached screenshots :) (in my case that set is rather complicated, as this api receives data as url query params rather than json body, but might be much shorter).

I'm nearly sure there is some user voice post regarding this topic, but can't find it.

MVP
In reply to: Maksymilian Stachowiak

Hi,
Webcon at some point started encoding url's used by REST actions.
As a workaround you could use text attribute - for those you have an option to choose, that text shouldn't be url encoded.
See attached screenshots :) (in my case that set is rather complicated, as this api receives data as url query params rather than json body, but might be much shorter).

I'm nearly sure there is some user voice post regarding this topic, but can't find it.

Hi,

this was changed in 2023 and I have been pestering WEBCON about changing it whenever I got a change. May it be in person or when I (again) upgraded another customer to a new version with a ticket.

Here's the user voice.
https://community.webcon.com/forum/thread/5645?page=1#m6795


You could also check my post to find any other potential issues:
https://daniels-notes.de/posts/2025/upgrade-2022-to-2025


Best regards,
Daniel