Roles with AG too long to store in WFSYST-AGENT

Mark Pyc mark.pyc at gmail.com
Tue May 17 12:46:00 EDT 2005


G'day all,

Playing with this further I was disappointed to see that Sushil was
indeed correct that security roles (AG) can not be used dynamically.

The response from OSS:
>>>
unfortunately it is not possible to use Roles (AG) like the other
OrgObjects (User, OrgUnit, ...) due to the well-noticed length
restriction.
It is only possible to use them 'hard-wired' on step-level and not in
a dynamic manner.
I'll treat this as development request (but without making promises..).
<<<

I think Security Roles have great potential in terms of design however
that potential is greatly hampered by the inability to use them
dynamically. There are of course ways around everything, but it'd be
nice to get this one out of the box.

Everyone who thinks this is a dodgy shortcoming of a potential
powerful technique please raise an OSS message.

Have fun,
Mark  

On 5/10/05, Sushil Guragain <sguragain at interpublic.com> wrote:
> Thanks Mark!
> 
> We are trying to use this to store the role when we need to send the email to this role. We are planning to store the responsible agents on this field (by supplying the role name). We decided to limit the WF roles to be a maximum of 12 characters so that WFSYST-AGENT can hold the AG+role name in it.
> 
> Thanks,
> 
> Sushil
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mark Pyc
> Sent: Tuesday, May 10, 2005 10:35 AM
> To: SAP Workflow Users' Group
> Subject: Re: Roles with AG too long to store in WFSYST-AGENT
> 
> G'day Sushil,
> 
> The Role name can actually be up to 30 characters which makes your situation worse except that from your description it sounds like you're wanting to pass the actual agent from one step to another.
> 
> If this is true WFSYST-AGENT will work for you since the actual agent of the first step will be returned as a US userid combo regardless of how you determined the original responsible agents for the first step.
> 
> Have fun,
> Mark
> 
> On 5/10/05, Sushil Guragain <sguragain at interpublic.com> wrote:
> > Hi WF Gurus,
> >
> > We are using a field of type WFSYST-AGENT to store the approving
> > manager information that will be passed on to another step in
> > workflow. However when you use a role AG - you could use longer role
> > names (up to 14 characters long role). Now the problem is WFSYST-AGENT
> > is 14 characters long and I can not fit AG + the role in the field. Is
> > there some trick to save that information? Thanks in advance for your help.
> >
> > Regards,
> >
> > SushilThis message contains information which may be confidential and
> > privileged.
> Unless you are the intended recipient (or authorized to receive
> > this message
> for the intended recipient), you may not use, copy, disseminate
> > or disclose to
> anyone the message or any information contained in the
> > message. If you have
> received the message in error, please advise the sender
> > by reply e-mail, and
> delete the message. Thank you very much.
> (A)
> >
> > _______________________________________________
> > 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 contains information which may be confidential and privileged.
> Unless you are the intended recipient (or authorized to receive this message
> for the intended recipient), you may not use, copy, disseminate or disclose to
> anyone the message or any information contained in the message.  If you have
> received the message in error, please advise the sender by reply e-mail, and
> delete the message.  Thank you very much.
> (A)
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>



More information about the SAP-WUG mailing list