<br><font size=2 face="sans-serif">Workflow Folk,</font>
<br>
<br><font size=2 face="sans-serif"> I
have recently encounter a situation where a workflow was being started
directly, and although the required information had been added to the database,
the Commit process had not completed and when the w/f tried to start, the
necessary object(s) had not be instantiated. We changed the process
to initiate an 'event' and let the w/f processes take care of starting
it and everything is now working as expected. My QUESTIONS to you
all are: </font>
<br>
<br><font size=2 face="sans-serif"> From
a best practice's perspective, what are your thoughts on starting workflows
directly??? </font>
<br><font size=2 face="sans-serif"> When
is it appropriate??? </font>
<br><font size=2 face="sans-serif"> Have
others experienced similar situations and specific solutions???? </font>
<br>
<br><font size=2 face="sans-serif">Regards and Thanks,</font>
<br>
<br><font size=2 face="sans-serif">Hal Fairless</font>
<br><font size=2 face="sans-serif">SAP Workflow Support</font>
<br><font size=2 face="sans-serif">RMS, Tucson </font>