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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0019595
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformminoralways2012-01-30 17:202013-01-03 13:12
ReportermaiteView Statuspublic 
Assigned ToAugustoMauch 
PrioritynormalResolutionfixedFixed in Version3.0MP19
StatusclosedFix in branchFixed in SCM revision51ea214b67be
ProjectionnoneETAnoneTarget Version3.0MP19
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Todbaz
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0019595: Enable "Display Logic" clauses to be working in Status Bar fields

DescriptionEnable "Display Logic" clauses to be working in Status Bar fields. Actually, if a field located in status bar has "Display Logic" associated, display logic rule is not considered
Steps To Reproduce1. Go to Business Partner window, and realize that "Customer Balance" field, showed in Status Bar, appears in both Customer and Vendor
2. If you review field's definition in "Windows, Tabs and Fields" you can verify that is has display logic associated
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 00052023.0MP19 closedAugustoMauch Implement display logic for tabs [No new BOM creation possible] 
related to defect 0022712 closedAugustoMauch Statusbar fields with display logic appear twice in the form 

-  Notes
(0052398)
AugustoMauch (manager)
2012-09-24 20:53

Effort: 5
Impact: low
Plan: mid
(0055227)
hgbot (developer)
2012-12-26 18:28

Repository: erp/devel/pi
Changeset: 51ea214b67be5b17f886a920f08430628ef8846f
Author: Augusto Mauch <augusto.mauch <at> openbravo.com>
Date: Wed Dec 26 18:26:12 2012 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/51ea214b67be5b17f886a920f08430628ef8846f [^]

Fixes issue 19595: Display logic can be applied to status bar fields

---
M modules/org.openbravo.client.application/src/org/openbravo/client/application/templates/ob-view-field.js.ftl
M modules/org.openbravo.client.application/src/org/openbravo/client/application/window/OBViewFieldHandler.java
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/ob-view-form.js
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/main/ob-standard-view.js
M src-db/database/sourcedata/AD_FIELD.xml
---
(0055228)
AugustoMauch (manager)
2012-12-26 18:32

Test plan:
Using the System Administrator role:
- Open the Windows, Tabs and Fields window
- Go to the field Sales Order -> Header -> Document Status. You might have to clear the filter, because the field is not displayed in the form, only in the status bar.
- Enter a valid display logic, i.e. @C_BPartner_ID@='9E6850C866BD4921AD0EB7F7796CE2C7'. With this display logic, the field will only be shown if the 'Hoteles Buenas Noches' business partner is selected.

Using the F&B role:
- Open sales order
- Create a new order using 'Hoteles Buenas Noches' as business partner. Save (until then the status bar fields are not shown), and check that the Document Status field is shown in the status bar. Change the business partner, and check that the Document Status field is no longer shown. Change it back, and check the it appears again.
(0055249)
dbaz (developer)
2012-12-27 16:00

Verified @ changeset: 19130 - 8643510fc80d
(0055324)
hudsonbot (developer)
2013-01-03 13:12

A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/792728467ed0 [^]

Maturity status: Test

- Issue History
Date Modified Username Field Change
2012-01-30 17:20 maite New Issue
2012-01-30 17:20 maite Assigned To => alostale
2012-01-30 17:20 maite Modules => Core
2012-01-30 17:20 maite Issue Monitored: networkb
2012-03-19 12:37 eintelau Issue Monitored: eintelau
2012-09-24 20:53 AugustoMauch Note Added: 0052398
2012-09-24 20:53 AugustoMauch Priority high => normal
2012-09-24 20:53 AugustoMauch Status new => scheduled
2012-11-23 08:04 alostale Relationship added related to 0005202
2012-11-23 08:06 alostale Target Version => 3.0MP19
2012-12-26 18:23 AugustoMauch Triggers an Emergency Pack => No
2012-12-26 18:23 AugustoMauch Assigned To alostale => AugustoMauch
2012-12-26 18:23 AugustoMauch Issue Monitored: dbaz
2012-12-26 18:28 hgbot Checkin
2012-12-26 18:28 hgbot Note Added: 0055227
2012-12-26 18:28 hgbot Status scheduled => resolved
2012-12-26 18:28 hgbot Resolution open => fixed
2012-12-26 18:28 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/51ea214b67be5b17f886a920f08430628ef8846f [^]
2012-12-26 18:32 AugustoMauch Note Added: 0055228
2012-12-27 16:00 dbaz Review Assigned To => dbaz
2012-12-27 16:00 dbaz Note Added: 0055249
2012-12-27 16:00 dbaz Status resolved => closed
2012-12-27 16:00 dbaz Fixed in Version => 3.0MP19
2012-12-31 13:10 AugustoMauch Relationship added related to 0022712
2013-01-03 13:12 hudsonbot Checkin
2013-01-03 13:12 hudsonbot Note Added: 0055324


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker