On 22/03/12 20:02 +0100, Albert Cervera i Areny wrote: > A Dijous, 22 de marē de 2012 19:39:34, Cédric Krier va escriure: > > On 22/03/12 19:30 +0100, Jan Grasnick | grasbauer ug wrote: > > > if a workflow changes to a next state, the states (required, > > > invisible) of some fields are changing depending of the state, > > > defined in pyson-domains. It would be helpful, if the workflow > > > engine is checking this further states on writing and setting the > > > fields to required on the fly. We have implemented some workaround > > > in the write-method of the models, but I think there should be a > > > pre-evaluation of the required fields in the next state of the > > > workflow. > > > > I don't understand with a required states this is already possible and > > managed. > > I think that what he says is: given that you already define all possible > workflow transitions (using self._transitions), the system should > automatically > define the "states" attributes for self._buttons.
That's not always possible nor easy to do. And more over it will make button for "workflow" behaves differently as other buttons. -- 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/
pgpQSriLWADJk.pgp
Description: PGP signature
