<div dir="ltr">Hi Robert,<div><br></div><div style>I know it's ugly and I know it's probably not the best solution but a 1-minute wait step at the very beginning of your workflow should fix this problem. I'm guessing you already know that though.</div>
<div style><br></div><div style>regards</div><div style>Rick</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 10, 2013 at 4:11 PM, Robert van den Berg <span dir="ltr"><<a href="mailto:wug@bergtop-ict.nl" target="_blank">wug@bergtop-ict.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif">Hi all,<div><br></div><div>i have a custom BOR object build with a few virtual paramaters.</div>
<div>When I test the workflow by raising an event, the workflow starts but goes in error because a virtual parameter is nog yet instanciated. When I refresh the container, the rest of the virtual parameters is instanciated and now the workflow can be continued after error.</div>
<div><br></div><div>How can I make sure the workflow only continues when the object is fully instanciated?</div><div><br></div><div>Kind regards,</div><div>Robert</div></div><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" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br></div>