jemmerling [https://community.jboss.org/people/jemmerling] created the discussion "Re: Human Task Assignment -- restrict based on process variables" To view the discussion, visit: https://community.jboss.org/message/645998#645998 -------------------------------------------------------------- OK, I believe I have at least partially answered this question for myself. So it appears that the method executeTaskAddRules has the purpose of allowing the developer (or analyst?) to define any rule he or she wants using any content they have defined. So, for example, if you have a process consisting of two approval steps, and you want to define a rule that states that an the actor that completed the first approval step may not be assigned the second approval step (even if both actors, in general, are eligible to perform that step) you would simply keep track of whatever actor approved the first step then define a rule that prevents that actor from being assigned to the second step. Note that this method is one of the few in jBPM5 that I have encountered so far which has any JavaDoc, so I am guessing it's an important method to understand. Taking note of the fact that this method throws an exception when a rule is violated, I need to investigate further to determine how to leverage this functionality in such a way that the routine application of a rule does not case a user to experience an error message. If somebody can confirm that this is the correct general approach, please reply and I will update this thread to "Answered". Also if you know of any example for implementing such a rule, please point me to it, if you don't mind, thanks! --JE -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/645998#645998] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]