Gary Stocker schrieb: > We're making really good progress with our implementation of > ezcWorkflow, its proving to be really powerful and perfect for us, > thanks to all who've been involved with it :)
You are welcome, glad to hear that you like the component. > We have an input node that defines variables, we then want to show > another input node prepopulated with the same variables (so they can > be confirmed). > Our current observation is that the workflow doesn't suspend at this > second node, or at least they're not in the 'waitingFor' array of the > execution. That is correct: if you set a workflow variable, it cannot be requested as input anymore. > Do you have any advise/suggestions on how this could be achieved. I think this is something that should not (and probably cannot) be solved in a generic way in the workflow engine. It should be addressed in the application that embeds the workflow engine. > Second question, that could solve the first in effect is we capture > 'firstname' and 'lastname' in the workflow, and want to set a variable > later down to 'Hi '.firstname.lastname how could this be achieved with > the ezcWorkflowNodeVariableSet method? This is currently not implemented. Can you file an issue for this? Thanks! -- Sebastian Bergmann System Developer s...@ez.no | eZ Systems | http://ez.no
signature.asc
Description: OpenPGP digital signature
-- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
