PriyaAllen0307 · 27 Mar 2026, 00:31 UTC
Both interface authors. Ask each to write when request starts, what accepts it and what clears it. One shared sequence, with ownership named.
14 pointsThe PLC author says request is an announcement. The application author expects it to remain until accepted.
19 pointsThat disagreement is enough to explain why their expectations differ. Is acknowledge already defined, or is its meaning equally loose?
7 pointsAnd what identifies the sample attempt? A fresh receipt of an old request must not look like another housing.
6 pointsAcknowledge needs its own clearing rule too. Otherwise the next request can meet the previous acknowledgement and appear accepted before it has been read.
8 pointsAisha, acknowledge means received in one note and completed in the other. Jasper, no attempt identity is documented.
11 pointsThen they need to name acceptance and completion separately in the specification. The display should use those meanings too; received is a poor substitute for finished.
25 pointsThanks. Ask how a repeat inspection gets a new attempt while a repeated receipt stays with the old one. Both happen in real work.
23 pointsI've returned those specific disagreements to both authors. The current ordinary interface is not agreed for commissioning.
4 pointsInclude connection loss after acceptance in their review. That state needs an answer before anyone decides to clear or resend it.
10 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.