SIP2: Protocol for self-checkout
(UXPROD-1001)
|
|
| Status: | Closed |
| Project: | sip2 |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 1.0.0 | Parent: | SIP2: Protocol for self-checkout |
| Type: | Story | Priority: | P3 |
| Reporter: | Hkaplanian | Assignee: | Martin Tran |
| Resolution: | Done | Votes: | 0 |
| Labels: | q1-2019-spillover | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Sprint: | 3Ms-SIP2-61, 3Ms-SIP2-60 | ||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Tester Assignee: | Magda Zacharska | ||||||||||||||||
| Epic Link: | SIP2: Protocol for self-checkout | ||||||||||||||||
| Description |
|
FOLIO must send this message in response to a SC Status message. Senario 1 Senario 2 |
| Comments |
| Comment by Magda Zacharska [ 18/Mar/19 ] | ||||||||||||||||||||||||||||||||||
|
The self checkout station will send status message to FOLIO: status code: It is a status of the self checkout unit. 1-char, fixed-length, required field. Allowed values: 0 (OK) or 1 (out of paper) or 2 (about to shut down) In the response FOLIO will return following message: on-line status: 1-char, fixed-length required field: Y or N.
terminal location: variable-length optional field. FOLIO could put the SC’s location in this field. Field Code: AN | ||||||||||||||||||||||||||||||||||
| Comment by Matt Reno [ 03/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|
Just a note here, we can't respond to SC status until a login message is placed. Scenario 1 and 2 should probably be updated to include "1a. SC sends a login message." For scenario 2, it is possible that the SC is currently logged in when the shutdown is initiated, but login is still a prerequisite for SC status to be accepted. | ||||||||||||||||||||||||||||||||||
| Comment by Magda Zacharska [ 03/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|
I think what you describe is covered by
According to the 3M Developer Manual (attaching to this user story) the login message is not required. SC might be configured to send certain character strings and wait for a certain character strings from ACS. At least this is how I understand the communication between SC and ASC | ||||||||||||||||||||||||||||||||||
| Comment by Matt Reno [ 04/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|
From a protocol perspective, that is true. But from a practical standpoint we cannot accept SC status without a login first in a multi-tenant setup. With Chalmers, sure they are the only one, but this wouldn't work when another tenant is on the system. Though, I think there are bigger issues here with respect to multi-tenant support. | ||||||||||||||||||||||||||||||||||
| Comment by Magda Zacharska [ 04/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|
Let's discuss the best approach and prioritize the work. | ||||||||||||||||||||||||||||||||||
| Comment by patty.wanninger [ 04/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|
Magda Zacharska, this ticket is marked "In-reveiw," but we (the manual testing team) have no way to test it. Can you assign yourself as tester? | ||||||||||||||||||||||||||||||||||
| Comment by Martin Tran [ 08/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|
4/8 - Developer's notes:
| ||||||||||||||||||||||||||||||||||
| Comment by Martin Tran [ 09/Apr/19 ] | ||||||||||||||||||||||||||||||||||
|