Cedk, Might be a bit different or impractical in speed.
Can the trigger be designed as multi rule, multi action compatible? Example: ir.trigger <<O2M>> ir.trigger.rules ir.trigger <<O2M>> ir.trigger.actions And each rule could have a property of 'Rule Logic' to say And, Or in the way they should be executed. Is it making too complex? I am not sure . Thanks On Fri, May 14, 2010 at 8:38 PM, Cédric Krier <[email protected]> wrote: > On 14/05/10 20:08 +0200, Cédric Krier wrote: > > Hi, > > > > I will start to work on trigger this W-E. > > Could you review the blueprint [1] before I start coding? > > > > Thanks. > > > > [1] http://code.google.com/p/tryton/wiki/TriggerIntegration > > > > I think about having only one condition field that will be used for each > cases: > > - create: if evaluated to True after creation then fire the action > - write: if evaluated to False before write and to True after then fire the > action > - delete: if evaluated to True before deletion the fire the action > > -- > Cédric Krier > > B2CK SPRL > Rue de Rotterdam, 4 > 4000 Liège > Belgium > Tel: +32 472 54 46 59 > Email/Jabber: [email protected] > Website: http://www.b2ck.com/ > -- Sharoon Thomas Business Analyst & Open Source ERP Consultant CEO @ http://openlabs.co.in -- [email protected] mailing list
