AW: How can I disable the SAP office forwarding under SAP 4.6 c

Tue Jun 4 10:50:04 EDT 2002

Gotcha, man, you're on the right track, the thing is just that EVERYONE =
is
potentially in group A, so there's no point to make any assignments =
other
than a general task assignment there..

-----Urspr=FCngliche Nachricht-----
Von: Zmudzin,Tomasz,VEVEY,GL-DS/DM [mailto:Tomasz.Zmudzin at nestle.com]
Gesendet: Dienstag, 4. Juni 2002 12:45
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: FW: How can I disable the SAP office forwarding under SAP 4.6 =
c

... and being so stubborn I'd just add that indeed you need to =
specifically
assign all the possible Group B users as belonging to Group A which may =
seem
impossible at the first look in a large installation -- but again =
naming
them via jobs & positions will save the day.

Kind regards -- and I promise to stop bombing you for a while,
Tomasz

-----Original Message-----
From: Zmudzin,Tomasz,VEVEY,GL-DS/DM=20
Sent: Tuesday, June 04, 2002 12:36 PM
To: 'SAP Workflow Users' Group'
Subject: RE: How can I disable the SAP office forwarding under SAP 4.6 =
c

Yes -- but I think we're still talking about two different things... =
>From
the functional point of view the agents for a task are determined by
checking three groups of agents:

Group A:    All the allowed agents of the task. If a task is "general", =
this
are all system users. If it's not, these are all the agents assigned in =
to
the task in the assignment (PFTC--> Additional Data --> Agent =
assignment).
This is static, cannot be changed at run-time. And this is specified at =
task
level -- no matter in which workflow you use the task, it will have the =
same
allowed agents.

Group B: Those specified in the "Agents" section of the task within
workflow. This is dynamic (e.g. via role or container element) and can =
be
determined / altered at runtime.

Group C: Those specified in the "Excluded" section of the task within
workflow (dynamic)

Now finally the agents for a task are determined as those belonging to =
Group
A _AND_ Group B, but _NOT_ belonging to Group C. Thus if we talk about
authorizations, we can model them by using the agent assignments (Group =
A).
This is static, shared across workflows -- just as authorizations are. =
Users
that don't belong to group A will not be able to execute an item.

In your e-mail you're probably referring to Group B -- this can be
determined dynamically at run-time based on document content etc., on a
per-process instance basis. So this is where you try to determine your
agents based on config tables, responsibilities, document content etc.
Because in the end only those belonging both to A and B will be picked, =
A
still acts like authorizations. And finally Group C is subtracted, the =
same
way.

So in our particular problem we can still specify our agents =
dynamically for
Group B (using frequently-changing tables, responsibilities etc.). But =
--
instead of making the task general (Group A =3D all), we assign it to =
the
allowed users only. Then you set the task attributes to "General =
forwarding
not allowed", and we still have the very dynamic agent determination, =
but
the task can be only forwarded to those you trust.=20

Or did I get it wrong?

BR - Tomasz

-----Original Message-----
From: Becker Stephan (extern)
[mailto:Stephan.Becker.ext at mchw.siemens.de]
Sent: Tuesday, June 04, 2002 12:06 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: How can I disable the SAP office forwarding under SAP 4.6 =
c

Thomasz, my point was that in many approval situations, you CANNOT =
determine
possible agents at definition time (other than saying it's a general =
task)
as the possible agents are determined at runtime, from document data, =
using
tables and/or other settings that change frequently in the production
system.

-----Urspr=FCngliche Nachricht-----
Von: Zmudzin,Tomasz,VEVEY,GL-DS/DM [mailto:Tomasz.Zmudzin at nestle.com]
Gesendet: Dienstag, 4. Juni 2002 11:52
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: How can I disable the SAP office forwarding under SAP 4.6 =
c

But in this case you can define the allowed agents for this task, and
restrict forwarding to these agents only. Not only will this solve the
problem of forwarding restriction, but also will guard you against =
possible
mistakes in the dynamic determination of agents...

I somehow believe that the allowed agent assignment is often
underutilized... It's just a great mechanism to implement =
authorization-like
restrictions for workflow tasks.

Kind regards,
Tomasz

-----Original Message-----
From: Becker Stephan (extern)
[mailto:Stephan.Becker.ext at mchw.siemens.de]
Sent: Tuesday, June 04, 2002 11:11 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: How can I disable the SAP office forwarding under SAP 4.6 =
c

For example: say there is no way to restrict agent assignment at =
definition
time, because agents are determined dynamically at runtime (e.g. for =
signing
of invoices), for example from movement data that changes all the time, =
but
you still want to prohibit forwarding because signatory authorisation =
is
linked to the person only..

-----Urspr=FCngliche Nachricht-----
Von: Zmudzin,Tomasz,VEVEY,GL-DS/DM [mailto:Tomasz.Zmudzin at nestle.com]
Gesendet: Dienstag, 4. Juni 2002 11:05
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: How can I disable the SAP office forwarding under SAP 4.6 =
c

Out of sheer curiosity -- if a task is general (i.e. can be performed =
by
anyone, even if it normally lands in specific inboxes) -- why would we =
want
to prohibit forwarding?=20

To my simple mind it looks as if it would make sense to prohibit it =
only if
you have certain users allowed to perform it. Then you could still
distinguish between allowing forwarding to allowed agents only or to =
the
general user community. Or am I missing something not-so-obvious?

Kind regards,
Tomasz

-----Original Message-----
From: Becker Stephan (extern)
[mailto:Stephan.Becker.ext at mchw.siemens.de]
Sent: Tuesday, June 04, 2002 10:37 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: How can I disable the SAP office forwarding under SAP 4.6 =
c

Good question.. for some reason probably only known to SAP, you cannot =
have
a general task and disallow forwarding at the same time.. if that is no
problem for you, set "general forwarding not allowed" in the attributes =
of
the agent maintenance of the TS. If it is a problem, I have in the past
chosen the (admittedly somewhat cloodgy but effective) approach to =
check in
the method if the agent before and after method execution are the same, =
and
to trigger an exception that is then in the builder evaluated in a loop =
that
just creates the item again for the user (with a message beforehand
informing the user about the rule).

Hth,
Stephan

-----Urspr=FCngliche Nachricht-----
Von: Vincze =C1rp=E1d [mailto:Arpad.Vincze at itelligence.hu]
Gesendet: Dienstag, 4. Juni 2002 10:26
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: How can I disable the SAP office forwarding under SAP 4.6 c

Hello Workflowers,

  I would like to disable the SAP office forwarding for workitems!
    How can I do it?

   Is there any hint?

   Regards:
                =C1rp=E1d

Vincze =C1rp=E1d
itelligence Hungary Kft.
H-1138 Budapest, V=E1ci =FAt 141
Tel.:   (+36 1) 452 3822
Fax:    (+36 1) 452 3839
Mobil:   (+36 20) 9 533 578
arpad.vincze at itelligence.hu