Notes |
|
(0096426)
|
hgbot
|
2017-05-05 16:43
|
|
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: abe131fd8eceeaa85fc66b131a6e80df7aed0eae
Author: Mario Castello <mario.castello <at> peoplewalking.com>
Date: Wed May 03 07:49:25 2017 -0600
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/abe131fd8eceeaa85fc66b131a6e80df7aed0eae [^]
Fixed issue 0035830: [SER-QA 2681] One payment overpayments should be checked before invoking payment provider
- Added validation for payment provider to check the new payment before the provider will be executed
---
M web/org.openbravo.retail.posterminal/js/pointofsale/view/keyboard-toolbars.js
M web/org.openbravo.retail.posterminal/js/pointofsale/view/payment.js
---
|
|
|
(0096614)
|
hgbot
|
2017-05-16 10:28
|
|
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: cd13ce1880cacd17a67146e9961babdbc91309e7
Author: Miguel de Juana <miguel.dejuana <at> openbravo.com>
Date: Mon May 15 17:59:08 2017 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/cd13ce1880cacd17a67146e9961babdbc91309e7 [^]
Related issue 35830, related issue 35623
It is breaking I35623_OpenReceiptAndPaymentProvider
Backed out changeset abe131fd8ece
---
M web/org.openbravo.retail.posterminal/js/pointofsale/view/keyboard-toolbars.js
M web/org.openbravo.retail.posterminal/js/pointofsale/view/payment.js
---
|
|
|
|
It is breaking I35623_OpenReceiptAndPaymentProvider test |
|
|
(0097109)
|
guilleaer
|
2017-06-02 16:59
(edited on: 2017-06-02 17:06) |
|
Checking patches provided by Ranjith:
Note: Credit card is configured as "not overpayment" === 0 and provider === dialog
A:
1. Mark voucher with amount to change 0.
2. Add a product with value 18.90
3. Pay with 20 using voucher
4. Error: Systems alerts but you can confirm the receipt
B:
1. Having voucher configured to allow change/overpayment
2. Add a product with value 18.90
3. Pay 10 with voucher (allowed to change)
4. pay 10 with credit card (Not allowed change = 0)
5. It is not possible because car is not allowed to overpay
however doing the following
1. Having voucher configured to allow change/overpayment
2. Add a product with value 18.90
3. Pay 10 with credit card (Not allowed change = 0)
4. pay 10 with voucher (allowed to change)
5. You can complete the overpayment because it is assumed by voucher.
I think in both above scenarios the behavior should be equal, even more taking into account the next scenario
C:
1. Add a product with value 18.90
2. Pay 10 with cash
3. pay 10 with credit card (Not allowed change = 0)
4. It is possible because change can be given back by cash
In case B (first example) it is not working with voucher.
D:
Do a cashup keeping 0 in cash and repeat previous step
The system will allow to add the credit card payment, but later on it will say that you don't have enough cash to give back change so the operation cannot be finished. This case also should be supported since it is quite similar to the case reported in this issue.
Apart from above scenarios, I'm not able to pay with credit card using pay open tickets:
1) create an order with product with value 18.90
2) create other new order with product with value 18.90
3) open pay open tickets
4) select tickets created above
5) try to pay 40 with credit card
JS error is raised!
|
|
|
|
|
|
(0097276)
|
hgbot
|
2017-06-09 12:01
|
|
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: b62a7f268b87217cd4d4e06f8e9e3d7cdc02209a
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri Jun 09 15:30:15 2017 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/b62a7f268b87217cd4d4e06f8e9e3d7cdc02209a [^]
Fixed issue 35830 : Payment method amount should be prevalidated if it is configured with provider
---
M src-db/database/sourcedata/AD_MESSAGE.xml
M web/org.openbravo.retail.posterminal/js/pointofsale/view/keyboard-toolbars.js
M web/org.openbravo.retail.posterminal/js/pointofsale/view/payment.js
---
|
|
|
(0097279)
|
hgbot
|
2017-06-09 12:01
|
|
Repository: tools/automation/pi-mobile
Changeset: 768f87a4b568f7f9691db5b573254ca3c46ce172
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri Jun 09 15:10:39 2017 +0530
URL: http://code.openbravo.com/tools/automation/pi-mobile/rev/768f87a4b568f7f9691db5b573254ca3c46ce172 [^]
Verifies issue 35830 : Added automated test 'I35830_VerifyPreValidationPaymentProvider'
---
M src-test/org/openbravo/test/mobile/retail/pack/selenium/tests/reversepayments/NoCashWhenReverse.java
A src-test/org/openbravo/test/mobile/retail/pack/selenium/tests/receipts/I35830_VerifyPreValidationPaymentProvider.java
---
|
|
|
(0097290)
|
hgbot
|
2017-06-09 14:04
|
|
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: b8b3b65277f94b7e7e809b8720da53c569383f28
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri Jun 09 17:33:20 2017 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/b8b3b65277f94b7e7e809b8720da53c569383f28 [^]
Related to issue 35830 : Backedout changeset due to functionality change
Backed out changeset: b62a7f268b87
---
M src-db/database/sourcedata/AD_MESSAGE.xml
M web/org.openbravo.retail.posterminal/js/pointofsale/view/keyboard-toolbars.js
M web/org.openbravo.retail.posterminal/js/pointofsale/view/payment.js
---
|
|
|
(0097291)
|
hgbot
|
2017-06-09 14:04
|
|
Repository: tools/automation/pi-mobile
Changeset: a3d7997cb2afa868a262c6b451fa480f01e8f055
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri Jun 09 17:34:26 2017 +0530
URL: http://code.openbravo.com/tools/automation/pi-mobile/rev/a3d7997cb2afa868a262c6b451fa480f01e8f055 [^]
Related to issue 35830 : Backedout changeset due to functionality change
Backed out changeset: 768f87a4b568
---
M src-test/org/openbravo/test/mobile/retail/pack/selenium/tests/reversepayments/NoCashWhenReverse.java
R src-test/org/openbravo/test/mobile/retail/pack/selenium/tests/receipts/I35830_VerifyPreValidationPaymentProvider.java
---
|
|
|
|
This change cannot be done currently as it is, because we would be breaking the existing API of the payment method providers, and several current implementations would be broken already.
Most likely a new payment gateway API should be designed, taking into account all the automatic checks which didn't exist when the original payment gateway API was implemented. |
|