On Tue, Jun 3, 2008 at 2:10 AM, Diego Moreno <[EMAIL PROTECTED]> wrote: > >> Variables are not accessible outside of the engine as workitems are. >> You can copy the value of a variable into a workitem field (attribute) >> with the "set" expression. > > Yes, I think this solution could be better. I will edit the update method in > the workitem controller, so when it receives the params from the formulary: > 1) It loads the field that I want to be persistent from the database. > 2) It updates the fields with params from formulary (erasing the previous > fields, including my persistent field) > 3) It adds, again, the persistent field loaded previously to the workitem. > > By this way, it is possible I get to have some persistent variables > associated with one workflow. I will try this way.
Have a look at filter and filter-definition, it's really meant for restricting the fields passed to the participant and for enforcing those restriction when the workitem comes back from the participant. It might save you lots of time. Ruote-web doesn't receive the info though, but the engine enforces the filters, outbound and inbound. Best regards, -- John Mettraux - http://jmettraux.wordpress.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
