Olivier, Are you sure it's a good idea to allow context in workflows ?
Workflows are not used for user interface interactions, but for controlling the evolution of the object. It has no sense to put context on constraints and, for the same reason, I don't think we should allow context in workflows. An activity should not depend on a context but on data stored on the object. The goal of the workflow is to easily modify it, add/remove some transitions, etc. If we depend on contexts, we may loose this modularity. I am still not sure about this, but I would not allow the context to be used in workflows, for the same reason that it has no sense to put context on constraints. On 13/12/11 19:05, Olivier Dony (OpenERP) wrote: > FWIW, you can have a look at the branch where I tested merging the same > thing[1]. > > As I explain on my merge prop there, I think we need more work on the addons > side in order to get any benefit from this work, and that will be much more > tricky. I started a wip of changing addons in this manner[2] but it is far > from complete or working yet, and perhaps it's too much at this point. > > > [1] lp:~openerp-dev/openobject-server/trunk-workflow-context-odo > [2] lp:~openerp-dev/openobject-addons/trunk-workflow-context-odo > -- https://code.launchpad.net/~openerp-community/openobject-server/context-in-workflows/+merge/85518 Your team OpenERP Community is subscribed to branch lp:~openerp-community/openobject-server/context-in-workflows. _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
