[jboss-jira] [JBoss JIRA] Commented: (JBPM-955) jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes)

[Tom Baeyens (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-955?page=comments#action_12363882 ] 
            
Tom Baeyens commented on JBPM-955:
----------------------------------

"
    <process-state name="initial interview">
        <sub-process name="interview" />
        ...
        <swimlane name="candidate" />
        ...
    </process-state>

Is that what you propose? 
"

yes.  but also with a mapped-name that allows for translation of the swimlane instance to be stored under a different name in the sub process instance.

i still don't get quite what you propose. with looking upward.  in general, i'm very sceptical about references maintained between process instances.  we'll probably end up in more problems then we actually solve.

the proposal that i sketched makes sure that information is copied in from and potentially extracted from the sub process.  so the two process instances are independent. 

> 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