Handling concurrency - Prevent over writing of changes made by another user
Hello Community!
I notice the following behavior -
User 'A' and 'B' have the same contact's page open at the same time and intend to modify the same field. 'A' changes a field and saves it. However 'B' does not know that the field value has changed behind the scenes and in turn modifies the value. I notice that B's change overwrites A's ie Last write wins. And neither user knows that this has happened.
- How do I ensure that 'B' is informed that 'A' has made a change so 'B' can get the latest data and take corrective action?
- Concurrency is a standard problem to solve. How does Creatio look at solving concurrency related issues? Is this part of the product road map??
Like
Hello!
Creatio assumes that each user only workes on 1 record - most sections have field "owner" which specifies what user responsible for which record. If there is a need to work with many records and users may interfere with each other you can use processes to distribute records as it is done in Queues.
Best regards,
Angela
Angela Reyes,
Hi Angela. Thank you for your response.
Multiple users having access to 1 record is common place where people work in teams and an entire Org role has access to modify a set of records. There are also cases where Creatio will need to co-exist with other enterprise systems which modify the same record thus creating a shared source of truth system.
I am going ahead and logging an idea on the community to make the above situations easier from a User POV.