Openbravo Issue Tracking System - POS2
View Issue Details
0052143POS2POSpublic2023-04-17 18:502023-04-18 11:35
gorka_gil 
Retail 
lowmajoralways
closedno change required 
5
 
 
No
0052143: Pager flow: next button saves
Pager code it is applied clicking back/next

- Go to the POS2 terminal and log in
- Type 'Carbonio Helmet' in the POS2 search bar and add it
- When the first step of the pager view appears, click 'Next' to go to the second step
- Press any number of the keypad, for example 1
- Click apply -> it will close the setup and the info is correct in the ticket
- select the line of the ticket,
- select in the menu "edit pager information", it will open the pager setup
- go to next step
- change the 1 to 2
- go back
- press next

ERROR: the pager in the ticket line has change from 1 to 2, it should not apply the change in the next, but only the apply
No tags attached.
related to defect 0052146 scheduled Rajesh_18 0052143: Pager code is lost going back and forward 
related to defect 0051891 closed Vitaliy Malets Pager flow: incorrect behavior in the pager flow 
Issue History
2023-04-17 18:50gorka_gilNew Issue
2023-04-17 18:50gorka_gilAssigned To => Retail
2023-04-17 18:50gorka_gilTriggers an Emergency Pack => No
2023-04-17 18:50gorka_gilRelationship addedrelated to 0051891
2023-04-18 09:26mtaalNote Added: 0148522
2023-04-18 11:33gorka_gilDescription Updatedbug_revision_view_page.php?rev_id=25886#r25886
2023-04-18 11:33gorka_gilSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=25888#r25888
2023-04-18 11:35gorka_gilNote Added: 0148528
2023-04-18 11:35gorka_gilStatusnew => closed
2023-04-18 11:35gorka_gilResolutionopen => no change required
2023-04-18 11:35gorka_gilRelationship addedrelated to 0052146

Notes
(0148522)
mtaal   
2023-04-18 09:26   
I think error 1 is by-design (not an error, maybe a design defect). The pager setting works the same as product configuration. When you change a product modifier in a flow it also updates the ticket line right away.
(0148528)
gorka_gil   
2023-04-18 11:35   
Closing the issue, since this behavior it is the intended one.

Created another issue to track the lost of the code in the input going back and forward:
https://issues.openbravo.com/view.php?id=52146 [^]