Why the account bpc_svc (assigned to Webcon BPS Service) need to license to execute timeout ?
Webcon version 2024.1.1.88
Why the account bpc_svc (assigned to Webcon BPS Service) need to license to execute timeout ?
Webcon version 2024.1.1.88
Are you sure you are starting a new document with this account?
Are you sure you are starting a new document with this account?
I created a scheduler where I have a template of the element.
On timeout every week I would like to create a new element.
I override the owner but still the license is required.
From my perspective it looks like a bug.
99% of customers have dedicated accounts for bps_svc and bps_appPool and now if a customer used all licenses I'm not able to do that.
Btw I found another example: if you have 10 API integration you have to have extra 10 licenses...
I created a scheduler where I have a template of the element.
On timeout every week I would like to create a new element.
I override the owner but still the license is required.
From my perspective it looks like a bug.
99% of customers have dedicated accounts for bps_svc and bps_appPool and now if a customer used all licenses I'm not able to do that.
Btw I found another example: if you have 10 API integration you have to have extra 10 licenses...
Hi,
I doubt that you get here an answer for a "Why" question. I also find it a little bit strange, that the workflow server needs a license since a few versions.
That the APIs requires a license is fine for me. I know other vendors who's API would need to be licensed separately and at a way higher prices.
In theory, you could replace the frontend using the API and any number of users could use the new frontend while only a single license is consumed.
Best regards,
Daniel
Hi,
I doubt that you get here an answer for a "Why" question. I also find it a little bit strange, that the workflow server needs a license since a few versions.
That the APIs requires a license is fine for me. I know other vendors who's API would need to be licensed separately and at a way higher prices.
In theory, you could replace the frontend using the API and any number of users could use the new frontend while only a single license is consumed.
Best regards,
Daniel
Hi!
You're correct that the API requires additional licenses. However, any internal operations performed by our server (especially timeouts) do not require a license. I recall there was a bug related to this issue. Please upgrade to the latest available version, and if the problem persists, feel free to reach out to our support team. ;)
Best regards,
Łukasz