Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0039080Openbravo ERP01. General setuppublic2018-07-05 18:142018-08-03 14:20
Reporterplujan 
Assigned Tocaristu 
PriorityimmediateSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionmain 
Target Version3.0PR18Q3Fixed in Version3.0PR18Q3 
Merge Request Status
Review Assigned ToAugustoMauch
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression levelQA functional test
Regression date2018-06-28
Regression introduced in releasemain
Regression introduced by commithttps://code.openbravo.com/erp/devel/pi/rev/ed73bce3ae3b093cba0908df13b6ffabb73f6564 [^]
Triggers an Emergency PackNo
Summary0039080: DB errors which several OB messages are not correctly parsed in PG
DescriptionWhen creating a Sales Order and one of the lines contains a product that has been marked as "Obsolete" the error message on booking the order says:

"Error: Please verify its PLM Status"
Steps To Reproduce1. Having a product marked as Obsolete in its PLM Status, create a new Sales Order
2. Add several lines containing active products and one line containing the obsolete one.
3. Try to book the order. The message shown does not point out which was the obsolete product, making the message not practical. See attached screenshot.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
blocks defect 0038907 closed caristu DB errors which several OB messages are not correctly parsed in PG 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-08-02 09:19alostaleTypedefect => backport
2018-08-02 09:19alostaleTarget Version => 3.0PR18Q3
2018-08-02 09:26alostaleAssigned Toplatform => caristu
2018-08-02 09:26alostalePrioritynormal => immediate
2018-08-02 09:45alostaleRegression introduced in release3.0PR17Q3 => main
2018-08-02 13:28hgbotCheckin
2018-08-02 13:28hgbotNote Added: 0106117
2018-08-02 13:28hgbotStatusscheduled => resolved
2018-08-02 13:28hgbotResolutionopen => fixed
2018-08-02 13:28hgbotFixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR18Q3/rev/8fb3d93ea8318971e2fc1a0637fdbdeefe322fcb [^]
2018-08-02 13:28caristuReview Assigned To => AugustoMauch
2018-08-03 14:19AugustoMauchNote Added: 0106160
2018-08-03 14:19AugustoMauchStatusresolved => closed
2018-08-03 14:20AugustoMauchFixed in Version => 3.0PR18Q3

Notes
(0106117)
hgbot   
2018-08-02 13:28   
Repository: erp/backports/3.0PR18Q3
Changeset: 8fb3d93ea8318971e2fc1a0637fdbdeefe322fcb
Author: Carlos Aristu <carlos.aristu <at> openbravo.com>
Date: Thu Aug 02 13:03:20 2018 +0200
URL: http://code.openbravo.com/erp/backports/3.0PR18Q3/rev/8fb3d93ea8318971e2fc1a0637fdbdeefe322fcb [^]

fixes bug 39080: PG error text parser is not translating properly some messages

  Fix for issue 0038827 was not taking into accout the possibility of having multiple translatable elements (text surrounded by @) in the same error message.

  Therefore, it has been restored the previous regular expression, and we are now directly stripping the part that contains the technical information of a trigger failure from the DB message returned by PostgreSQL.

---
M src/org/openbravo/erpCommon/utility/ErrorTextParserPOSTGRE.java
---
(0106160)
AugustoMauch   
2018-08-03 14:19   
Code reviewed and verified