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

[Arjan van Bentem (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-955?page=comments#action_12363858 ] 
            
Arjan van Bentem commented on JBPM-955:
---------------------------------------


> so the same way as you can map variables to sub processes, you want to
> map swimlanes to sub processes. would that cover your feature request ?

I guess you're referring to for example:

    <process-state name="initial interview">
        <sub-process name="interview" />
        <variable name="a" access="read,write" mapped-name="aa" />
        ...
    </process-state>

...which could then be enhanced to allow for

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

Is that what you propose? If so:

- maybe some others would like to set an explicit actor, not the swimlane (so that would need an <assignment> mapping as well)

- if a sub-process is invoked from within another sub-process then one may not know the hardcoded swimlane name ("candidate" in the example above, or "client" and "employer" in my first post)

So I guess it would cover my current needs, but I'm not sure if the above would yield the most flexible solution. And it can probably just as easy be implemented using some custom component:

    <task name="survey">
        <assignment actor-id="#{myCustomTaskAssignerComponent.surveyActor.id}"/>
    </task>	

Maybe it would be more flexible to either have jBPM search for an assignment (swimlane or actor, whichever is found first) anywhere up in the calling tree, or to make the current swimlane somehow available in expressions. As for the latter, one could then simply use:

    <task swimlane='#{jbpmSwimlane}' />

If this is doable, then I guess others might like the current actor to be available in expressions as well.

Does this answer your question?

Thanks,
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