Hi,
when a user opens a screen for a table and keeps the session open in the browser,
the underlying table is locked for backend processes.
Using the uncommitted read isolation level will solve this issue.
I went through the docs, but could not find the information,
how to set the isolation level in a standard browse screen.
Is there a way to do that on a central place?
Or how to handle that in JMIX apps?
Regards Roland