Optimistic locking would allow the changes to be made by multiple persons but the problem is then forcing everyone else to refresh their browser after a change is saved.

If this is not done, users could very well make decisions based on "stale" data.

Suppose a parent case that spins off clones of itself as subcases.

The subcases are configured to not lock the parent hence can be updated independently.

On save, the child case would lock the parent then see if the pxUpdateDateTime is now newer than its own value, meaning some other subcase had updated it.

If (A) there is no overlap in terms of what the two subcases had updated and

(B) the non-overlapping updates have no bearing on the changes made in the current subcase,

THEN its updates and only those updates could be transferred to the parent case.

Whereas (A) can be detected automatically, it would be difficult to code for (B).

Side-by-side visual inspection would be needed.