Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0031980 | Retail Modules | Web POS | public | 2016-01-21 11:50 | 2016-01-21 11:50 |
| Reporter | plujan | ||||
| Assigned To | Retail | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | main | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0031980: [RR16Q1] Message when trying to access a non active terminal is not correct | ||||
| Description | When trying to login to a terminal that has been set as not active, the message is unclear: Web POS terminal (%0) does not exist Web POS Terminal VBS1120 is not present in DB. Ask your System Administrator. | ||||
| Steps To Reproduce | Scenario A: Accessing a non existent terminal (correct scenario) 1. Change the default URL to get a non existent terminal, ie. change VBS-1 to XXX-1 2. Before showing the login screen, a message appears: "There are no users for the XXX-1 terminal or the terminal does not exist. Please contact the system administrator." Scenario B: Accessing an existent but not active terminal (failing scenario) 1. Access to the back end as White Valley group admin 2. Go to POS Terminal window and seek for the terminal VBS1120 3. Edit the record unchecking the Active checkbox. 4. Go to webPOS changing the default URL to this not active terminal, ie. change VBS-1 to VBS1120 5. Login page appears, users are shown. Select vallblanca user and enter his password. Click Log In button. 6. A confusing message is shown: "Web POS terminal (%0) does not exist Web POS Terminal VBS1120 is not present in DB. Ask your System Administrator." | ||||
| Proposed Solution | *Not active terminals should not allow login to later say it is not possible to log in (behaviour should be as in non existent terminals) *Not active terminals should not show a message saying they are not present in the DB, since that is not correct *Message text should be reviewed since it is not properly written. In order to keep the style, both messages (non existent and not active) should be similar. Note that one says "Please contact the system administrator" while the other says "Ask your System Administrator". *Error message should be specific to let the user know what is wrong. Ie. "This terminal has been set as not active. Please contact your System Administrator." | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2016-01-21 11:50 | plujan | New Issue | |||
| 2016-01-21 11:50 | plujan | Assigned To | => Retail | ||
| 2016-01-21 11:50 | plujan | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |