Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0047517Retail ModulesWeb POSpublic2021-08-09 11:032021-10-29 12:03
Reporterfermin_ostivar 
Assigned ToRetail 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0047517: The screen Pay open tickets show paid tickets
DescriptionThe screen Pay open tickets show paid tickets
Steps To ReproduceBackoffice
Step 1:
Set Preference Web POS Prepayment Under Limit Approval -> Y , assign to a User.

Step 2:
In Touchpoint Type, Allow Prepayments and partial payments

Web pos
Step 3:
Pay a ticket partially

Step 4
Menu -> Pay Open tickets, select the ticket and pay total

Step 5
Menu -> Pay Open tickets, search by customer, the ticket is paid but it is shown


Updated Steps to Reproduce
POS - https://livebuilds.openbravo.com/retail_pi_pgsql/web/org.openbravo.retail.posterminal/?terminal=OMNI-1#retail.pointofsale [^]
Add Product and complete it
Open Pay open tickets
Last completed ticket should not be listed, But its listing
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0040087 closed javierRodriguez [RR19Q1] [OMNI] Usability of the new "Pay Open Tickets" pop up should be improved 
Attached Filespng Step1.png (55,149) 2021-08-09 11:03
https://issues.openbravo.com/file_download.php?file_id=16086&type=bug
png

png Step2.png (87,132) 2021-08-09 11:04
https://issues.openbravo.com/file_download.php?file_id=16087&type=bug
png

png Step31.png (75,269) 2021-08-09 11:04
https://issues.openbravo.com/file_download.php?file_id=16088&type=bug
png

png Step32.png (34,090) 2021-08-09 11:04
https://issues.openbravo.com/file_download.php?file_id=16089&type=bug
png

png Step41.png (72,011) 2021-08-09 11:04
https://issues.openbravo.com/file_download.php?file_id=16090&type=bug
png

png Step42.png (68,279) 2021-08-09 11:05
https://issues.openbravo.com/file_download.php?file_id=16091&type=bug
png

png Step51.png (26,390) 2021-08-09 11:05
https://issues.openbravo.com/file_download.php?file_id=16092&type=bug
png

png Step52.png (39,958) 2021-08-09 11:05
https://issues.openbravo.com/file_download.php?file_id=16093&type=bug
png

png Step53.png (335,329) 2021-08-09 11:05
https://issues.openbravo.com/file_download.php?file_id=16094&type=bug
Issue History
Date ModifiedUsernameFieldChange
2021-08-09 11:03fermin_ostivarNew Issue
2021-08-09 11:03fermin_ostivarAssigned To => Retail
2021-08-09 11:03fermin_ostivarFile Added: Step1.png
2021-08-09 11:03fermin_ostivarTriggers an Emergency Pack => No
2021-08-09 11:04fermin_ostivarFile Added: Step2.png
2021-08-09 11:04fermin_ostivarFile Added: Step31.png
2021-08-09 11:04fermin_ostivarFile Added: Step32.png
2021-08-09 11:04fermin_ostivarFile Added: Step41.png
2021-08-09 11:05fermin_ostivarFile Added: Step42.png
2021-08-09 11:05fermin_ostivarFile Added: Step51.png
2021-08-09 11:05fermin_ostivarFile Added: Step52.png
2021-08-09 11:05fermin_ostivarFile Added: Step53.png
2021-10-20 08:44ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2021-10-20 13:35ranjith_qualiantech_comSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=23216#r23216
2021-10-21 08:43ranjith_qualiantech_comRelationship addedrelated to 0040087
2021-10-21 08:55marvintmReview Assigned To => marvintm
2021-10-21 08:55marvintmNote Added: 0132513
2021-10-21 08:55marvintmStatusnew => closed
2021-10-21 08:55marvintmResolutionopen => no change required
2021-10-29 12:03marvintmTypedefect => design defect
2021-10-29 12:03marvintmAssigned Toranjith_qualiantech_com => Retail
2021-10-29 12:03marvintmStatusclosed => new
2021-10-29 12:03marvintmResolutionno change required => open

Notes
(0132513)
marvintm   
2021-10-21 08:55   
This is a limitation of the selector mainly for performance reasons. When it was initially implemented, we found that it was not possible to add payment-related restrictions to the main query as in environments with high volumes of data, it didn't work properly.

Therefore, the implementation doesn't initially filter for the orders that are already paid, but if you try to execute the flow after selecting an order that is already paid, it is correctly validated and a message is shown to the user.