https://www.infopathdev.com:443/forums/39.aspxNew to InfoPath? Search to see if your question has already been answered. If it has not, then ask it here or the appropriate topic forum.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/86265.aspxTue, 22 Jan 2013 08:16:51 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:86265JenniferLindsay0https://www.infopathdev.com:443/forums/thread/86265.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=39&PostID=86265<p>Here&#39;s an idea: Add a hidden field to your form called Count&nbsp;(or whatever you want), make it a promoted property so it appears in the library columns, and when you submit a new form to the library make sure the value for Count is set to 0.&nbsp; </p><p>Next, add a step to the very top of your workflow to increment the value in the Count column by 1 every time the workflow runs.&nbsp; </p><p>Put the rest of your workflow (the steps you already have)&nbsp;underneath this new step inside an If condition: &quot;If Current Item:Count is equal to 1&quot;.</p><p>Now, the very first time you submit a form to the library, Count will&nbsp;be incremented&nbsp;from 0 to 1, the If condition for the rest of your workflow will be satisfied, and the rest of your workflow will run just the way you want.<br /><br />If the user deletes the form and then restores it, Count will&nbsp;be incremented&nbsp;from 1 to 2, the If condition will&nbsp;NOT be satisfied, and the rest of your workflow will NOT run.</p><p>&nbsp;I haven&#39;t actually had a chance to test this, so if you try it do let me know if you run into problems.</p>https://www.infopathdev.com:443/forums/thread/85898.aspxWed, 09 Jan 2013 15:32:07 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:85898bline220https://www.infopathdev.com:443/forums/thread/85898.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=39&PostID=85898Hello, I have a request to see if i can fix the following and I am not sure if it is possible with out of the box functionality. The issue is, when a user deletes an item from a library and it gets restored it starts the workflow over again so a series of emails get kicked off. How do we prevent this on restore? Currently the workflow is trigger to start on item creation so I believe that is why this is occurring. We do not want to manually start this workflow so I don&#39;t know if we have any option but to put up with this inconvenience. Any ideas. Thanks.