2008/6/2 John Mettraux <[EMAIL PROTECTED]>: > maybe you could "hide" the field via javascript and have a button for > showing it (see [1] which is included in Rails and therefore in > ruote-web), so that the user could unhide the input field and change > its value at will. >
Maybe I did not explain it clearly. I do not want the user to have the possibility to change these variables. For that reason, this solution is not suitable for me. > The variables are stored in "environment" expressions which correspond > to the scopes in the process definition languages. All the expressions > are stored in an expression storage. By default, ruote-web stores the > expression in files under work_development/expool/ > > 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. Thank you very much for the help, John. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
