WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > Forum > Latest posts

latest posts

MVP

Hi,
Firstly, see if there is more information in the event log.
From my own experience, I know that if the translation files can contain errors that cause problems y with the import. Errors are e.g. some white characters pasted into the translated data, or e.g. the translated data is not the text entered in the cell but e.g. an excel formula. It all depends on who translated the file and how.
Try generating a new file to translate from the process, then copy e.g. the first 3-5 translated columns from the translated file into this new one, and try importing anyway, bit by bit.... you should be able to trace where there is possibly an error in the data.

Regards.

WEBCON

Quoting the changelog:

"The functionality can be managed through a new section, WEBCON BPS Statistics,
(System settings → Global parameters), which was added to Designer Studio. The
section allows users to withdraw their consent (the Allow sending statistics checkbox)
(note that in such cases, the information is still collected even though it is not
transmitted), check the last data delivery time (Date of last sent data), view a file listing
delivered data (Show sent data),"

You can easily check what data is collected and potentially sent.
I am attaching a fragment of the file with statistics.

I think (I hope) that the individual statistics are clearly described in the file. If not, please let us know.

Michał, in documentation WEBCON 2025

https://community.webcon.com/download/changelog2/331?q=71d3da3

"3.4. API & SDK
• Usunięto API v4.0, natomiast wersja 5.0 została oznaczona jako przestarzała.
Endpoint api/login służący do uwierzytelniania został usunięty i zastąpiony
endpointem /api/oauth2/token. W związku z powyższym, jeżeli w Designer Studio
skonfigurowano połączenie REST Web Service, gdzie jako typ uwierzytelnienia
podano WEBCON BPS, to nastąpi samoczynna aktualizacja połączeń do
Aplikacja (oAuth). Ponadto:
- jeżeli połączenie do wersji WEBCON BPS 2022 i wyższej nawiązuje aplikacja
(Połącz jako -> Aplikacja), to nie są wymagane żadne dodatkowe działania,
- jeżeli połączenie do starszych wersji WEBCON BPS nawiązuje aplikacja, to
poprawne działanie połączenia wymaga zmiany ustawień na Połącz jako ->
Aplikacja (przestarzałe),
- jeżeli połączenie do wersji WEBCON BPS 2025 nawiązuje użytkownik (Połącz
jako -> Użytkownik), to konieczne jest przekonfigurowanie połączenia na
wykorzystujące uwierzytelnienie oAuth2 User -> API lub typu Aplikacja (oAuth)."

Hello.


According to this documentation: https://developer.webcon.com/docs/api-registration-and-authentication,
the api/login endpoint is still listed as an option. I see that this refers to version 2025.1. However, I'm using version 2025.2 and the api/login endpoint no longer works.
Do you know why? Where is information about this change, I know there is OAuth2 option, I would like to keep it all way.

Did you know that with WEBCON you can automate virtually any process? Even baking cookies 🍪
 
Speaking of cookies: we use the ones that are essential for our website to function properly, as well as additional ones that help us customize our content to your preferences. If you don’t mind cookies, click Accept. If you want to learn more, explore settings.
Settings