<div>If WF log is critical then create a WF attribute long enogh to hold the condtion. This attribute can be filled out in the BADI per each condition that has been executed. In workflow create a step to display the attribute.
</div>
<div> </div>
<div>This way you can see what conditions have been set in BADI also it will be easy to track the condition in question while keeping the WF simple and elegant.</div>
<div> </div>
<div>Raju </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 11/9/05, <b class="gmail_sendername">Mike Pokraka (WUG)</b> <<a href="mailto:wug.replies@workflowconnections.com">wug.replies@workflowconnections.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Sue,<br><br>Always a big question of keeping a balance between simplicity and<br>visibility. I lean towards visibility. Spend that little bit of extra time
<br>in designing sensible subflows and you can cram quite a lot of stuff into a<br>flow that still remains manageable.<br><br>Another factor to consider is putting as much 'business' conditions in the<br>WF as possible and hiding the techie stuff in code. Bear in mind that it may
<br>be business users looking at the logs, so hiding too much makes that<br>useless. Oh, and it makes productive debugging easier to have stuff in the<br>flow.<br><br>Just my 2c,<br>Cheers<br>Mike<br><br>-----Original Message-----
<br>From: <a href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</a> [mailto:<a href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</a>] On Behalf Of<br>Susan R. Keohan<br>Sent: 09 November 2005 19:55<br>
To: SAP Workflow Users' Group<br>Subject: Theoretical question - WF Design<br><br>Hello all,<br><br>I am in the process of designing workflows for SRM 5.0 (Shopping Cart<br>Release - using N-step BAdi, PO, etc.). My organization is very thin when
<br>it comes to workflow expertise. Therefore, I ask the<br>following:<br><br>Is it better to put conditions, branching, etc in the workflow itself, which<br>exposes the conditions, but also complicates the flow, and would require a
<br>WF person to modify/maintain, or<br><br>put a lot of effort into the underlying ABAP, the theory being that it would<br>be easier to find an ABAPer who can maintain/modify the code. The drawback,<br>of course, is that the conditions are not so visible.
<br><br>There's no right or wrong answer... just food for thought.<br><br>Happy WF-ing,<br>Sue<br>--<br>Susan R. Keohan<br>SAP Workflow Developer<br>MIT Lincoln Laboratory<br>244 Wood Street<br>LI-200<br>Lexington, MA. 02420
<br>781-981-3561<br><a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br></blockquote></div><br>