关于乐观并发失败的最终用户消息有什么好的
我试图想出一些好词来向用户解释乐观并发异常。事实证明,这比我想象的要困难得多。到目前为止我拥有的最好的是:
其他人已经修改了 记录你正在处理的事情。他们的新 值如下所示。请重拍 您所做的更改。
这对我来说有点糟糕,他们一定是更好的东西。有什么想法吗?
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?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
该记录已被另一用户修改。要保留更改,请按 <>或按<>获取最新更新。
This record has been modified by another user. To persist your changes Press <> or Press <> to obtain the latest update.
请注意,您需要涵盖四种场景:
鉴于此,如果您需要一条消息,请尝试以下操作:
更好(但更多的工作)是根据特定条件提供消息的几种变体,并且如果可能的话告诉他们另一个用户是谁。
您还应该考虑用户体验。
删除通常是从网格中完成的,因此除了场景 1(更新/更新)之外,说“新值如下所示”可能不合适。
另外,场景 2(更新/删除)很棘手,因为您可能希望将用户重定向到新表单。否则,如果他们要更新的记录被删除了,你要向他们展示什么?
场景 4(删除/删除)可以说可以被忽略。别人抢先了你,那又怎样?
Note that you have four scenarios to cover:
In light of this, if you need a single message try this:
Even better (but more work) would be to offer several variations of the messages based on the specific conditions, and if possible to tell them who the other user was.
You should also consider the user experience.
Deleting is often done from a grid, so saying "the new values are shown below" may not be appropriate except for scenario 1 (update/update).
Also, scenario 2 (update/delete) is tricky because you probably want to redirect the user to a new form. Otherwise, if the record they want to update is deleted, what are you going to show them?
Scenario 4 (delete/delete) could arguably be ignored. Someone else beat you to it, so what?
除了冲突字段之外,如果您知道进行更改的前一个用户,为什么不也提供该信息。也许用户完全知道该消息的含义,但对他们来说,知道是谁进行了更改会更有用,以便他们可以联系他们并了解他们的更改是否更相关。
我还认为,该消息可能对您的最终用户有意义 - 他们是技术性的还是非技术性的(因此了解这个概念),是否有任何有帮助的业务术语?
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:
怎么样。
How about.