[
http://jira.jboss.com/jira/browse/JBPM-955?page=comments#action_12363864 ]
Arjan van Bentem commented on JBPM-955:
---------------------------------------
Errr, sorry... On second thought I think that
<task swimlane='#{jbpmSwimlane}'>
is not to be preferred. This would force one to know in advance how the generic
sub-process will be used by other processes. Above, the interview sub-process might be
used for the actor "candidate" and, at some other point in the process, for the
swimlane "collegeuas". The above would not allow for that.
The feature request in short: could jBPM iterate the process graph (thus recursively also
going up in any parent process-state) until some Swimlane or Actor is found? If yes, then
one should be allowed to set a swimlane, actor or pooled-actors on:
- <process-definition>
- <process-state>
- <task> (no change needed)
Arjan.
jBPM: support setting Actor or Swimlane on process level (to re-use
sub-processes)
----------------------------------------------------------------------------------
Key: JBPM-955
URL:
http://jira.jboss.com/jira/browse/JBPM-955
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Environment: All
Reporter: Arjan van Bentem
Assigned To: Tom Baeyens
Priority: Minor
Currently, an Actor or Swimlane is assigned within the task definition. When using
sub-processes it would be very convenient to make the assignments in the parent process,
such as in the parent <process-state>, or maybe even in the outermost
<process-definition>.
For example: both a helpdesk employee and the customer would need to fill in the same
questionnaire at different points in the main process. The steps to fill in the
questionnaire would be a generic sub-process, in which (at design time) one would not know
the Swimlane nor Actor. This would require a way to set the swimlane in the parent's
process-state:
<!-- multiple references to the same sub-process, for different swimlanes -->
<process-state name="Customer survey" swimlane="client">
<sub-process name="survey" />
</process-state>
:
:
<process-state name="Employee survey" swimlane="employer">
<sub-process name="survey" />
</process-state>
... or
<process-state name="Employee survey">
<assignment actor-id="..."/>
<sub-process name="survey" />
</process-state>
... or maybe even at an even higher level, where jBPM would iterate up into the chain,
possibly though nested sub-processes, until some assignment is found?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira