Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0023405 | Retail Modules | Web POS | public | 2013-03-26 13:12 | 2013-03-26 13:12 |
| Reporter | marvintm | ||||
| Assigned To | marvintm | ||||
| Priority | normal | Severity | major | 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 | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0023405: Payment methods should be extensible without having to change the application dictionary | ||||
| Description | Currently, to add a new payment method to the Web POS, you need to create a new entry in the Application Dictionary, specifically in the Reference/List Reference window. This is because you also need to add a preference which is linked to a list property. This is not a nice way to do this, because payment method information is not code, it's user information which should not require development actions to be implemented. | ||||
| Steps To Reproduce | . | ||||
| Proposed Solution | A possible way to improve this would be to load not only the preferences related to Web POS dependant modules through the property, but also preferences which follow some naming convention related to Web POS payment information. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2013-03-26 13:12 | marvintm | New Issue | |||
| 2013-03-26 13:12 | marvintm | Assigned To | => marvintm | ||
| There are no notes attached to this issue. |