Possible Agent Assignment

[yegorm]

Hello!
It is  SAP_TAGT evaluation path that is used in this case, and it
seems impossible to redefine -'SAP_TAGT' is hardcoded . (I got this
from a quick debug, so I might be wrong)
SAP_TAGT will not walk the orgunits tree recursively - I suppose it is
designed this way intentionally to prevent overflows on huge
structures.
So it looks like some other way of declaring possible agents should be
used here.

On Tue, Jul 13, 2010 at 9:26 PM,  <michael.mcley at daimler.com> wrote:
>
> Hey All,
>
> Small problem, hopefully this is an easy one.
>
> 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.
>
> 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...
>
> Michael McLey
> MBUSI - IT Parts & Administration
> Mercedes-Benz US International, Inc.
> 1 Mercedes Drive
> Vance, AL 35490
> PHONE:  (205) 462 - 5239
> EMAIL:   michael.mcley at daimler.com
> 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.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>