Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0027915 | Retail Modules | Gift cards and gift vouchers | public | 2014-10-20 13:53 | 2015-09-08 11:28 |
| Reporter | plujan | ||||
| Assigned To | marvintm | ||||
| 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 | 0027915: Error message when not filling the fields properly is not clear enough | ||||
| Description | When creating a new Gif Card product, I've made a mistake when filling the "POS Properties" section. As a result, I've got an error message that is too generic to let me know what was my mistake. Error Saving failed. There is a constraint defined that was not satisfied. Please check the data entered | ||||
| Steps To Reproduce | 1. Having the Gift and Vouchers module installed, log in the backend as WhiteValley admin role. 2. Go to Product and create a new product with following data: Organization: Vall Blanca Store Search Key: GC/001 Name: Gift card 1 UOM: Unit Product Category: Backpacks & Travel Tax Category: IVA Normal Purchase: Unchecked Sales: Checked Stocked: Unchecked In POS properties (section) Is Scale: Unchecked Grouped Product: Unchecked Show stock screen: Unchecked Gift Card Type: Gift Card Gift Card Initial Amount: 1000.00 Finally, Deferred Revenue: checked This last field should have been unchecked, but if you try to save the record with the field as checked, an error is raised: Error Saving failed. There is a constraint defined that was not satisfied. Please check the data entered Although it is correct to raise an error, the message is too generic and force the user to check every possible field or combination. | ||||
| Proposed Solution | Error messages should be as specific as possible in order to help the user to fix it and continue. Generic error messages lead to a bad user experience. There is a missing ad_message in a module Check this: http://wiki.openbravo.com/wiki/How_to_add_a_Constraint#Adding_a_proper_message [^] [^] | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2014-10-20 13:53 | plujan | New Issue | |||
| 2014-10-20 13:53 | plujan | Assigned To | => marvintm | ||
| 2014-10-20 13:53 | plujan | Triggers an Emergency Pack | => No | ||
| 2015-09-07 17:48 | Orekaria | Note Added: 0080208 | |||
| 2015-09-08 11:28 | Orekaria | Note Added: 0080239 | |||
| 2015-09-08 11:28 | Orekaria | Note Deleted: 0080208 | |||
| 2015-09-08 11:28 | Orekaria | Proposed Solution updated | |||
| Notes | |||||
|
|
|||||
|
|
||||