09.10.2026
20:40
Hello,
We are currently using WEBCON BPS 2026.2.4.193 and have noticed a number of changes related to form locking and concurrent editing behavior compared to previous versions.
I would like to ask whether these changes are expected and intentional, or whether some fixes are planned in upcoming releases.
For example, we occasionally receive messages indicating that the workflow item has been refreshed or modified by another user/session, even though there is no active parallel editing of the form by another person.
We are also using the "work on behalf of" (delegation) functionality extensively for testing purposes, and this is where we have observed the most unexpected behavior.
Some examples:
I open and edit a form while working on behalf of another employee. After being inactive for 2-3 minutes, I receive an error indicating that the workflow item is being edited by the user on whose behalf I am working, even though I am the only person editing the form.
If I alternate between working under my own account and working on behalf of another user on the same workflow item, the lock is sometimes not released correctly. In some cases, it can take several minutes (even more than 10 minutes) before the item becomes available again.
While working on behalf of another user, I sometimes receive a message stating that the form is being edited by my own account, although I am not simultaneously editing the item in a separate session.
Has anyone else experienced similar issues after upgrading to WEBCON BPS 2026?
Are there any documented changes in the locking mechanism, session handling, or concurrent editing logic that could explain this behavior?
Any insights or experiences would be greatly appreciated.
Thank you.
