Discussion: Standard Workflow Templates Purpose

['Mark Pyc']

G'day Paul,
 
That's a fair summation of the Templates I'd say. They exist to give
pointers to what processes make sense, which object to use, which events
to use as triggers and often links to the useful methods (release etc). A
big advantage of them is that they often give a focal point for Library
help to describe what config is required to get the standard events
triggering.
 
Whether or not SWDD_CONFIG gets a big wrap depends entirely on your trainer. I've never seen a
realistic use of it (shopping cart approval maybe?) and wouldn't suggest
otherwise to students.
 
Have fun,
Mark
 
 
 
 
 
 
Paul Batey <paul.batey at intelligroup.com.au>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
15/04/2004 14:53
Please respond to SAP Workflow Users' Group
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Discussion: Standard Workflow Templates Purpose
 
 
Evening all,
 
I am hoping to glean the purpose of the SAP standard templates.  To me
they are basic examples to point you in the right direction for your own
further development.  I have come across several specs recently that
start off...
 
"This is a simple workflow, just copy WS######## and allow for
escalation, changes, what the weather is, and then bung in some
completely different text for the task description"
 
By the time you have copied a standard template and wedged in the client
requirements it, to me, is always quicker to get the gist from the
standard, but then build it from scratch. This may not be true for the
backgroundy idoc type of things, but I have never been able to take a
standard and just switch it on.  This makes the whole idea of
SWDD_CONFIG meaningless, and a pain when you train people to say
SWDD_CONFIG is wonderful in BIT600, because it is never used.
 
Any thoughts folks?
 
Cheers,
 
Paul
 
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.638 / Virus Database: 409 - Release Date: 21/03/2004