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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0039080
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] 01. General setupmajorhave not tried2018-07-05 18:142018-08-03 14:20
ReporterplujanView Statuspublic 
Assigned Tocaristu 
PriorityimmediateResolutionfixedFixed in Version3.0PR18Q3
StatusclosedFix in branchFixed in SCM revision8fb3d93ea831
ProjectionnoneETAnoneTarget Version3.0PR18Q3
OSAnyDatabasePostgreSQLJava version
OS VersionDatabase versionAnt version
Product VersionmainSCM revision 
Review Assigned ToAugustoMauch
Web browser
ModulesCore
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
Summary

0039080: 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.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
blocks defect 0038907 closedcaristu DB errors which several OB messages are not correctly parsed in PG 

-  Notes
(0106117)
hgbot (developer)
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 (administrator)
2018-08-03 14:19

 Code reviewed and verified

- Issue History
Date Modified Username Field Change
2018-08-02 09:19 alostale Type defect => backport
2018-08-02 09:19 alostale Target Version => 3.0PR18Q3
2018-08-02 09:26 alostale Assigned To platform => caristu
2018-08-02 09:26 alostale Priority normal => immediate
2018-08-02 09:45 alostale Regression introduced in release 3.0PR17Q3 => main
2018-08-02 13:28 hgbot Checkin
2018-08-02 13:28 hgbot Note Added: 0106117
2018-08-02 13:28 hgbot Status scheduled => resolved
2018-08-02 13:28 hgbot Resolution open => fixed
2018-08-02 13:28 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR18Q3/rev/8fb3d93ea8318971e2fc1a0637fdbdeefe322fcb [^]
2018-08-02 13:28 caristu Review Assigned To => AugustoMauch
2018-08-03 14:19 AugustoMauch Note Added: 0106160
2018-08-03 14:19 AugustoMauch Status resolved => closed
2018-08-03 14:20 AugustoMauch Fixed in Version => 3.0PR18Q3

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker