This is how the variables should be handled, so yes your description does make a lot sense :-)<br>Most of them are already in the roadmap/jira normally.<br><br><div class="gmail_quote">On Tue, Dec 8, 2009 at 8:22 AM, Sebastian Schneider <span dir="ltr"><<a href="mailto:schneider@dvz.fh-aachen.de">schneider@dvz.fh-aachen.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Good morning,<br>
<br>
regarding issue #JBPM-2506 I have a question and some remarks:<br>
<br>
<a href="https://jira.jboss.org/jira/browse/JBPM-2506" target="_blank">https://jira.jboss.org/jira/browse/JBPM-2506</a><br>
<br>
Does this issue just refer to process variables or also to<br>
task-variables? In case of task-variables I am proposing the following:<br>
<br>
- add an attribute stating if a task-variable is needed for a task to be<br>
completed properly or if the variable is optional<br>
- extend the API so that one can query the list of a task's variables<br>
- distinguish between optional and obligatory task-variables<br>
<br>
In combination with issue #JBPM-2609 this could simplify development of<br>
user interfaces which aim to be generic.<br>
<br>
<a href="https://jira.jboss.org/jira/browse/JBPM-2609" target="_blank">https://jira.jboss.org/jira/browse/JBPM-2609</a><br>
<br>
Am I misleaded or does this make sense to you?<br>
<br>
Regards<br>
<br>
Sebastian<br>
<font color="#888888"><br>
--<br>
Sebastian Schneider<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbpm-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
</font></blockquote></div><br>