]
Thomas Diesler updated JBPM-955:
--------------------------------
Fix Version/s: jBPM 3.3.2 GA
Revisit issues that have votes
jBPM: support setting Actor or Swimlane on process level (to re-use
sub-processes)
----------------------------------------------------------------------------------
Key: JBPM-955
URL:
https://jira.jboss.org/jira/browse/JBPM-955
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.2.0
Environment: All
Reporter: Arjan van Bentem
Priority: Minor
Fix For: jBPM 3.3.2 GA
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: