Agent Assignment in Task Definition - getting rid of general tasks!

[Dale Davis]

Hi Susan:
 
If you can't find a job that fits your requirement, you might  want to
assign the task to the organization. To protect against broadcasting th=
e
task to the org if the
role resolution fails, you can specify a default role in the task
definition. This is helpful if you don't want the administrative overhe=
ad
associated with setting the role to terminate which causes the workitem=
 to
go into error status. In one of the cases where we specified the defaul=
t
role, we made that role the adminstrator responsible  for agent assignm=
ents
for that process. For SAP delivered standard tasks you cannot assign a
default role without making a repair. In those cases you can copy the S=
AP
standard task to one of your own then modify
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow & PP Consultant - SAP Practice
 
IBM Global Services
Phone: 919-543-7678
               T/L 8-441-7678
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to=
 
lose sight of the shore..........
 
 
"Susan R. Keohan" <skeohan at MIT.EDU>@MITVMA.MIT.EDU> on 12/11/2001 01:36=
:38
PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:  Re: Agent Assignment in Task Definition - getting rid of gene=
ral
      tasks!
 
 
 
Hi Martin,
 
I am on 4.6c.
 
Thank you for clarifying the use of standard roles .vs. the use of the =
role
from the user profile.=A0 I am not sure I can find a job which fits the=
 need
but I will continue to try.
 
FYI, your presentation at the Fall Conference is what is inspiring me t=
o
make these changes!
 
Regards,
Sue
At 12:23 PM 12/11/01 -0500, you wrote:
hi sue:
 
what release are you on ?
 
if i understand correctly, you want to use a role, i.e. AC00000138, as =
the
assignment of possible agents in the task maintenance. this is not poss=
ible
because AC roles are part of the dynamic agent determination. they only=
 
apply to selected agents, not to possible agents, because theoretically=
,
diffent agent can be selected every time the workflow uses the role, se=
e my
presentation at the fall conference. the AG role the system lets you us=
e is
the role from the user profile (transaction SU01) which includes
authorizations etc.
 
as discussed during the expert panel, a job assignment (pd object type =
C)
might be the best way to avoid potential performance issues ...
 
i hope this helps. please let me know, if you need more info.
 
martin
 
 
-------------------------------------------------------------
Martin Maguth
Consultant
IBM Global Services
Phone: (937) 225-6521, t/l 663
Email: mmaguth at us.ibm.com
 
 
"Susan R. Keohan" <skeohan at MIT.EDU>@MITVMA.MIT.EDU> on 12/11/2001 10:39=
:01
AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:=A0 SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:=A0=A0 SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:=A0 Agent Assignment in Task Definition - getting rid of genera=
l
=A0=A0=A0=A0=A0 tasks!
 
 
 
Hello all,
 
I am trying to get rid of the 'general' assignment for some workflow ta=
sks,
as the experts have informed me that this will improve performance.=A0 =
I want
to change the agent assignment in the task definition to the standard r=
ole
(which is also specified in the multi-step task in the 'agents' field.)=
 SAP
doesn't seem to want to let me specify a role of type AC; in the 'choos=
e
role' pop-up box, I can choose roles of object type AG but that's all.
 
Can anybody shed some light on what I am missing here ?
 
Thanks
Sue
 
=