I've been using the business rule feature for human tasks to assign people to tasks based on one or more parameters passed into the human task from the process payload. In your case, if you wanted to have a group assigned based on a state, you'd pass into the human task the parameter that represented the state (e.g. "TX" or "AZ"). The business rule in the human task would then assign the work item instance to the correct LDAP group (e.g. "TexasAccountMgrs" or "ArizonaAccountMgrs").
I wrote this blog (http://www.avioconsulting.com/blog/datwood/2012/08/27/creating-parametric-roles-using-business-rules) a few months ago that gives you a step-by-step on how to do this.
thanks a lot for your quick response.
I went through your blog and tried implementing the same.
But in my case i have to send parallel notifications to both the states.
Please correct me if i am wrong, using if conditions in rules is allowing me to send to only one state.
I also tried the following approach
1) setting the organization units in bpm workspace
2) passing values using human task parametric roles
3) and looping the subprocess that has the humantask for the count of states.
I am able to loop the subprocess but i am not able to change the parametric role value for the next iteration of the subprocess.
I assume that these two groups are actually the owners of the task (i.e. it is in their application role) then you can send the notification to the owners (option in notification tab) and this will send them to both groups.
Put the list of users in the TX and the AZ groups in a comma separated format and concatenate the two lists together. This concatenated string that represents the list of approvers is then passed as input to the interactive activity's human task to define the list of approvers for the task.