Openbravo Issue Tracking System - Retail Modules |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0041428 | Retail Modules | Web POS | public | 2019-07-23 10:12 | 2019-09-12 09:57 |
|
Reporter | adrianromero | |
Assigned To | adrianromero | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | RR19Q4 | |
Merge Request Status | |
Review Assigned To | marvintm |
OBNetwork customer | No |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0041428: Define a new Payment type UNDEFINED to always have a payment method to assign transactions |
Description | In the functionality Payment Methods grouping by Provider http://wiki.openbravo.com/wiki/Retail:Payment_Methods_grouping_by_Provider_User_Guide [^] may happen if there is not a payment method defined with the type returned by the provider. If this is the case an error is displayed to the user warning that the payment has been charged to the customer but it cannot be added any payment line to the receipt because there is not any payment method that can be assigned to the type returned.
This situation is hard to manage because the customer has been charged and the money must be returned to him manually. |
Steps To Reproduce | In description |
Proposed Solution | Create an special payment type named "UNDEFINED" that in case there is no payment method with the payment type returned by the payment provider then use the payment method with the special payment type "UNDEFINED".
This way, all approved transactions will have a payment method even in the case there is no match because in this case the payment method with payment type "UNDEFINED" will be used. |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2019-07-23 10:12 | adrianromero | New Issue | |
2019-07-23 10:12 | adrianromero | Assigned To | => Retail |
2019-07-23 10:12 | adrianromero | OBNetwork customer | => No |
2019-07-23 10:12 | adrianromero | Triggers an Emergency Pack | => No |
2019-08-29 08:59 | hgbot | Checkin | |
2019-08-29 08:59 | hgbot | Note Added: 0114316 | |
2019-08-29 08:59 | hgbot | Status | new => resolved |
2019-08-29 08:59 | hgbot | Resolution | open => fixed |
2019-08-29 08:59 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/174cc3511d2f16b9c129ec72373a258fb42701f1 [^] |
2019-09-03 09:26 | shuehner | Assigned To | Retail => adrianromero |
2019-09-12 09:57 | marvintm | Review Assigned To | => marvintm |
2019-09-12 09:57 | marvintm | Status | resolved => closed |
2019-09-12 09:57 | marvintm | Fixed in Version | => RR19Q4 |