-
1. Re: script tag in
phantomass Nov 3, 2005 12:47 PM (in response to phantomass)I've solved my problem.
I must put 'write' for the variable access. -
2. Re: script tag in
phantomass Nov 3, 2005 1:03 PM (in response to phantomass)Sorry the problem is still there. I didn't solve the problem.
If somebody has an idea.
Thanks -
3. Re: script tag in
kukeltje Nov 4, 2005 2:26 AM (in response to phantomass)can you provide a full testcase including a unit test?
-
4. Re: script tag in
tom.baeyens Nov 4, 2005 6:53 AM (in response to phantomass)it's a know problem. the script in a fork is not persisted. afaik this should have printed a warning while parsing the processdefinition.xml
we are going to extend the nodetypes. probably we will go into the direction of many node types with limited configuration options. instead of limited node types with extensive configuration options.
we have currently taken the approach to offer a limited set of node types for now. (we have done some research in test cases to verify that our core engine design actually covers all the workflow patterns) but we only documented the most used subselection of the node types and created documentation and persistence for that subset.
so in 3.2 you'll see the number of supported node types grow. we will have support for adding dynamic programming logic in a fork. not sure yet if this will be done in the current Fork implementation or in a differrent node type...
regards, tom. -
5. Re: script tag in
phantomass Nov 4, 2005 8:43 AM (in response to phantomass)Thank you Tom.
I'll try a work around with node and action delegation to do my dynamic execution path.
regards,
Jérôme