Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0038286 | Retail Modules | Web POS | public | 2018-04-05 17:57 | 2018-04-05 17:57 |
| Reporter | plujan | ||||
| Assigned To | Retail | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | main | ||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0038286: [RR18Q2] [FastBrowse] The message when entering wrong values in the Assortment configuration is not clear enough | ||||
| Description | If a row, column, Bestseller row or Bestseller column is greater than the configured value in Fast Browse, the message only say "Saving failed. Row defined for fast browse is not allowed by configuration. Row limit exceeded", it should say what is the value so the user does not have to guess nor return to the previous window to check it. And it is not said that some fields cannot be left blank. Since they are marked as non mandatory, it is difficult to understand what happens when the message shown is Saving failed. There is a constraint defined that was not satisfied. Please check the data entered | ||||
| Steps To Reproduce | 1. Using a Fast Browse enabled environment, after configuring the Fast Browse Configuration window, go to the Assortment window 2. Fill the fields "Row", "Column" and "Bestseller row" with the value 100. 3. Try to save, the message stated in the issue description is shown. 4. Change the three values to 1 (note: the field Bestseller Column will remain blank). 5. Try to save, the message stated in the issue description is shown. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2018-04-05 17:57 | plujan | New Issue | |||
| 2018-04-05 17:57 | plujan | Assigned To | => Retail | ||
| 2018-04-05 17:57 | plujan | Regression introduced in release | => main | ||
| 2018-04-05 17:57 | plujan | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |