<br><font size=2 face="sans-serif">Hey All,</font><br><br><font size=2 face="sans-serif">Small problem, hopefully this is an
easy one. </font><br><br><font size=2 face="sans-serif">Most of our tasks in our workflows are
assigned as general tasks. I would like to restrict a number of them
to a list of possible agents (as I guess is a best practice). The
problem is, I had assumed that if I assigned a higher level org unit as
a possible agent that the lower level org units would come along. However,
I find this is not the case. Only the position assignments associated
with that org unit get listed as possible agents for the task. I
would like to change this behavior.</font><br><br><font size=2 face="sans-serif">Is there some way in workflow, or maybe
HR org management to change what gets pulled into the list of possible
agents when the task is assigned to an org unit? Hopefully this question
makes sense...<br></font><font size=4 color=#808000><b> </b></font><p><font size=4 color=#808000><b>Michael McLey</b></font><font size=3 color=#808000><b></b><br>MBUSI - IT Parts & Administration </font><font size=2 color=#808000><br>Mercedes-Benz US International, Inc.</font><font size=3 color=#808000></font><font size=2 color=#808000><br>1 Mercedes Drive</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>Vance, AL 35490</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>PHONE: (205) 462 - 5239</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>EMAIL: michael.mcley@daimler.com</font><font size=3 color=#808000>
</font><font face="sans-serif"><font face="sans-serif, Arial, Helvetica" size="-1" color="#808080"><br>If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
<br></br>
</font></font>