-
1. Re: Why can't we assign a Process Instance to Users/Roles..
klsateesh Nov 15, 2005 4:23 PM (in response to 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 -
2. Re: Why can't we assign a Process Instance to Users/Roles..
koen.aers Nov 15, 2005 5:00 PM (in response to klsateesh)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 -
3. Re: Why can't we assign a Process Instance to Users/Roles..
koen.aers Nov 15, 2005 5:04 PM (in response to klsateesh)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... -
4. Re: Why can't we assign a Process Instance to Users/Roles..
gengshg Nov 17, 2005 4:10 AM (in response to klsateesh)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)