In our application, one object is open in two different sessions (it doesn't matter if these sessions belong to the same user or different users).
The object is open in a data view in both sessions, the data view shows the status of the object, in this case: 'error'
In a microflow from one of the two sessions, the status of this object is changed to 'OK', and the object is commited and refreshed in client.
Now, in only one of the two sessions the object is actually updated, stating 'OK'. in the other session, the object still shows 'error'. Refreshing the object in the 'error' session doesn't help at all, the object really has to be completely reloaded in order to show the status update.
I can kind of understand that when two people are working on the same object, if one commits and refreshes in client, the other doens't want to lose their changes. However, i also see this potentially corrupting data.
In our case we want the object to be updated in both sessions at the same time, to prevent data from getting corrupt.
Does anybody have a workaround for this?