I'm trying to come up with some good words to explain an optimistic concurrency exception to a user. It turns out it's a lot harder that I thought it would be. the best I have so far is:
Someone else has already modified the record you were working on. Their new values are shown below. Please remake the changes you made.
This feels kinda crappy to me, they must be something better. Any thoughts?
How about.
The record you are working on has been modified by another user. The new values for this record are shown below. Changes you have made have not been saved, please resubmit.
This record has been modified by another user. To persist your changes Press <> or Press <> to obtain the latest update.
As well as the fields in conflict, if you know the previous user that made the change, why not supply that too. Maybe the user is fully aware of what the message means, but for them it would be more useful to know who made the change so they can contact them and find out if their's is more relevant.
I think also that the message is probably going to be something that has meaning to your end user - are they technical or non-technical (so aware of the concept) and are there any business terms that would help?
Not sure if it is technically feasible in your case but the following information might be considered helpful by the users:
Changes to this 'customer' record can't be saved.
This is because the user 'aliceb' just changed it. You have to redo your changes. The fields 'Adress' and 'Name' are updated.