Hi Dojo,
We need to know if the CRUD execution of the same DOM Instance is locked or not? And also the execution of the scripts linked to DOM buttons.
Use case is that multiple users are making changes to the same DOM Instance. In that case we need to ensure that the CRUD execution happens sequentially.
Hi Jens,
My response to your other Dojo question contains some details already about this flow, but in general, all write operations to DOM instances are queued on each DMA. This does not include the DOM action requests but does include the DOM transition requests.
What this will do is ensure that the first user who executed a DOM transition, will transition the DOM instance, and the next will get an error that the DOM instance would already be transitioned. Something similar applies when a user updates fields that should not be updated anymore after the status transition that was done right before the field update.
Since the DOM instance updates are full object replacements, you do need to keep in mind that updates could be overwritten. (See other Dojo question)
That is correct. The actions behind the buttons can be executed in parallel. (Both on DMA and DMS level) However, if that action (script) does DOM updates, then these are queued.
Hi Thomas, thank you for the quick reply.
So if I understand correctly there is no locking when a user clicks on a DOM button?