Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0047470Retail ModulesWeb POSpublic2021-07-28 12:432023-01-10 14:31
Reporterrafaroda 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityalways
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
Summary0047470: Cross Store: Anonymous Customer A of Store A is not considered Anonymous Customer in Store B
DescriptionCross Store: Anonymous Customer A of Store A is not considered Anonymous Customer in Store B
Steps To Reproduce* Store A and Store B have difefrent anonymous customer A and B
* Do a ticket in store A for Anonymous Customer of Store A
* Recall that ticket in Store B: the Anoynmous Customer A in Store B is NOT considered anonymous customer

So all the logics that apply to anonymnous customer are broken, for instance, the preference that says that we can't edit an anonymous customer, or that we can't invoice an anonymous customer
Proposed SolutionAn anonymous Customer A of Store A, should be also be considered an anonymous customer in the Store B
Additional Information
TagsNOR
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2021-07-28 12:43rafarodaNew Issue
2021-07-28 12:43rafarodaAssigned To => Retail
2021-07-28 12:43rafarodaTriggers an Emergency Pack => No
2021-07-28 12:43rafarodaResolution time => 1629410400
2021-07-28 12:43rafarodaTag Attached: NOR
2021-07-30 09:52adrianromeroStatusnew => acknowledged
2021-07-30 12:50jetxarriNote Added: 0130896
2021-08-04 17:34adrianromeroAssigned ToRetail => adrianromero
2021-08-04 17:34adrianromeroAssigned Toadrianromero => rafaroda
2021-08-04 17:35adrianromeroAssigned Torafaroda => prakashmurugesan88
2021-08-04 17:35adrianromeroStatusacknowledged => scheduled
2021-08-12 08:10marvintmResolution time1629410400 =>
2021-08-12 08:10marvintmNote Added: 0131088
2021-08-12 08:10marvintmTypedefect => design defect
2021-09-10 09:13prakashmurugesan88Assigned Toprakashmurugesan88 => Retail
2021-09-10 09:13prakashmurugesan88Statusscheduled => feedback
2023-01-10 14:31ngarciaStatusfeedback => new

Notes
(0130896)
jetxarri   
2021-07-30 12:50   
How I fixed for our client:
-extend bp model adding property
add(new HQLProperty(
            "coalesce((select max('true') from Organization o where o.obretcoCBpartner = bp), 'false') ",
            "isDefaultBp"));
-also adding in the front model
,
    {
      name: 'isDefaultBp',
      column: 'isDefaultBp',
      type: 'BOOLEAN'
    }

Apart from that I have created a global function to see if a bp is a default bp in any store
OB.NORCUS_UTILS.isDefaultBp = function(businesspartner) {
  if (
    businesspartner.has('isDefaultBp') &&
    businesspartner.get('isDefaultBp')
  ) {
    return true;
  } else {
    return false;
  }
};

And finally, instead of using
currentBP.id === anonymousBP
I am using
OB.NORCUS_UTILS.isDefaultBp(currentBP)
(0131088)
marvintm   
2021-08-12 08:10   
The cross-store functionality was mainly designed to be used together with specific business partners. That is why currently all these restrictions related to the anonymous customer do not currently work.

Of course, the changes required to make them work could be implemented, but we don't consider this a simple bug, it is a project that should be planned and designed first, and due to this we are changing this issue to "design defect".