[jbpm-dev] #JBPM-2506

Joram Barrez joram.barrez at gmail.com
Wed Dec 9 04:23:22 EST 2009


This is how the variables should be handled, so yes your description does
make a lot sense :-)
Most of them are already in the roadmap/jira normally.

On Tue, Dec 8, 2009 at 8:22 AM, Sebastian Schneider <
schneider at dvz.fh-aachen.de> wrote:

> Good morning,
>
> regarding issue #JBPM-2506 I have a question and some remarks:
>
> https://jira.jboss.org/jira/browse/JBPM-2506
>
> Does this issue just refer to process variables or also to
> task-variables? In case of task-variables I am proposing the following:
>
> - add an attribute stating if a task-variable is needed for a task to be
> completed properly or if the variable is optional
> - extend the API so that one can query the list of a task's variables
> - distinguish between optional and obligatory task-variables
>
> In combination with issue #JBPM-2609 this could simplify development of
> user interfaces which aim to be generic.
>
> https://jira.jboss.org/jira/browse/JBPM-2609
>
> Am I misleaded or does this make sense to you?
>
> Regards
>
> Sebastian
>
> --
> Sebastian Schneider
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbpm-dev/attachments/20091209/bcd41670/attachment.html 


More information about the jbpm-dev mailing list