Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0043669
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] OMSminoralways2020-04-06 09:302020-05-19 16:39
Reporterinigo_lergaView Statuspublic 
Assigned Toinigo_lerga 
PrioritynormalResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned Tovmromanos
Regression introduced in release
Summary

0043669: No OMS Configuration message defined in wrong module

DescriptionIf some configuration is still not defined or missing, the OBOMSOC_NoOMSConfiguration message is thrown in the code.
This message is defined in the module "OMS Order Confirmation" instead of "Order Management System (OMS)", where it actually belongs.
Steps To Reproduce-
Proposed Solution1. Delete the message from OMS Order Confirmation module.
2. Create the message in Order Management System (OMS) module.
3. Modify the java implemmentation in Order Management System (OMS) module to add the organization name to the message during execution time.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0119047)
inigo_lerga (reporter)
2020-04-07 12:14
edited on: 2020-04-23 17:12

--Test Plan Mantis--
Beforehand, the environment needs to have the api generated
and NO OMS configuration setup.
  - Enter the OMS Web Service API
  - Select oms1.1.0
  - Press the Authorize button and Log in with
    Openbravo - openbravo as usual.
  - Open the OMS Web Service POST section (the green one)
  - Press the Try it out button
  - Select any example in the Examples selector
  - Execute the example
#In this moment the error message (filled with the Organization name in use without a OMS configuration) will be thrown as response#

(0120056)
hgbot (developer)
2020-05-19 16:34
edited on: 2020-05-19 16:38

Repository: erp/pmods/org.openbravo.retail.oms.orderconfirmation
Changeset: 91cde272ecc9
Author: Iñigo Lerga <inigo.lerga <at> openbravo.com>
Date: Thu Apr 24 10:11:18 2020 +0200
URL: https://code.openbravo.com/erp/pmods/org.openbravo.oms/rev/91cde272ecc9 [^]

fixes BUG 43669:Added correct message No OMS Config

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M src/org/openbravo/oms/engine/OMSEngine.java
---

(0120057)
hgbot (developer)
2020-05-19 16:34

Repository: erp/pmods/org.openbravo.retail.oms.orderconfirmation
Changeset: 854da45378a3942e521816b347458323e7660528
Author: Iñigo Lerga <inigo.lerga <at> openbravo.com>
Date: Thu Apr 23 17:07:58 2020 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.oms.orderconfirmation/rev/854da45378a3942e521816b347458323e7660528 [^]

related to ISSUE-43669: Removed message which belongs to OMS module

---
M src-db/database/sourcedata/AD_MESSAGE.xml
---
(0120059)
vmromanos (manager)
2020-05-19 16:39

Code review + testing OK

- Issue History
Date Modified Username Field Change
2020-04-06 09:30 inigo_lerga New Issue
2020-04-06 09:30 inigo_lerga Assigned To => inigo_lerga
2020-04-07 11:02 inigo_lerga Status new => scheduled
2020-04-07 12:14 inigo_lerga Note Added: 0119047
2020-04-23 17:12 inigo_lerga Note Edited: 0119047 View Revisions
2020-04-23 17:15 inigo_lerga Summary OBOMSOC_NoOMSConfiguration message not defined => No OMS Configuration message defined in wrong module
2020-04-23 17:15 inigo_lerga Description Updated View Revisions
2020-04-23 17:15 inigo_lerga Proposed Solution updated
2020-05-19 16:34 hgbot Checkin
2020-05-19 16:34 hgbot Note Added: 0120056
2020-05-19 16:34 hgbot Checkin
2020-05-19 16:34 hgbot Note Added: 0120057
2020-05-19 16:38 vmromanos Note Edited: 0120056 View Revisions
2020-05-19 16:38 vmromanos Status scheduled => resolved
2020-05-19 16:38 vmromanos Resolution open => fixed
2020-05-19 16:39 vmromanos Review Assigned To => vmromanos
2020-05-19 16:39 vmromanos Note Added: 0120059
2020-05-19 16:39 vmromanos Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker