Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0036302Openbravo ERPA. Platformpublic2017-06-21 08:512017-07-04 08:37
AtulOpenbravo 
platform 
normalmajorhave not tried
closedopen 
5
 
 
caristu
Core
Production - Confirmed Stable
3.0PR16Q4
No
0036302: Display logic in fields is not working in callouts using SimpleCallout
Display logic for fields Order UOM and Order Quantity does not work in following callouts

1. SL_InOutLine_Product
2. SL_Inventory_Product
3. SL_Movement_Product

which are refactored to make use of SimpleCallout by using following statement

info.addResult("EXECUTE", "displayLogic();"); or
info.executeCodeInBrowser("displayLogic();");


Display logic properly worked in Servlet based callouts.
- Login as System Admin Role
- Mark as displayed = Yes fields
  - Window: Goods Receipt/ Shipment, Tab: Lines, Fields: Order Quantity, Order Uom
  - Window: Goods Movement, Tab: Lines, Fields: Order Quantity, Order Uom
  - Window: Physical Inventory, Tab: Lines, Fields: Order Quantity, Order Uom
- Logout
- Login as QA Testing Admin.
- Create a new Product "Test Product".
- Assign second UOM as Kilogram to "Test Product" in the UOM Tab
- Create a Goods Receipt
- Add a line and select the Test Product, enter Movement Quantity 1
- Realize that Order Uom and Order Quantity fields are not displayed.
- Save Record and Refresh (as Display Logic does not work)
- Realize that Order Uom and Order Quantity fields are displayed.
No tags attached.
related to design defect 0036067 closed markmm82 old callouts should be refactored to implement SimpleCallout 
related to design defect 00196753.0MP9 closed guilleaer Some callouts should be re-factorized 
caused by design defect 00323663.0PR16Q4 closed inigosanchez callout invocation ineficiencies 
related to defect 0036392 closed collazoandy4 Avoid casting to Object when adding numeric results from a SimpleCallout 
related to defect 0036590 closed markmm82 Callouts retrieve wrong quantity when Format.xml file is set with too many decimals 
Issue History
2017-06-21 08:51AtulOpenbravoNew Issue
2017-06-21 08:51AtulOpenbravoAssigned To => platform
2017-06-21 08:51AtulOpenbravoModules => Core
2017-06-21 08:51AtulOpenbravoTriggers an Emergency Pack => No
2017-06-21 11:00aferrazRegression level => Production - Confirmed Stable
2017-06-21 11:00aferrazRegression introduced in release => 3.0PR16Q4
2017-06-21 11:02aferrazRelationship addedcaused by 0032366
2017-06-21 11:02aferrazRelationship addedrelated to 0036067
2017-06-21 11:03aferrazRelationship addedrelated to 0019675
2017-07-04 08:33caristuRelationship addedrelated to 0036392
2017-07-04 08:37caristuReview Assigned To => caristu
2017-07-04 08:37caristuNote Added: 0097813
2017-07-04 08:37caristuStatusnew => closed
2017-07-04 08:38caristuNote Edited: 0097813bug_revision_view_page.php?bugnote_id=0097813#r15452
2017-07-04 08:53caristuNote Edited: 0097813bug_revision_view_page.php?bugnote_id=0097813#r15455
2017-08-18 12:57inigosanchezRelationship addedrelated to 0036590

Notes
(0097813)
caristu   
2017-07-04 08:37   
(edited on: 2017-07-04 08:53)
This problem is not caused by the usage of the "EXECUTE" callout command. This command is no longer supported and it is not needed because the display logics are recalculated on the FIC response.

Therefore this issue has been closed and the real problem has been reported here: 0036392