Moving from Mail to forum:
Ronald:
| >>> This works:
| >>>
| >>> <bpmn:userTask id="UserTask" name="user
task"
| >>> implementation="other">
| >>> <!-- use jbpm internal task management -->
| >>> <bpmn:performer id="myPerformer"
| >>> resourceRef="sampleResource">
| >>> <bpmn:resourceAssignmentExpression
| >>> id="rae">
| >>> <bpmn:formalExpression
| >>>
language="juel">${assignedUser}</bpmn:formalExpression>
| >>> </bpmn:resourceAssignmentExpression>
| >>> </bpmn:performer>
| >>> <bpmn:rendering id="myRendering">
| >>> <jbpm:form>MyForm.ftl</jbpm:form>
| >>> </bpmn:rendering>
| >>> </bpmn:userTask>
| >>>
| >>> Assigning a task to a user while parsing a processvariable. Not sure
| >>> how I have to use the resource though, that's still a blurry subject
| >>> for me in this regard.
| >>>
| >>> What also works is setting the form on the taskDefinition based on
| >>> the jbpm:form inside the rendering element (yes Tom, OTHER namespace
| >>> required :-P), so it might just be that it is possible to hook this
| >>> up to the console already.
| >>>
| >>> What I'm currently looking into is how to differentiate between
| >>> users and groups. There is a potentialOwner element of which you can
| >>> have multiple, but it might be that
|
Ronald:
| >> I could initially do something like:
| >>
| >> <bpmn:potentialOwner id="myPerformer"
| >> resourceRef="sampleResource" jbpm:type="group">
| >>
| >> for groups
| >>
| >> and
| >>
| >> <bpmn:potentialOwner id="myPerformer"
| >> resourceRef="sampleResource" jbpm:type="user">
| >>
| >> for users.
|
Tom wrote :
| > isn't the simplest way if we couple resourceRef directly to our groups ?
| >
| > <bpmn:potentialOwner id="myPerformer"
resourceRef="accounting">
| >
| > in jBPM we could then associate the group as a candidate for that
| > task. i think that covers the most common form of task assignment.
| >
| > wdyt?
|
Bernd:
| > This is not the BPMN 2 way of thinking I guess. So I would go for what
| > Ronald proposed, that looks like valid BPMN 2.
| >
| > For the groups I didn't find anything in the spec. I check Bruce's
| > book. Maybe there...
| >
| > Intuitivley I would put it in the resource (example from spec, p. 183):
| >
| > <resource id="regionalManager" name="Regional
Manager">
| > <resourceParameter id="buyerName" isRequired="true"
name="Buyer Name"
| > type="xsd:string"/>
| > <resourceParameter id="region" isRequired="false"
name="Region"
| > type="xsd:string"/>
| > <jbpm:type>user</jbpm:type>
| > </resource>
|
Tom:
| can't we start with resourceAssignmentExpression instead of the resourceRef as the
most basic way of assigning a task?
|
| <potentialOwner id="myPerformer">
| <resourceAssignmentExpression>
| <formalExpression body="tom" language="jbpm-user" />
|
| or
|
| <potentialOwner id="myPerformer">
| <resourceAssignmentExpression>
| <formalExpression body="sales-dept" language="jbpm-group"
/>
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248300#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...