Sebastian Schneider [http://community.jboss.org/people/sebastian.s] replied to the discussion "How send mail to "starter" user" To view the discussion, visit: http://community.jboss.org/message/537825#537825 -------------------------------------------------------------- It's more an issue of jBPM than of the console. But you're right the console would need a change, too. However jBPM's API is even already prepared if you take a look at the javadocs. http://docs.jboss.org/jbpm/v4/javadocs/org/jbpm/api/ProcessEngine.html http://docs.jboss.org/jbpm/v4/javadocs/org/jbpm/api/ProcessEngine.html Take a look at the method called setAuthenticatedUserId(java.lang.String authenticatedUserId 1. the console has knowledge of the authenciated user (he had to authenciate to access the console) 2. the console needs to call this method each time the user invokes a method on the API (like starting a process)  to pass on the information 3. jBPM needs to store the information somewhere (maybe in a process variable but rather not) to expose it to the process and user IMHO it should be stored in the history data together with the information about the start event and it should be queryable via the API. It could be exposed via the execution context to the process. The issue is more or less an issue bothering people who use the included console. People using their own GUIs just store the name of the process starter in a process variable and use this variable later on - for example to do calucations, assign a task to him or just refer to him. Setting the starter via the API would be cleaner. The issue ( https://jira.jboss.org/jira/browse/JBPM-2482 https://jira.jboss.org/jira/browse/JBPM-2482) mentions the place in the source code which is affected. Whenever a new process instance is created the supplied user needs to be stored somewhere. Right now the code is not dealing with the supplied user name. This issue is related or almost the same. I think it refers to the part of the API which I mentioned: https://jira.jboss.org/jira/browse/JBPM-2417 https://jira.jboss.org/jira/browse/JBPM-2417 Because of this issue https://jira.jboss.org/jira/browse/JBPM-2416 https://jira.jboss.org/jira/browse/JBPM-2416 using a process variable is not a good either. This issue deals with audit capabilities regarding method invokations on the API. Sometimes not only the data coming from tasks in the process is interesting but also who has started, stopped or affected a process in some way. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/537825#537825] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]