Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 01. General setupmajoralways2021-07-13 10:112021-07-13 11:36
ReporteravicenteView Statuspublic 
Assigned ToTriage Omni OMS 
PriorityhighResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0047380: Copy Retail Store doesn't copy the field 'Channel - Touchpoint || Blockchain Initialized'

DescriptionNote: the following modules must be installed:

When new touchpoints will be created through the process Copy Retail Store, if the Legal entity of the store has the field 'Initialize Blockchain in New POS Touchpoints'=Yes, the new touchpoints must be created with the field 'Blockchain Initialized'=Yes. Now, they are created with 'Blockchain Initialized'=No.

It is not working properly when a new store is created with or without excel.
Steps To ReproduceNote: the following modules must be installed:

1. Through the process 'Copy Retail Store', create a new store that belongs to a legal entity defined as Initialize Blockchain in New POS Touchpoints'=Yes. Check that the new touchpoints for the new store are created as 'Blockchain Initialized'=No. They must be created as 'Blockchain Initialized'=Yes.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0045015 closedvmromanos Openbravo Localizations Copy Store not working with Frenc Certification 

-  Notes
avicente (developer)
2021-07-13 10:13

Project developer comment: "After reviewing this issue with Product Team, I have come to the conclusion that the Ticket Initialization(blockchain) process can not be integrated in the CopyStore process, at least not in a way that doesn’t affect the CopyStore’s flow itself.
The main reason is that the logic that determines whether a new terminal is set in the blockchain or not, is run in a database trigger. So, every time a new terminal record is inserted in the database, the blockchain logic runs, but at that moment, since the CopyStore hasn’t persisted yet the newly generated data, the blockchain logic fails (the new store/organization still doesn’t exist in database)."
dmiguelez (developer)
2021-07-13 11:36

As explained by the developer there is no obvious solution for this problem, so it is updated as a design defect to be managed accordingly (resolution date removed like for any other design defect not analyzed yet)

- Issue History
Date Modified Username Field Change
2021-07-13 10:11 avicente New Issue
2021-07-13 10:11 avicente Assigned To => Triage Finance
2021-07-13 10:11 avicente Modules => Core
2021-07-13 10:11 avicente Resolution time => 1627682400
2021-07-13 10:11 avicente Triggers an Emergency Pack => No
2021-07-13 10:12 avicente Tag Attached: NOR
2021-07-13 10:13 avicente Note Added: 0130402
2021-07-13 11:16 rafaroda Issue Monitored: rafaroda
2021-07-13 11:35 dmiguelez Relationship added related to 0045015
2021-07-13 11:36 dmiguelez Resolution time 1627682400 =>
2021-07-13 11:36 dmiguelez Note Added: 0130407
2021-07-13 11:36 dmiguelez Type defect => design defect

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker