Possible agents

Tue Apr 15 10:29:30 EDT 2008

Hello Florin,
This makes sense to me if the logic is that if no possible agents are
defined then even though there is a role assignment there should be 'no
recipients''

David.S.Dittmer
Accenture

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Florin Wach
Sent: Tuesday, April 15, 2008 9:30 AM
To: SAP Workflow Users' Group
Subject: Re: RE: Possible agents

Hi David,

the assigned role can only pick agents from the group of the "possible
agents".
If that group is empty, none can be picked.

You'll need to have a group of agents assigned to a task (or the
associated task group).
If the task group has no explicit agent assignment (e.g. it is a
"general task"), this attribute is not propagated to it's member (so the
task will not become "general", as well).

Best wishes,
   Florin

-------- Original-Nachricht --------
> Datum: Tue, 15 Apr 2008 08:17:33 -0500
> Von: david.s.dittmer at accenture.com
> An: sap-wug at mit.edu
> Betreff: RE: Possible agents

> Hello mike,
> The workflow task does not belong to any task group. The workflow does
> have a role agent assignment with a function module attached which
> directs the workflow to search the partner profiles for an agent but I
> thought that if there is no possible agent then the role would be
> ignored but maybe I am wrong.
> 
> regards
> 
> David.S.Dittmer
> Accenture
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
> Of Mike Pokraka
> Sent: Tuesday, April 15, 2008 8:37 AM
> To: SAP Workflow Users' Group
> Subject: RE: Possible agents
> 
> Just to ask the obvious: Does this taks belong to any task group?
> 
> On Tue, April 15, 2008 12:56 pm, david.s.dittmer at accenture.com wrote:
> > Hello Mike,
> > The users attached to the partner profiles have been in place for
> months
> > and the GENERAL TASK was removed from the agent assignment a number
of
> > weeks ago. My question is if there are no possible agents is it
> possible
> > for the workflow still to be generated.
> >
> > regards
> >
> > David.S.Dittmer
> > Accenture
> >
> >
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
> > Of Mike Pokraka
> > Sent: Tuesday, April 15, 2008 5:46 AM
> > To: SAP Workflow Users' Group
> > Subject: Re: Possible agents
> >
> > Hi David,
> > Did you change the assignment? Organization data is buffered and
> > refreshed
> > at midnight, so you need to use OOCU_RESP before testing any changes
> the
> > same day. Also rememebr to come out of any transactions - if you
> remain
> > in
> > the inbox, the old org is cached in the session regardless of buffer
> > refresh.
> > Cheers,
> > Mike
> >
> > On Tue, April 15, 2008 12:12 am, david.s.dittmer at accenture.com
wrote:
> >> Hello workflow experts,
> >>
> >> I have a workflow with the additional agents assigned to the
> attribute
> >> NO GENERAL TASK and no agent assignment. I have a role function
> module
> >> with code which searches for agents on the partner profiles of the
> >> customer and work items are being sent to these agents. How is it
> >> possible that when there are no possible agents, that the role
> > overrides
> >> the workflow agent settings.
> >>
> >>
> >>
> >> David.S.Dittmer
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> This message is for the designated recipient only and may contain
> >> privileged, proprietary, or otherwise private information.  If you
> > have
> >> received it in error, please notify the sender immediately and
delete
> > the
> >> original.  Any other use of the email by you is prohibited.
> >> _______________________________________________
> >> 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
> >
> >
> >
> > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise private information.  If you
> have
> > received it in error, please notify the sender immediately and
delete
> the
> > original.  Any other use of the email by you is prohibited.
> >
> > _______________________________________________
> > 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
> 
> 
> 
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information.  If you
have received it
> in error, please notify the sender immediately and delete the
original. 
> Any other use of the email by you is prohibited.
> 
> _______________________________________________
> 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

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.