On 2017-03-15 04:31, edbo.des...@gmail.com wrote: > I'm working on a review and revise module. This module have a workflow with > the states "draft" -> "review" -> "released" . The data can only be edited > when in state "draft". When in state "released" and a user wants to change > it, the state goes back to "draft". But in that transaction (from > "released" to "draft") I want to store a copy of the data. > > Instead of writing my own history table and functionality I want to use the > standard _history = true . But then I get on all write-actions a new copy > in the history-table.
And what is the problem? > What are the (other) possibilities? The history feature is designed to be a complete history without any lost. So you can not skip it. One feature that could be interesting is to allow to tag some history record to easily go back to them instead of using only the datetime. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ -- You received this message because you are subscribed to the Google Groups "tryton-dev" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton-dev/20170315131307.GC43953%40tetsuo.
