MMI-3063 better UX for concurrency errors #2391
Conversation
|
|
||
| // Throw user-friendly message with better formatting | ||
| var userMessage = $"Content has been modified by another user. Modified fields: '{changedFields}'. " + | ||
| "Please save your changes, refresh page, and reapply your updates."; |
There was a problem hiding this comment.
It's impossible for the user to save their changes before refreshing the page. It will result in the same error.
A better user experience would be to inform the user which fields are different. Then they could choose whether they want to override the values in the database with their own. You just need to be careful here, because many users will just say override. Ideally we would have a way to determine what was changed, rather than what is different. For example if the first save changes fields A and B, and the second save changes fields B and C. Technically we can automatically resolve changes to fields A and C, but need to ask the user what to do with field B because they both edited it.
There was a problem hiding this comment.
Thanks, for the helpful input. I think I may need to discuss some of this with the designer and modify the UI.
There was a problem hiding this comment.
Ideally if there is no difference other than the version number, or the status, it should be able to merge and save correctly without returning an error.
…dle concurrency conflicts more gracefully. Added methods to retrieve and log changed properties, improving user feedback on modifications made by others.
- Add ContentConflictException to middleware for handling content update conflicts - Update useToastError hook to display detailed conflict messages with modified fields - Modify ContentService to use ContentConflictException
kkwangsir
force-pushed
the
MMI-3063-API
branch
from
f046175 to
a95bacd
Compare
|
It's been a while since we've found with this issue. Based on the designer's feedback, let's keep the current toast display approach but make it clearer for the user. If there's a content conflict, show the modified fields. For the ContentConflictException error specifically, manually close the toast to give users enough time to read and act. |
…uers - Modify useToastError words
| } | ||
| catch (DbUpdateConcurrencyException ex) | ||
| { | ||
| this.Logger.LogInformation("Concurrency conflict detected - ContentId: {ContentId}", entity.Id); |
There was a problem hiding this comment.
Do we need this as error log too?
There was a problem hiding this comment.
thanks, it is a good idea.
In the past, it was monitored that there were some concurrency errors in the API during content editing. After a long period of comparison, I found that most of it was actually harmless.
Some of it was caused by the request for a transcript. I tried automatic merging, but it turned out to be unsafe, as there were too many factors to consider.
So, I changed it to display the modified fields on the frontend, giving users a prompt, and logging some detailed content on the backend for debugging purposes.