Can't use roles as agents in expressions?

[Ramki Maley]

Hi Mike,

How about a single rule that has the Role Name as a parameter? You can 
then resolve the role to get the responsible agents. You will still 
retain the Redo Rule functionality as well!

Cheers,
Ramki Maley.

asap at workflowconnections.com wrote:
> Hi Ed,
> Yes I really did mean dynamic as in determined at runtime. Client doesn't
> believe in rules or org structures, so they use Z-tables and tons of
> Z-roles with direct user assignments. Not fun.
>
> Net result, I need to lookup a ROLE name at runtime and send item to all
> users having that role. Yes one cen look up the corresponding user (which
> I now did), but the WF builder is misleading: It allows you to select
> "Role" from the dropdown and it works if you type one in. So it's natural
> to assume that selecting "Expression" and entering a container element
> with a value AG<rulename> should also work. It doesn't.
>
> Hoewever I'm grateful for your having cleared up the mystery connection to
> 'Activity groups',so by all means stick to your line of work :-)
>
> Thanks,
> Mike
>
>
> On Thu, March 1, 2007 3:51 pm, Edward Diehl wrote:
>   
>> Mike,
>> Im gonna go out on a limb here, but, as far as I know, there is no such
>> thing as a dynamic role, as current defined.  A role is a group of entries
>> in table AGR_USERS, grouped by the role id.  These used to be called
>> activity groups before SAP decided to "clarify" things by changing them to
>> roles.  In a way they have always been roles because this is the same
>> table used by SAP security.  Along with the change to "Roles" instead of
>> Activity Groups, workflow roles became "Rules".   I guess if a method
>> dynamically populated your role prior to the instantiation of the work
>> item, it might work, but it has to exist as a predefined list prior to
>> instantiation of the work item.
>> As before, just don't assign any agents to the runtime agent assignment,
>> or if the syntax checker objects, create a container element EMPTY_AGENT,
>> type wfsyst-agent and make that the runtime agent. (EXPRESSION =
>> EMPTY_AGENT).
>>
>> Please, somebody let me know if I am wrong.  If so, I will begin looking
>> for another line of work.
>> Ed
>>
>>
>>
>>
>>
>>     
>>> Date: Thu, 1 Mar 2007 14:43:28 +0000> Subject: RE: Can't use roles as
>>> agents in expressions?> From: asap at workflowconnections.com> To:
>>> sap-wug at mit.edu> > Thanks Ed & Ramki.> It has to be a dynamic role so
>>> task assignments are not applicable. Client> uses roles instead of
>>> rules.> > Workarounds are not an issue, I'm just wondering whether this
>>> shouldn't> work as standard. Ramki has indicated that this indeed
>>> doesn't work on> other 620 systems so at least I know it's not just our
>>> system.> > Cheers,> Mike> > On Thu, March 1, 2007 1:36 pm, Edward Diehl
>>> wrote:> > Mike,> > The way you do that is to use the role to define the
>>> possible agents and> > then don't assign any agent at all in the task at
>>> run time. It will then> > go to all of the possible agents; i.e. your
>>> role.> >> > Hope that helps,> > Ed> >> >> > To: sap-wug at mit.eduSubject:
>>> Re: Can't use roles as agents in> > expressions?Date: Thu, 1 Mar 2007
>>> 07:38:03 -0500From: workflow99 at aol.com> > Mike,> >> > I tried the same a
>>> couple of years ago on a 6.20 system as well and my> > experience was
>>> the same. The agent type in WFSYST-AGENT can only be the> > standard HR
>>> org objects like Job, Position, Org Unit etc. Definitely Role> > and
>>> Rule do not work that way.> >> > Best Regards,Ramki Maley.> >
>>> -----Original Message-----From: asap at workflowconnections.comTo:> >
>>> sap-wug at mit.eduSent: Thu, 1 Mar 2007 5:43 AMSubject: Can't use roles as>
>>>       
>>>> agents in expressions?> >> >> > G'Day,> > I just noticed that one
>>>>         
>>> cannot use a role in an agent expression. Can> > anyone confirm whether
>>> this is supposed to be so or if it's a bug? The> > docs are quiet on the
>>> matter.> >> > e.g. in the WF builder I can assign agent type role and
>>> assign ZMYROLE.> > Recipients are all users with role ZMYROLE, great.>
>>>       
>>>>>> If I create a container element Agent type WFSYST-AGENT and assign>
>>>>>>             
>>>> AGZMYROLE, the WI ends up with nobody on our 6.20 system.> >> > Of
>>>>         
>>> course one can work around this by an extra step/attribute, but just> >
>>> wondering whether why I should have to.> > Cheers,> > Mike> >> >> >
>>> _______________________________________________> > SAP-WUG mailing list>
>>>       
>>>> SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >>
>>>>         
>>>>>>>> AOL now offers free email to everyone. Find out more about
>>>>>>>>                 
>>> what's free> > from AOL at
>>> AOL.com._______________________________________________> > SAP-WUG
>>> mailing list> > SAP-WUG at mit.edu> >
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > > -- > Mike
>>> Pokraka> Senior Consultant> Workflow Connections> Mobile: +44(0)7786
>>> 910855> > _______________________________________________> 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
>>
>>     
>
>
>