Update or create a new Workflow?

[Soady, Phil]

Slam it in the main one.
But the now is your chance to do something good.
If you havent already, take the business requirement docu/
functional spec docu and or tech specs and include them in the long of =
the workflow.
Not only one stop shopping for the maintaine,  its documented as well =
:-)
Imagine knowing which workflows does what :-/
 
Subworkflows can still be used for concepts that reoccur.
 
Old fashioned software design principals still apply to your workflows.
 OO software design prinicpals are limited since the workflow itself =
cant behave
like an object in classic OO speak.
 
Workflows cant be built as subtypes with redefined paths or redefined =
activities.
A shell workflows can however have task determination based on =
variable...
So already I like the single shell workflow concept more than mutiple =
copies.=20
Back to the procedural programming paradigm...
You must do the best possible inside the workflow.
This is a CASE/Switch on an attribute in the lead object.
If you like the OO world. Task determination based on a variable is you =
best chance.
 
Otherwise copying workflows is like copying programs.
More damm code to maintain...
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia=20
M  +61 (0) 412 213 079
E  phil.soady at sap.com
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Robert.vande.Berg at nuon.com
Sent: Friday,12 March 2004 9:22 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Update or create a new Workflow?
 
 
Build in a check on the vendortype.=20
 
In the beginning of the workflow you can put a condition which checks =
the
type of vendor (perhaps attribute of the object of the vendor??). If =
the
vendortype equals the type you specify, then send a notification and =
end the
workflow. Else, proceed with the workflow as existing.
 
If you build a new workflow, you have to make startconditions to the =
old and
new workflows, and as Stephan says, you have to maintain a new one..
 
-----Oorspronkelijk bericht-----
Van: Becker, Stephan [mailto:stephan_becker.ext at siemens.com]
Verzonden: vrijdag 12 maart 2004 10:58
Aan: SAP-WUG at MITVMA.MIT.EDU
Onderwerp: Re: Update or create a new Workflow?
 
 
Do it in the same workflow, one less to maintain..
 
-----Mensaje original-----
De: "Schr=F6der, Ute Marion" [mailto:UteMarion.Schroeder at REWE.de]=20
Enviado el: 12 March 2004 10:15
Para: SAP-WUG at MITVMA.MIT.EDU
Asunto: Update or create a new Workflow?
 
Hi everybody,
 
this may be a stupid question,
anyway, I give it a try, maybe someone shares his / her experience.
 
We are on 4.7 right now.
 
Situation is as follows:
We have a customer created vendor-transaction,
depending on the action done, either the change or create-workflow is
triggered.
Now there has to be a new kind of vendor, which does not need approval =
via
creation as the others do,
there only ought to be a notice to a dedicated user, that such a vendor =
has
been created.
 
So, what do you think. Should I enlarge the existing creation-workflow =
which
has about 8 different arms by now,
or should I create a new one, where only this notice is posted?
 
Any hints from you will be of help.
 
Thanx in advance.
 
Yours
 
Ute