<div dir="ltr"><div class="gmail_default" style="font-size:small">WUG'ers :) (longtime no see)</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I am graduating to SCP Workflow and have a question, I wonder if anyone can help me out.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I have always built Classic Workflows triggered after an object has been created in a database, or SAP always saves the object and then sends the Wf triggering event. I would say thats best practice and it also fits with my other narrative about keeping process and application logic separate. </div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">In SCP it is possible to trigger a SCP Workflow without an Object, but is that a good idea? The thought it to trigger SCP Wf and have a step that calls a task to create the object, so the Wf is basically generic to start with, then becomes instantiated after the first step. Would anyone else think this is a good idea? I don't, I think a Wf should have an object before being started but I am having a hard time arguing the case, so really looking for other informed opinion.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Anyone got one?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div><div class="gmail_signature" data-smartmail="gmail_signature">Andy Curtis<br><br></div></div>
</div>