关于乐观并发失败的最终用户消息有什么好的

发布于 2024-09-18 01:26:23 字数 183 浏览 2 评论 0原文

我试图想出一些好词来向用户解释乐观并发异常。事实证明,这比我想象的要困难得多。到目前为止我拥有的最好的是:

其他人已经修改了 记录你正在处理的事情。他们的新 值如下所示。请重拍 您所做的更改。

这对我来说有点糟糕,他们一定是更好的东西。有什么想法吗?

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 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

意犹 2024-09-25 01:26:45

该记录已被另一用户修改。要保留更改,请按 <>或按<>获取最新更新。

This record has been modified by another user. To persist your changes Press <> or Press <> to obtain the latest update.

最冷一天 2024-09-25 01:26:42

请注意,您需要涵盖四种场景:

  1. 用户尝试更新记录,但其他人先更新了它。
  2. 用户尝试更新记录,但其他人先删除了该记录。
  3. 用户尝试删除该记录,但其他人先更新了该记录。
  4. 用户尝试删除该记录,但其他人先删除了它。

鉴于此,如果您需要一条消息,请尝试以下操作:

操作失败,因为另一用户已更新或删除该记录。您的更改已丢失。请在重试之前检查其更改。

更好(但更多的工作)是根据特定条件提供消息的几种变体,并且如果可能的话告诉他们另一个用户是谁。

您还应该考虑用户体验。

删除通常是从网格中完成的,因此除了场景 1(更新/更新)之外,说“新值如下所示”可能不合适。

另外,场景 2(更新/删除)很棘手,因为您可能希望将用户重定向到新表单。否则,如果他们要更新的记录被删除了,你要向他们展示什么?

场景 4(删除/删除)可以说可以被忽略。别人抢先了你,那又怎样?

Note that you have four scenarios to cover:

  1. The user tries to update the record, but someone else updated it first.
  2. The user tries to update the record, but someone else deleted it first.
  3. The user tries to delete the record, but someone else updated it first.
  4. The user tries to delete the record, but someone else deleted it first.

In light of this, if you need a single message try this:

Operation failed because another user has updated or deleted the record. Your changes have been lost. Please review their changes before trying again.

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?

内心激荡 2024-09-25 01:26:38

除了冲突字段之外,如果您知道进行更改的前一个用户,为什么不也提供该信息。也许用户完全知道该消息的含义,但对他们来说,知道是谁进行了更改会更有用,以便他们可以联系他们并了解他们的更改是否更相关。

我还认为,该消息可能对您的最终用户有意义 - 他们是技术性的还是非技术性的(因此了解这个概念),是否有任何有帮助的业务术语?

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?

满天都是小星星 2024-09-25 01:26:35

不确定这在您的情况下在技术上是否可行,但用户可能认为以下信息有帮助:

无法保存对此“客户”记录的更改。

这是因为用户“aliceb”刚刚更改了它。您必须重做更改。 “地址”和“姓名”字段已更新。

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.

三岁铭 2024-09-25 01:26:32

怎么样。

您正在处理的记录已被其他用户修改。该记录的新值如下所示。您所做的更改尚未保存,请重新提交。

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.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文