Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0038286
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSminorhave not tried2018-04-05 17:572018-04-05 17:57
ReporterplujanView Statuspublic 
Assigned ToRetail 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in releasemain
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0038286: [RR18Q2] [FastBrowse] The message when entering wrong values in the Assortment configuration is not clear enough

DescriptionIf 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 Reproduce1. 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- 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


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker