SAP_WAPI_ADM_WORKITEM_REDORULE

Mark Pyc mark.pyc at gmail.com
Tue May 2 07:52:45 EDT 2006


G'day Mike,

Maybe what you're doing should work, maybe not. Redo-rule may struggle when
there is no rule.

You may be better off (from a sanity point of view) to wrap the read of the
attribute in a function module rule.

Have fun,
Mark


On 5/2/06, Mike.Nickson at boots.com <Mike.Nickson at boots.com> wrote:
>
>
> Mike
>
> Agent determination of the particular workitem that is causing me grief is
> done against an attribute of the object.
>
> 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 ?
>
> 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 ?
>
> Mike
>
>
>
>   *Mike Pokraka <asap at workflowconnections.com>*
> Sent by: sap-wug-bounces at mit.edu
>
> 28/04/2006 19:06
> Please respond to "SAP Workflow Users' Group"
>
>         To:        "SAP Workflow Users' Group" <sap-wug at mit.edu>
>         cc:
>         Subject:        Re: SAP_WAPI_ADM_WORKITEM_REDORULE
>
>
>
>
> G'Day Mr Nickson,
>
> Sounds like a wood/trees problem - but that's to be expected rather late
> on a Friday:
> 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.
>
> Cheers,
> Mike
>
>
> Mike.Nickson at boots.com wrote:
> >
> > Basis 620 Level 55 - HR 470 Level 51
> >
> > When I am executing SAP_WAPI_ADM_WORKITEM_REDORULE (as part of a
> > method), for most workitems it work OK and the workitem is rerouting
> > according to the current agent assignment rules against it.
> > However when that workitem is a PCR (Personell Change Request), after
> > the call to the function module the workitem is being distributed to ALL
>
> > users (i.e. As a general task visible to all users).
> > This is causing problems as random curious users are grabbing the
> > workitem (and thereby reserving it) and then on occasions also rejecting
>
> > it.
> >
> > This is a sensitive area of the business and I am then manually having
> > to snatch it back and reassign it to the correct user agent.
> >
> > Does anyone have any idea why SAP_WAPI_ADM_WORKITEM_REDORULE leaves PCR
> > (and I suspect possibly other) workitems as a general task available to
> > all users ?
> >
> > The full scenario is that if a user changes position in the HR org
> > structure, then we reevaluate the agent rules against their workitems to
>
> > ensure that they are still relevant to them in their new position.
> >
> > Mike
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060502/3afb0392/attachment.htm


More information about the SAP-WUG mailing list