简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
IsabelAdams0126 · 2026年1月20日 16:07 UTC
Have both authors name the writer and meaning of each ordinary signal together.
19分Our handover used 'accepted' for both receiving a request and accepting the part. Sort those meanings out before agreeing the clearing sequence.
16分Which message did the operator actually see after the missed request, Isabel?
18分Oliver, 'coupon rejected'. There is no inspection result behind that message. Hana, the application author says acknowledgement means request received; the PLC note calls it inspection accepted. That explains some of the disagreement.
6分Then the screen text is wrong for that case regardless of how they repair the request timing. Keep it on the work list.
20分Did the authors agree one acknowledgement meaning yet?
13分Receipt only is agreed. Completion and its result are separate. The draft keeps the request identifiable until receipt and names which side writes and clears each part of the exchange.
23分Isabel, what if receipt comes back after the application has declared a timeout? Our tidy normal sequence did not answer that.
14分And what does the operator do during that timeout, while the authors are debating its signal names?
20分Hana, late receipt is still an open design case. Oliver, the proposed screen says receipt uncertain and calls for the named support contact, without offering a blind repeat. We need to test that wording with our operator.
14分I wouldn't call the interface complete with that case open. An ordinary delay is not some exotic future enhancement.
14分Agreed. Put it in the required cases before implementation is signed off.
4分It is required. The authors have now defined the late-receipt handling against the original attempt identity and added a controlled delayed-reply test. I was too quick to describe the normal exchange as the main thing.
20分Include duplicate receipt as well, since clearing and seeing the same value again should not start a second inspection.
2分Delayed and duplicate receipt tests passed in the offline interface check. The operator correctly distinguished uncertain receipt from an actual rejected coupon in the walkthrough. Installed integration checks remain, but the contradictory note and misleading screen label are corrected.
9分Was the support contact able to identify the attempt from the operator's screen during that walkthrough?
8分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .