Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0043887Retail ModulesWeb POSpublic2020-04-28 15:092020-05-27 17:18
Reporterranjith_qualiantech_com 
Assigned Toranjith_qualiantech_com 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR20Q3 
Merge Request Status
Review Assigned Toadrianromero
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0043887: DocumentNo Threshold not updated properly when reloading the POS
DescriptionWhen POS has unpaid receipt, if user reloads the POS, DocumentNo Threshold was not updated properly after loading unpaid receipts
Steps To Reproducein POS
Get Doc No
Add Product
reload POS
Check Doc No - It should not be changed. OK
Delete receipt
Check Doc No - its changed, incremented by 1, KO
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2020-04-28 15:09ranjith_qualiantech_comNew Issue
2020-04-28 15:09ranjith_qualiantech_comAssigned To => ranjith_qualiantech_com
2020-04-28 15:09ranjith_qualiantech_comTriggers an Emergency Pack => No
2020-05-22 12:39ranjith_qualiantech_comStatusnew => scheduled
2020-05-22 12:39ranjith_qualiantech_comNote Added: 0120178
2020-05-22 12:39ranjith_qualiantech_comStatusscheduled => resolved
2020-05-22 12:39ranjith_qualiantech_comResolutionopen => fixed
2020-05-27 17:18adrianromeroReview Assigned To => adrianromero
2020-05-27 17:18adrianromeroNote Added: 0120369
2020-05-27 17:18adrianromeroStatusresolved => closed
2020-05-27 17:18adrianromeroFixed in Version => RR20Q3

Notes
(0120178)
ranjith_qualiantech_com   
2020-05-22 12:39   
Fixed in [indexedDB-state-docseq] branch
(0120369)
adrianromero   
2020-05-27 17:18   
With the current behaviour the document is generated when closing the receipt, not when the receipt is created.

Both flows described in the issue works properly and the application does not generate holes in the document numbers sequence.