Openbravo Issue Tracking System - Openbravo ERP | |||||||||||||||||||
View Issue Details | |||||||||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||||||||
0022127 | Openbravo ERP | A. Platform | public | 2012-10-29 09:31 | 2016-02-29 17:52 | ||||||||||||||
Reporter | marvintm | ||||||||||||||||||
Assigned To | AugustoMauch | ||||||||||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||||||||||
Status | new | Resolution | open | ||||||||||||||||
Platform | OS | 5 | OS Version | ||||||||||||||||
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 | 0022127: Ability to define datasets as "not updateable", so that they are initially created but afterwards not updated | ||||||||||||||||||
Description | Currently, if a module adds a dataset to the system, it is considered the owner of the dataset, so if the customer updates the module, then the Enterprise Module Management can be used to update the dataset information. There is no way to define that a specific dataset should not be updated in any case. Therefore, if a dataset contains "configuration"-like information, which the customer may want to change, the next time the module which owns it is updated, the changes done by the customer will be overridden. It would be useful to be able to define a dataset as "not updateable". In this case, the dataset would be initially created in the system, but afterwards, even if the module is updated, its contents would not be changed. In other words, after the dataset is created in the system, the customer would be the owner of the data, and would be able to change its contents as he wishes. In the future, this distinction between "updateable" and "not updateable" could also be moved down to dataset table level, and even to dataset column level. | ||||||||||||||||||
Steps To Reproduce | This feature request basically is related to the ability to apply datasets, done mainly in Initial Client Setup and Initial Organization Setup. | ||||||||||||||||||
Proposed Solution | |||||||||||||||||||
Additional Information | |||||||||||||||||||
Tags | No tags attached. | ||||||||||||||||||
Relationships |
| ||||||||||||||||||
Attached Files | |||||||||||||||||||
Issue History | |||||||||||||||||||
Date Modified | Username | Field | Change | ||||||||||||||||
2012-10-29 09:31 | marvintm | New Issue | |||||||||||||||||
2012-10-29 09:31 | marvintm | Assigned To | => AugustoMauch | ||||||||||||||||
2012-10-29 09:31 | marvintm | Modules | => Core | ||||||||||||||||
2016-02-29 17:49 | ngarcia | Relationship added | has duplicate 0015000 | ||||||||||||||||
2016-02-29 17:52 | ngarcia | Relationship added | related to 0015951 |
There are no notes attached to this issue. |