Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0026569 | Openbravo ERP | A. Platform | public | 2014-05-16 10:49 | 2015-02-24 17:12 |
| Reporter | vmromanos | ||||
| Assigned To | AugustoMauch | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 20 | OS Version | Debian 5.0 | |
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0026569: Trees: it should be possible to define a read only tree where records can be deleted | ||||
| Description | Right now, when you define a tab with a read only tree, the delete button is disabled. If you want to delete a record you need to change to grid view and select the record(s) you want to delete. Besides, when changing to grid view, the order of the records is changed and it's very difficult to remember the record(s) you wanted to delete. I think it makes sense to specify if a tree allows to delete records regardless the read only flag. In this case the system should enable the delete button (and the delete record context menu entry). | ||||
| Steps To Reproduce | 1. Define a table with Is Tree = Y 2. Go to Table Tree Category tab and create a new record. Define any possible tree configuration 3. Into the tab associated to this table, set Read Only Tree = Y 4. Go to this tab, change to the tree view. The delete button is disabled. | ||||
| Proposed Solution | Allow to delete records from the tree view regardless the read only tree configuration. Probably the Node Deletion Policy at Table Tree Category tab can be used to define richer configuration, or alternatively a create a new flag at tab level. Not sure where is the best place to define it. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2014-05-16 10:49 | vmromanos | New Issue | |||
| 2014-05-16 10:49 | vmromanos | Assigned To | => AugustoMauch | ||
| 2014-05-16 10:49 | vmromanos | Modules | => Core | ||
| 2014-05-16 10:49 | vmromanos | Triggers an Emergency Pack | => No | ||
| 2015-02-24 17:12 | alostale | Note Added: 0074862 | |||
| 2015-02-24 17:12 | alostale | Type | defect => feature request | ||
| Notes | |||||
|
|
|||||
|
|
||||