Creatio has a 'Last write wins' policy with respect to handling concurrent updates to the same record. Use case below -
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. B's change overwrites A's and neither user knows that this has happened.
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.
Request the following ideas to be considered to be added to the platform -
At a first level, users need to be alerted of any changes to a record they are currently viewing. That way, they can refresh to get the latest values and take corrective action.
At the next level, when the user saves their changes, S/he can be presented with their version of changes vs the version of changes done by another user - thereby enabling manual resolution of conflicts.
Thank you for providing us with ideas that can improve the customer experience of using the Creatio platform. For the 1st idea, we have registered a separate request to our R&D team. If this idea will be in high demand it can be implemented in future versions of the application after additional analysis. Also, you can contact our manager to discuss the faster implementation of the required functionality.
Accordingly to 2nd idea: if I understood your request correctly, this kind of functionality is already provided with out-of-the-box version of the application. For this purpose you can use "Change log" section. The change log contains information about adding, modifying, and deleting records (entries) in the database tables for Creatio objects. This includes sections, details, lookups, as well as other objects.
More information about "Change log" you can find in the next atricle:
Hi Roman. Thank you for the response. Yes, I am aware of the change log and it certainly helps in retrospective action. But, It doesn't help in conflict resolution at the moment of the conflict.
It will help if a user is presented with the conflicting changes at the moment s/he saves - so that they can decide which values are the correct ones and then save.
Both problems are in the "Accepted" status by the R&D team so they will be definitely implemented in one of the future releases, but there is no ETA on these tasks yet. Once the functionality of alerts on simultaneous modification of records is developed we will notify all our clients and partners in the "Release notes" available here.
Hi, is there any update on this feature now? I can't see it when testing in a 8.1.0 environment currently, but would be a very useful feature to have to bring parity with Salesforce and Siebel in the CRM sphere.
As of now this functionality is not yet implemented. Unfortunately, due to complexity of such task and the need of additional testing before implementing such functionality there is no specific ETA as of now.
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??
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.
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.
