Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0037472Retail ModulesCash uppublic2017-12-13 18:472017-12-14 10:39
Reportergorkaion 
Assigned ToRetail 
PriorityhighSeverityminorReproducibilityN/A
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0037472: Differentiate syncrhonization errors that block cashup or not
DescriptionWhen processing a cashup if there is any record in the Errors While Importing of the terminal the process is stopped.

It would be nice if you could configure somehow which Import Entry Type of Data or which OBPOSErrors should block the cash up process.

This would allow to implement a custom data synchronization of an entity that does not affect the cashup process. So even if there are errors the cashup could be processed.
Steps To ReproduceCreate a custom data synchronization for an entity that does not affect the cashup.

Do some synchronization with errors so they are registered in the Errors While Importing window.

Try to process a cashup.
Proposed SolutionAdd a flag "blocks cashup" in OBPOSErrors with default value true.

Create a method that can be overridden in DataSyncronizationProcess or DataSynchronizationErrorHandler. So the implementation of the custom entity could override it to set the flag to false.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-12-13 18:47gorkaionNew Issue
2017-12-13 18:47gorkaionAssigned To => Retail
2017-12-13 18:47gorkaionTriggers an Emergency Pack => No

There are no notes attached to this issue.