Info requested: Has anyone turned forwarding off or created custom tools?

[Mark Pyc]

G'day Jocelyn,

I've been at a site where they chose to use a task per company code to
prevent forwarding across company codes. This is worse when the task is a
user decision (with no real auth control hence the concern) which can't be
dynamically bound, so you need a subflow per company code. In my opinion
unmanageable when they had almost 2000 company codes. However they still
preferred this to the uncontrolled nature of forwarding.

It's been an issue for a number of other sites, but they were unwilling to
have the support issues associated with this kind of plan.

Please please please give us some control. Ideally give us a retro-fitable
BAdI or similar.

Have fun,
Mark


On 1/12/06, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:
>
> Hi Folks,
>
> I'm trying to advocate some changes to the standard forwarding mechanism
> so that chosen forward-to user can be
> validated.
>
> To help raise the priority of this issue, would anyone please let me know
> if you have worked on any site where:
>
> * Forwarding was turned off due to lack of the ability to validate the
> user according to business rules
>
> * Custom tools were developed to ensure work items could only be forwarded
> to appropriate users according to business rules
>
> Your assistance is much appreciated.
>
> Regards,
> *Jocelyn Dart*
> Senior Consultant
> *SAP Australia Pty Ltd.*
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> ***http://www.sap.com* <http://www.sap.com/>
>
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for the
> person or entity to which it is addressed. If you are not the intended
> recipient, you are hereby notified that any distribution, copying, review,
> retransmission, dissemination or other use of this electronic transmission
> or the information contained in it is strictly prohibited. If you have
> received this electronic transmission in error, please immediately contact
> the sender to arrange for the return of the original documents.
>
> Electronic transmission cannot be guaranteed to be secure and accordingly,
> the sender does not accept liability for any such data corruption,
> interception, unauthorized amendment, viruses, delays or the consequences
> thereof.
>
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the sender
> is authorized to state them to be the views of SAP AG or any of its
> subsidiaries. SAP AG, its subsidiaries, and their directors, officers and
> employees make no representation nor accept any liability for the accuracy
> or completeness of the views or information contained herein. Please be
> aware that the furnishing of any pricing information/ business proposal
> herein is indicative only, is subject to change and shall not be construed
> as an offer or as constituting a binding agreement on the part of SAP AG or
> any of its subsidiaries to enter into any relationship, unless otherwise
> expressly stated.
>
>
> _______________________________________________
> 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/20060112/1c62f958/attachment.htm