<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005>P.S. The below is not a flame to Phil - just a
reminder to all of the new options.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005>Phil, I've used the new event and it's great
stuff! And yes it definitely achieves the sort of change you made in
4.6. And yes I absolutely agree that its a better approach than just
forwarding to a new agent. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005>E.g. put your agents in a multiline container element,
on deadline reached, append your new agents to the container element then fire
the event. Magic stuff!</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005>Also helps to send a mail at the same time telling the
original agents that they have now been "dobbed in" to the next level
above.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005>Jocelyn.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=867173600-21012005></SPAN></FONT> </DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Dart, Jocelyn <BR><B>Sent:</B> Friday,21
January 2005 11:27 AM<BR><B>To:</B> 'SAP Workflow Users'
Group'<BR><B>Subject:</B> RE: Forwarding work items and possible
agents<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2>By the way everyone...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2>As of 6.20/6.40 you should no longer use
SWW_WI_AGENTS_CHANGE, but use the special workflow header level event(Outcome)
"Reevaluate rules on active work items or the "Redo rules" option in the
workflow administrator transactions or the equivalent SAP_WAPI function
modules instead. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2>Much better and much much easier to use - especially the
header level event. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=735452300-21012005><FONT face=Arial
color=#0000ff size=2>Jocelyn </FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Soady,
Phil<BR><B>Sent:</B> Wednesday,19 January 2005 9:48 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Forwarding work items and
possible agents<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Hi WUGers</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>I watch this one with interest.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Perhaps I made an assumption in the past how this
works.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>But I have used
SWW_WI_AGENTS_CHANGE</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>to add people to a workflow so they COULD execute. In
fact because an ALL actual agents can execute.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>I saw this as a desirable feature. Delegation in
real-time.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>The weren't NOT originally on a possible agent. But
someone passes to them.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Just like with
paperwork.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>My understanding was the fact that someone becomes a
CURRENT agent.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Either by adding them programmatically or via
forwarding, there are now 2 agent actuals.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Not yet reserved, but 2 agents with the task in the
inbox ready to go.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Perhaps under 6.x with the re-evaluate rule, this might
catch this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>I haven't tried that.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>A test of possible agent still correctly shows one not
as a possible agent.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>All New WFlows don't go to one of the users. AS
expected.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>But once a workflow was delivered to a user by someone
who did have originally have access</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>they have effectively delegated. Hence the
warning. The user is a possible agent. Are you
sure</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>you want to pass this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Hence also the general agents forwarding. Switch.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>I remember looking as some code way back
when....</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>But maybe I made a mistake. But that this the way I
thought it worked.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Heres the code we used (4.6) back in
2001.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>Please no flames because I didn't use the SAP_WAPIs ;-)
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2>If someone with a system with suitable test users etc
can test the Re-evaluate rule aspect I</FONT></SPAN></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT size=2><FONT
color=#0000ff><SPAN class=902382710-19012005>would be interested in the
result.</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT size=2><FONT
color=#0000ff><SPAN class=902382710-19012005></SPAN><SPAN
class=902382710-19012005></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2> 1 *<BR> 2 function
z_ess_change_absence_approver .<BR> 3
*"----------------------------------------------------------------------<BR>
4 *"*"Local interface:<BR> 5 *"
IMPORTING<BR> 6 *"
VALUE(DOCSY) LIKE ZESSLEAVEWI_ID-DOCSY<BR> 7
*" VALUE(DOCNR) LIKE
ZESSLEAVEWI_ID-DOCNR<BR> 8 *"
TABLES<BR> 9 *" AGENTS
STRUCTURE SWHACTOR OPTIONAL<BR> 10
*" DEPENDENT_WIS STRUCTURE SWWWIHEAD
OPTIONAL<BR> 11 *" EXCEPTIONS<BR>
12 *" BAD_CONTROL_CONFIG<BR>
13 *" BAD_TASK_CONFIG<BR>
14 *" BAD_DOCSY_DOCNR<BR>
15 *" UPDATE_FAILED<BR>
16
*"----------------------------------------------------------------------<BR>
17<BR> 18<BR> 19 data: wi_id
like zessleavewi_id-wi_id,<BR>
20
l_task_control like zesscontrol-ar_app_task_id.<BR>
21<BR> 22<BR> 23 * Read ZESS control
information:<BR> 24 select single
ar_app_task_id into l_task_control from zesscontrol<BR>
25 where
sysid = sy-sysid.<BR> 26<BR>
27 if sy-subrc <> 0.<BR>
28 raise bad_control_config.<BR>
29 endif.<BR> 30<BR>
31 if l_task_control is initial.<BR>
32 raise bad_task_config.<BR>
33 endif.<BR> 34<BR>
35<BR> 36 * Read Doc - WF link table:<BR>
37 select single wi_id into wi_id from
zessleavewi_id<BR>
38 where docsy =
docsy<BR>
39 and docnr =
docnr.<BR> 40<BR> 41 if sy-subrc
<> 0.<BR> 42 raise
bad_docsy_docnr.<BR> 43 endif.<BR>
44<BR> 45<BR> 46 refresh
dependent_wis.<BR> 47 clear
dependent_wis.<BR> 48<BR> 49 call
function 'SWI_GET_DEPENDENT_WORKITEMS'<BR>
50 exporting<BR>
51
wi_id =
wi_id<BR> 52
tables<BR>
53
dependent_wis = dependent_wis.<BR> 54<BR>
55 loop at dependent_wis where wi_rh_task =
l_task_control.<BR> 56<BR>
57 call function
'SWW_WI_AGENTS_CHANGE'<BR>
58
exporting<BR> 59
* NOTIFICATION_AGENTS_APPEND
= ' '<BR> 60
*
DEADLINE_AGENTS_APPEND = ' '<BR>
61 *
DESIRED_END_AGENTS_APPEND = ' '<BR></FONT></SPAN><SPAN
class=902382710-19012005><FONT face=Arial color=#0000ff size=2>
62 *
LATEST_START_AGENTS_APPEND = ' '<BR> 63
*
EXCLUDED_AGENTS_APPEND = ' '<BR>
64
agents_append
= ' '<BR>
65
wi_id
= dependent_wis-wi_id<BR> 66
*
DO_COMMIT
= 'X'<BR> 67
*
AUTHORIZATION_CHECKED = ' '<BR>
68
tables<BR>
69
agents
= agents<BR> 70
*
DEADLINE_AGENTS
=<BR> 71 *
DESIRED_END_AGENTS
=<BR> 72 *
LATEST_START_AGENTS
=<BR> 73 *
EXCLUDED_AGENTS
=<BR> 74 *
NOTIFICATION_AGENTS
=<BR> 75
exceptions<BR>
76
no_authorization
= 1<BR>
77
update_failed
= 2<BR>
78
invalid_type
= 3<BR>
79
others
= 4<BR>
80
.<BR> 81 if sy-subrc <>
0.<BR> 82 raise
update_failed.<BR> 83
endif.<BR> 84<BR> 85
exit.<BR> 86 endloop.<BR>
87<BR> 88<BR> 89
endfunction.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=902382710-19012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><B><FONT face=Arial color=#000080 size=1>Phil Soady</FONT></B> <BR><FONT
face=Arial color=#808080 size=1>Senior Consultant</FONT> <BR><FONT
face=Arial color=#808080 size=1>Business Technologies</FONT> <BR><B><FONT
face=Arial color=#808080 size=1>SAP Australia </FONT></B><BR><FONT
face=Arial color=#808080 size=1>M +61 (0) 412 213 079</FONT> <BR><FONT
face=Arial color=#808080 size=1>E </FONT><A
href="mailto:phil.soady@sap.com"><U><FONT face=Arial color=#0000ff
size=1>phil.soady@sap.com</FONT></U></A> </P>
<DIV> </DIV><BR>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Cristiana
D'Agosto<BR><B>Sent:</B> Wednesday,19 January 2005 3:17 PM<BR><B>To:</B>
SAP Workflow Users' Group<BR><B>Subject:</B> RE: Forwarding work items and
possible agents<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Hi Jocelyn,</FONT>
<BR><BR><FONT face=sans-serif size=2>but my issue is that the user is NOT
a possible agent and can execute the work item! I am puzzled because I
know that this should not have happened!</FONT> <BR><BR><FONT
face=sans-serif size=2>Any other ideas on why the user is being able to
execute the work item that has been forwarded to him even thought he
doesn't have the required authorization role assigned to his user
id??</FONT> <BR><BR><FONT face=sans-serif size=2>Its driving me crazy!
This user id has not been changed recently, so it is not
buffer-related.</FONT> <BR><BR><FONT face=sans-serif size=2>Thanks</FONT>
<BR><BR><FONT face=sans-serif size=2>Cheers</FONT> <BR><BR><FONT
face=sans-serif size=2>Cristiana</FONT> <BR><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Dart, Jocelyn"
<jocelyn.dart@sap.com></B> </FONT><BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>19/01/2005 03:01 PM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users'
Group"</FONT></DIV></TD></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>"SAP Workflow
Users' Group" <sap-wug@mit.edu></FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>RE: Forwarding
work items and possible agents</FONT></TD></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><BR><BR><FONT
face=Arial color=blue size=2>Yes that's right Cristiana - sending it to
someone who is not a possible agent means they can't execute it, but they
can view it and forward it to a 3rd party. </FONT><BR><FONT face=Arial
color=blue size=2>Not something you would usually want - hence the warning
- but occasionally handy if:</FONT> <BR><FONT face=Arial color=blue
size=2>* You want to forward to a help desk or shared services desk who is
responsible for finding an alternative agent</FONT> <BR><FONT face=Arial
color=blue size=2>* The person you are forwarding to is the correct agent
but doesn't have the security to execute it yet, it can then sit in their
inbox until their security is sorted out. </FONT><BR><FONT
size=3> </FONT> <BR><FONT face=Arial color=blue size=2>Mark the task
as "Forwarding not allowed" (4.6D or above) to prevent forwarding to
anyone. Mark the task as "General Forwarding not allowed" to prevent
forwarding to agents who are not possible agents. </FONT><BR><FONT
face=Arial color=blue size=2>Regards,</FONT> <BR><FONT face=Arial
color=blue size=2>Jocelyn</FONT> <BR><BR>
<HR>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Cristiana
D'Agosto<B><BR>Sent:</B> Wednesday,19 January 2005 12:31 PM<B><BR>To:</B>
SAP Workflow Users' Group<B><BR>Subject:</B> Re: Forwarding work items and
possible agents</FONT><FONT size=3><BR></FONT><BR><FONT face=sans-serif
size=2><BR>Hi Paul,</FONT><FONT size=3> <BR></FONT><FONT face=sans-serif
size=2><BR>I understand that ideally the 'General Forwarding Not Allowed'
should be set.</FONT><FONT size=3> <BR></FONT><FONT face=sans-serif
size=2><BR>But I don't understand why the user was able to execute the
work item if he was not a possible agent??</FONT><FONT size=3>
<BR></FONT><FONT face=sans-serif size=2><BR>Any other ideas?</FONT><FONT
size=3> <BR></FONT><FONT face=sans-serif size=2><BR>Regards</FONT><FONT
size=3> </FONT><FONT face=sans-serif size=2><BR><BR>Cristiana</FONT><FONT
size=3> <BR><BR><BR></FONT>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="42%"><FONT face=sans-serif
size=1><B>Paul.Bakker@osr.treasury.qld.gov.au</B> <BR>Sent by:
sap-wug-bounces@mit.edu</FONT><FONT size=3> </FONT>
<P><FONT face=sans-serif size=1>19/01/2005 10:38 AM</FONT><FONT
size=3> </FONT><BR>
<TABLE width="100%" border=4>
<TBODY>
<TR vAlign=top>
<TD width="100%" bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users'
Group"</FONT></DIV></TD></TR></TBODY></TABLE>
<P></P>
<TD width="57%"><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="13%">
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top width="86%"><FONT face=sans-serif size=1>"SAP
Workflow Users' Group" <sap-wug@mit.edu></FONT><FONT
size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>Re: Forwarding
work items and possible
agents</FONT></TD></TR></TBODY></TABLE><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="49%">
<TD
width="50%"></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><FONT
size=3><BR><BR></FONT><FONT face=Arial
size=2><BR><BR><BR>Cristiana,<BR><BR>Is the 'General Forwarding Not
Allowed' attribute set on your task?<BR><BR>If it is set, you should only
be able to forward to a possible agent (who<BR>hasn't been excluded by the
workflow).<BR><BR>hope this
helps,<BR>Paul<BR>(Brisbane)<BR><BR><BR><BR>
<BR>
"Cristiana D'Agosto"
<BR>
<cristiana.dagosto@a
To: sap-wug@mit.edu
<BR>
u1.ibm.com>
cc:
<BR>
Sent by:
Subject: Forwarding work items and
possible agents
<BR>
sap-wug-bounces@mit.
<BR>
edu
<BR>
<BR>
<BR>
19/01/2005 08:41
<BR>
Please
respond to
<BR>
"SAP Workflow Users'
<BR>
Group"
<BR>
<BR>
<BR><BR><BR><BR><BR><BR>G'day,<BR><BR>we are in version
4.7<BR><BR>If a work item is forwarded to an user that is NOT a possible
agent, a<BR>message is displayed but you can still forward it.<BR><BR>In
my scenario I'm using one security role assigned to the task
to<BR>determine the possible agents.<BR><BR>In my testing, the user that I
forwarded the work item to is NOT a possible<BR>agent. I accepted to
forward the work item anyway; log on as the user and<BR>could execute the
work item?<BR><BR>I thought that if the user is not a possible agent of
the work item, he/she<BR>cannot execute it?<BR><BR>It seems rather a silly
question but I am puzzled. I must have missed<BR>something, but
what?<BR><BR>Much thanks and
regards,<BR><BR>Cristiana<BR><BR>_________________________________<BR>Cristiana
d'Agosto<BR>IBM Business Consulting Services<BR>Direct: +61 2 9478
8926<BR>Mobile: +61 417 927
224<BR>cristiana.dagosto@au1.ibm.com<BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR><BR><BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug</FONT><FONT
size=3><BR></FONT><FONT face=Arial
size=2>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>