Why can't we assign a Process Instance to Users/Roles..

[klsateesh]

HI,

It seems we cannot assign Process Instances to Users or Roles .. Why ?
This forces to create tasks for driving the Process Instance..


I am testing a sample Workflow in a Web Application and if we cannot assign Process Instances to Users the only way we can control the Process Instances is to have a Task at each and every State..

Could you guys let me know is there another way of Controlling the Process Instances ??

Thanks
Sateesh

[klsateesh]

Hi,

It seems i need to have at least one Task which should be alive to Drive the entire Process Instance. Ideally this might be owened by the User who initiated the Process Instance . And this servers as a Handle to the Process Instance..



If there is a better way pls let me know..

Thanks
Sateesh

[koen.aers]

You don't need tasks to add actor information. Have a look at the documentation : http://docs.jboss.com/jbpm/v3/userguide/security.html and at the javadocs of the Authentication class hierarchy (http://docs.jboss.com/jbpm/v3/javadoc/org/jbpm/security/Authentication.html). Each time an authenticated user is to perform something, whether it be starting a processinstance or signalling a token, use this class to push and pop the actorid.

Regards,
Koen

[koen.aers]

oops...
the urls are :
- http://docs.jboss.com/jbpm/v3/userguide/security.html for the security documentation
- http://docs.jboss.com/jbpm/v3/javadoc/org/jbpm/security/Authentication.html for the Authentication class hierarchy...

[gengshg]

This (task) is the feature of jbpm's archetect, I think the right way is to follow this feature (don't consider assign the process to actor)