When editing and/or saving a record, there should be some indication to a user of the need to refresh for the most current record data when the record has been edited/changed by another user since the record was accessed. This would avoid causing overwriting and/or reverting of changes, causing potential production delays.
Yes, permissions can be set so only one user can access a record at a time but this isn't efficient. User A and B should both be able to enter their data on a record without the need for a different workflow state for each to ensure no inadvertent, or accidental, overwriting of data.
Examples -
Scenario 1 - User A is editing a record; User B edits the same record and saves changes; User A then saves their changes unaware User B did anything. This overwrites and/or reverts any changes User B made without User A being aware the version they were editing was no longer the current version. User B thinks they are done and with no need to go back to the record and the record sits causing delays.
Scenario 2 - User A is viewing (not editing) a record; User B edits the same record and saves changes; User A then edits the record they have been viewing and saves their changes unaware the version they were viewing is no longer the current version. This overwrites and/or reverts any changes User B made without User A being made aware the version they edited was no longer the current version. User B thinks they've completed their part with no need to go back to the record and the record sits causing delays.
