Theoretical question - WF Design

[Mike Pokraka (WUG)]

Hi Sue, 

Always a big question of keeping a balance between simplicity and
visibility. I lean towards visibility. Spend that little bit of extra time
in designing sensible subflows and you can cram quite a lot of stuff into a
flow that still remains manageable. 

Another factor to consider is putting as much 'business' conditions in the
WF as possible and hiding the techie stuff in code. Bear in mind that it may
be business users looking at the logs, so hiding too much makes that
useless. Oh, and it makes productive debugging easier to have stuff in the
flow. 

Just my 2c,
Cheers
Mike

-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf Of
Susan R. Keohan
Sent: 09 November 2005 19:55
To: SAP Workflow Users' Group
Subject: Theoretical question - WF Design

Hello all,

I am in the process of designing workflows for SRM 5.0 (Shopping Cart
Release - using N-step BAdi, PO, etc.).  My organization is very thin when
it comes to workflow expertise.  Therefore, I ask the
following:

Is it better to put conditions, branching, etc in the workflow itself, which
exposes the conditions, but also complicates the flow, and would require a
WF person to modify/maintain, or

put a lot of effort into the underlying ABAP, the theory being that it would
be easier to find an ABAPer who can maintain/modify the code.  The drawback,
of course, is that the conditions are not so visible.

There's no right or wrong answer... just food for thought.

Happy WF-ing,
Sue
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug