<br><font size=2 face="sans-serif">Mike</font>
<br>
<br><font size=2 face="sans-serif">Agent determination of the particular workitem that is causing me grief is done against an attribute of the object.</font>
<br>
<br><font size=2 face="sans-serif">I see that for this workitem the object itself is not being passed in the binding . . . . Do you think that this may be the problem ?</font>
<br>
<br><font size=2 face="sans-serif">I can see that agent determination at the time the workitem is created would have access to the object in the workflow container, but would it still have access to the workflow container when the rule is reevaluated if the object is not part of the task binding ?</font>
<br>
<br><font size=2 face="sans-serif">Mike</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Mike Pokraka <asap@workflowconnections.com></b></font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">28/04/2006 19:06</font>
<br><font size=1 face="sans-serif">Please respond to "SAP Workflow Users' Group"</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: "SAP Workflow Users' Group" <sap-wug@mit.edu></font>
<br><font size=1 face="sans-serif"> cc: </font>
<br><font size=1 face="sans-serif"> Subject: Re: SAP_WAPI_ADM_WORKITEM_REDORULE</font></table>
<br>
<br>
<br><font size=2><tt>G'Day Mr Nickson, <br>
<br>
Sounds like a wood/trees problem - but that's to be expected rather late on a Friday: <br>
If the rule no longer finds any agents (i.e. the item is no longer relevant to the original agent), then it will happily send it out to all possible agents. Check how your agent determination is done, if it doesn't use a rule you should change it so that is uses a rule which is set to fail when none are found. <br>
<br>
Cheers, <br>
Mike<br>
<br>
<br>
Mike.Nickson@boots.com wrote:<br>
> <br>
> Basis 620 Level 55 - HR 470 Level 51<br>
> <br>
> When I am executing SAP_WAPI_ADM_WORKITEM_REDORULE (as part of a <br>
> method), for most workitems it work OK and the workitem is rerouting <br>
> according to the current agent assignment rules against it.<br>
> However when that workitem is a PCR (Personell Change Request), after <br>
> the call to the function module the workitem is being distributed to ALL <br>
> users (i.e. As a general task visible to all users).<br>
> This is causing problems as random curious users are grabbing the <br>
> workitem (and thereby reserving it) and then on occasions also rejecting <br>
> it.<br>
> <br>
> This is a sensitive area of the business and I am then manually having <br>
> to snatch it back and reassign it to the correct user agent.<br>
> <br>
> Does anyone have any idea why SAP_WAPI_ADM_WORKITEM_REDORULE leaves PCR <br>
> (and I suspect possibly other) workitems as a general task available to <br>
> all users ?<br>
> <br>
> The full scenario is that if a user changes position in the HR org <br>
> structure, then we reevaluate the agent rules against their workitems to <br>
> ensure that they are still relevant to them in their new position.<br>
> <br>
> Mike<br>
> <br>
> <br>
> ------------------------------------------------------------------------<br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>
<br>