Am 22.04.2015 um 16:34 schrieb Prakash Pandey: > Hello folks, > Hi
> I am not sure how useful this feature would be and the areas where we > can use this. Thoughts please? > I'm very interested ... and still working on a module which will extend the history with a kind of version control The module [1] is in a really bad state. It's only a proof of concept - only follow, never try it :). It needs also a patch to add datetime_field to field.Reference. I opened a issue already and I'm working on this. The idea: You can set special records to 'version control' - if you create a version for a record and the version is approved, you can use them as many2one, one2many and reference in other models. If state is 'Under review' or 'Rejected' the client rises an error if you are try to link them to a record. If someone change a approved record, a new version with state 'Under review' is created and you can't use the record until the revison is approved by a reviewer. Each revision is linked to a _history entry of the record - so we need to apply _history to all models involved. Beside the problems with programming the module itself, I'm also searching for a way to apply the new functions to a set of models. Jan [1] http://review.gewinnmonitor.de/record_revision
