Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminoralways2008-07-17 14:582009-05-22 19:34
ReportergalderromoView Statuspublic 
Assigned Toiciordia 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
Projection@40@ETAnoneTarget Version
OSLinux 32 bitDatabaseOracleJava version1.5.0_15
OS VersionGentoo 2.6.24Database versionXEAnt version1.7
Product Version2.40betaSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0004434: Uneditable fields souldn't be list (drop)

DescriptionHaving an uneditable field means can't be changed. So does not make sense being a value list (tabledir, list, etc.).
This issue is very important when you have a huge amount of data, because the application slows down and the performance is not acceptable.
Steps To ReproduceFor example,
Supposing you have 20.000 business partners on you C_BPARTNER table.
Go to Business partner window, bank account tab, and check how long it takes to load the business partner uneditable list.
Proposed SolutionChange all uneditable list to search for business partners, products, accounts, projects, etc. For the rest of the cases, find a suitable solution.

Take into account, that an uneditable search field just loads and shoes one record.
TagsPerformance, ReleaseCandidate, ToBeReviewed
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
galderromo (reporter)
2008-07-17 15:09

Also appends on the dictionary:
Go to:
- WINDOW: Windows, tabs and fields.
- TAB: Tabs
- TAB: Fields
- TAB: Field translation.
- Being AD_FIELD_ID uneditable the application loads all the data on table AD_FIELD.
cromero (reporter)
2008-07-22 09:27

There are some problems related to this issue that should be take into account and that is why I prefer change this issue to 'Feature request':
* Read only logic: now you can have fields that depending on the values of the fields in the page can be readonly or not.
* Callouts: it is normal that fields that are readonly and can not be modified by the user can be modified via callouts. So, this issue should also modify all the callouts in order to read and set the proper value.

- Issue History
Date Modified Username Field Change
2008-07-17 14:58 galderromo New Issue
2008-07-17 14:58 galderromo Assigned To => cromero
2008-07-17 14:58 galderromo sf_bug_id 0 => 2020579
2008-07-17 15:09 galderromo Note Added: 0008326
2008-07-22 09:27 cromero Note Added: 0008354
2008-07-22 09:27 cromero Type defect => feature request
2008-11-10 13:10 cromero Assigned To cromero => pjuvara
2008-11-16 15:27 pjuvara Tag Attached: ReleaseCandidate
2008-11-16 15:28 pjuvara Status new => acknowledged
2008-11-16 15:28 pjuvara Projection none => @40@
2008-11-16 15:28 pjuvara Category I. Performance => A. Platform
2008-11-16 15:28 pjuvara Tag Attached: ToBeReviewed
2008-11-16 15:29 pjuvara Tag Attached: Performance
2009-05-22 19:34 pjuvara Assigned To pjuvara => iciordia

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker