Openbravo Issue Tracking System - Modules |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0043669 | Modules | OMS | public | 2020-04-06 09:30 | 2020-05-19 16:39 |
|
Reporter | inigo_lerga | |
Assigned To | inigo_lerga | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Regression date | |
Regression introduced by commit | |
Regression level | |
Review Assigned To | vmromanos |
Support ticket | |
OBNetwork customer | |
Regression introduced in release | |
|
Summary | 0043669: No OMS Configuration message defined in wrong module |
Description | If 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 Solution | 1. 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. |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
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 | bug_revision_view_page.php?bugnote_id=0119047#r20867 |
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 | bug_revision_view_page.php?rev_id=20869#r20869 |
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 | bug_revision_view_page.php?bugnote_id=0120056#r21067 |
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 |
Notes |
|
(0119047)
|
inigo_lerga
|
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
|
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
|
2020-05-19 16:34
|
|
|
|
|
|