Instance Scoped Groups

[akriel]

I am evaluating Jbpm as a possible solution for a new project. Although in general users often belong to specific groups, it is possible on the instance level that a user may need to be added/removed from a group for that instance only.

Based on what I've seen looking at the jbpm source code something like this would have to be an extension, and is not currently supported. Have I missed something or is this an accurate statement?

Assuming I'm right about this not currently being supported, is this a feature the community would use? or does this seem like an uncommon requirement?

To clarify what I'm talking about, imagine a develop new software process. In general the same groups/people will handle each task. However assume that you have multiple contractors working at your company. These contractors need to be added on a per instance basis, because they are only contributing to the specific instance, not to every new instance of the process.

[kukeltje]

I am evaluating Jbpm as a possible solution for a new project. Although in general users often belong to specific groups, it is possible on the instance level that a user may need to be added/removed from a group for that instance only.

No

Based on what I've seen looking at the jbpm source code something like this would have to be an extension, and is not currently supported. Have I missed something or is this an accurate statement?

It is accurate

Assuming I'm right about this not currently being supported, is this a feature the community would use? or does this seem like an uncommon requirement?

I would not, since I can always add the individual actorid to the pooledactors list, besides the basic groupname for the* swimalaneinstance*

To clarify what I'm talking about, imagine a develop new software process. In general the same groups/people will handle each task. However assume that you have multiple contractors working at your company. These contractors need to be added on a per instance basis, because they are only contributing to the specific instance, not to every new instance of the process.

As mentioned before, you can use swimlanes for this

[akriel]

"kukeltje" wrote:

To clarify what I'm talking about, imagine a develop new software process. In general the same groups/people will handle each task. However assume that you have multiple contractors working at your company. These contractors need to be added on a per instance basis, because they are only contributing to the specific instance, not to every new instance of the process.

As mentioned before, you can use swimlanes for this

Thanks for your response.

I'm still trying to get a handle on what changes effect the process definition and which effect only the process instance. It sounds like your telling me I can add users to the specific tasks pooled actors without effecting the overall process definition. This would take the place of creating temporary groups!

[kukeltje]

yep

[akriel]

I was definitely over complicating it in my mind :)