Hi, Could you clarify what changes were made to the SDK licenses in WEBCON 2024 and 2025? I don’t fully understand the modifications and would like to know if I need to take any additional steps regarding the license or key to sign plugins. If I’m currently using an SDK plugin developed by our in-house development team, does that mean I might not have an SDK license? Or do I need to do something with the signing key? I’m a bit confused. For context, we have a perpetual license - webcon 2022
On Danielk's blog:
https://daniels-notes.de/posts/2024/webcon-bps-2024-change-log#sdks
"In addition to this: If you are not creating SDKs on your own, but have a partner do it, ask them whether they have given WEBCON the public key. Otherwise it may happen that these cannot be used."
in the webcon change log to 2024 version:
"Changed the method of license control when using SDK extensions.
The change applies to perpetual license environments where SDK extensions are
actively used. Currently, the license that allows the use of SDK extensions is
verified before the plugin is run. Before upgrading the system, it is recommended
to verify the availability of the WEBCON BPS SDK Framework license in the
environment. A list of current licenses is available in Designer Studio under
Reports › Licenses › License usage.
Regardless of the availability of the WEBCON BPS SDK Framework license, SDK
extensions created by authorized WEBCON partners, who have signed the
extensions with their key previously provided to WEBCON, can be run on the
environment.
For environments running under a subscription-based licensing model, no action
is required – the WEBCON BPS SDK Framework is licensed by default under this
model.
The SDK plugins can also be used freely in time-limited environments (demo
license) and in installations based on the Freemium version."