Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0036305 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Retail Modules] StoreServer | major | have not tried | 2017-06-22 10:24 | 2017-06-26 09:10 | |||
| Reporter | AugustoMauch | View Status | public | |||||
| Assigned To | AugustoMauch | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | RR17Q3 | |||
| Status | closed | Fix in branch | Fixed in SCM revision | 8f64435de0a2 | ||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Review Assigned To | mtaal | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0036305: Location router is not properly defined | |||||||
| Description | The Location router should work like this: - If the location belongs to a business partner, then its change should be sent to the servers that have access to the business partner - If not, the organization of the location is used to route the change But what is actually happening is: - The change is routed to all the records with access to the organization and the location - On top of that, it is also being sent to the servers that have access to the business partner related with the organization This results in the change being sent to more servers than needed. | |||||||
| Steps To Reproduce | In a multiserver environment: - Create a location in the * organization, assign it to a business partner - Modify the location - Check that the change is sent to all the store servers, instead of only the store server that have access to the business partner | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0097606) hgbot (developer) 2017-06-23 11:36 |
Repository: erp/pmods/org.openbravo.retail.storeserver.synchronization Changeset: 8f64435de0a2b0e84fcf83a74ae2f813994028d5 Author: Augusto Mauch <augusto.mauch <at> openbravo.com> Date: Fri Jun 23 11:35:07 2017 +0200 URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.storeserver.synchronization/rev/8f64435de0a2b0e84fcf83a74ae2f813994028d5 [^] Fixes issue 36305: Location router works properly for bp locations If a location belongs to a business partner, then it will not be routed based on its organization, it will be routed to the servers where its business partner belongs to. --- M src/org/openbravo/retail/storeserver/synchronization/router/LocationRouter.java --- |
|
(0097631) mtaal (manager) 2017-06-26 09:10 |
Reviewed and tested |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-06-22 10:24 | AugustoMauch | New Issue | |
| 2017-06-22 10:24 | AugustoMauch | Assigned To | => AugustoMauch |
| 2017-06-22 10:24 | AugustoMauch | Triggers an Emergency Pack | => No |
| 2017-06-23 11:35 | AugustoMauch | Review Assigned To | => mtaal |
| 2017-06-23 11:36 | hgbot | Checkin | |
| 2017-06-23 11:36 | hgbot | Note Added: 0097606 | |
| 2017-06-23 11:36 | hgbot | Status | new => resolved |
| 2017-06-23 11:36 | hgbot | Resolution | open => fixed |
| 2017-06-23 11:36 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/pmods/org.openbravo.retail.storeserver.synchronization/rev/8f64435de0a2b0e84fcf83a74ae2f813994028d5 [^] |
| 2017-06-26 09:10 | mtaal | Note Added: 0097631 | |
| 2017-06-26 09:10 | mtaal | Status | resolved => closed |
| 2017-06-26 09:10 | mtaal | Fixed in Version | => RR17Q3 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |