rswuwfml or mail forwarding

Michael Pokraka workflow at quirky.me.uk
Tue Jan 27 09:54:28 EST 2004


Hi John,
The default consultant's answer applies: "It depends".
Serious answers aside, a few factors you may consider:
 
* Workitems (and hence RSWUWFML) have more flexible agent resolution.
* Mails can be sent to workgroup mailboxes.
* Also, consider that notifying 3 possible agents means that 3 mails go
out, one will pick up the item and the others end up with a notification
without a WI (this is where team mailboxes come in handy).
* RSWUWFML is a single, consistent process across multiple different
workflows. Thus if you have many flows, easier maintenance and less user
training.
* Both become a pain if workitems are too frequent.
* Mails don't pay any attention to Workflow substitutions.
 
So it's pretty much requirement-driven, though in my experience I'd go
with a mixed bag approach with RSWUWFML as a base and mail for the better
suited tasks. On the other hand, my current client works completely
without mail. Even simple notifications get a workitem. It's a successful
example of neither option.
 
Cheers
Mike
 
John A Haworth wrote:
> Hi
>
> Has anyone a view on which approach is best for emailing Approvers
> (outside
> of SAP), using the RSWUWFML program or auto-forwarding workflow emails.
>
> Thanks
>
> John
>
>
> -----------------------------------------------------------------------=
-----------------
>
> This is a PRIVATE message. If you are not the intended recipient, pleas=
e
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
> written
> agreement or government initiative expressly permitting the use of e-ma=
il
> for such purpose.
> -----------------------------------------------------------------------=
-----------------
>
>
 


More information about the SAP-WUG mailing list