<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>General</title><link>https://www.infopathdev.com:443/forums/41.aspx</link><description>If you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Timed Workflows</title><link>https://www.infopathdev.com:443/forums/thread/107097.aspx</link><pubDate>Mon, 20 Jun 2016 20:04:04 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:107097</guid><dc:creator>dapklp</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/107097.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=107097</wfw:commentRss><description>I asked the Web guys to change the frequency from daily to hourly, which they did. Same thing happened. At the first appointed time, the workflow fired and I got the desired results. I reset the records or loaded new ones that would be caught by the next appointed time, and...nothing. In the case of hourly, 5 appointed times have come and gone and 2 files which satisfy the workflow criteria still sit without triggering an e-mail or a change to the file (resetting a flag). I don&amp;#39;t have the repeating feature turned on because upon the appointed (day/hour), the workflow should trigger and the record would change to prevent another e-mail or file change. I&amp;#39;m sure it is a scheduling issue or possibly a load balance issue (we use 2 SharePoint servers). I can get it to work once, but just not for files that it should work at the repeating times.</description></item><item><title>Re: Timed Workflows</title><link>https://www.infopathdev.com:443/forums/thread/107077.aspx</link><pubDate>Fri, 17 Jun 2016 15:17:29 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:107077</guid><dc:creator>dapklp</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/107077.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=107077</wfw:commentRss><description>For the folks following this, I provided some additional information to Hilary whereby my CA policies did not fire the next time, presumably because the other method I was trying (using pause actions) caused an &amp;quot;in progress&amp;quot; status for a wworkflow when I wanted the CA policies triggered workflow to trigger. I made more adjustments and since the CA policies are administered by the Web server guys, I&amp;#39;ll report the results expected tomorrow at 2:15 AM</description></item><item><title>Re: Timed Workflows</title><link>https://www.infopathdev.com:443/forums/thread/107076.aspx</link><pubDate>Fri, 17 Jun 2016 15:10:56 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:107076</guid><dc:creator>Hilary Stoupa</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/107076.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=107076</wfw:commentRss><description>The only thing I can think of is pausing. Depending on the conditions under which your workflow runs, I guess the one thing I&amp;#39;d make sure of is that I don&amp;#39;t end up with a new instance starting &amp;amp; pausing each time the form is opened or revised.... and I guess I&amp;#39;d be concerned about how to handle for a changed expiration date? Could that happen?</description></item><item><title>Timed Workflows</title><link>https://www.infopathdev.com:443/forums/thread/107025.aspx</link><pubDate>Tue, 14 Jun 2016 19:06:12 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:107025</guid><dc:creator>dapklp</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/107025.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=107025</wfw:commentRss><description>&lt;p&gt;I tried using the Information Management Policy and Expiration Policy (on CA) method laid out in &lt;a href="http://blogs.askcts.com/2013/05/14/creating-a-timed-workflow-in-sharepoint-2010/"&gt;http://blogs.askcts.com/2013/05/14/creating-a-timed-workflow-in-sharepoint-2010/&lt;/a&gt;, but it has not worked for me yet. I had the Information Management Policy sent to run daily at 2:00 AM and then the Expiration Policy to run at 2:15 AM. I then created a worfklow that looks to see if a particular date field equals today, then send me an e-mail. It didn&amp;#39;t work. I made adjustments and will see tomorrow if I get the expected results.&lt;/p&gt;&lt;p&gt;&amp;nbsp;In the meantime, I tried another approach, but couldn&amp;#39;t get the workflow to revise a counter field I in my form using a workflow. &lt;/p&gt;&lt;p&gt;&amp;nbsp;So, seeing the pieces I could play with, I created a workflow that looks for a certain State (in my form), has it send an e-mail to me announcing the clock is ticking, find the difference between today and my expiration date field and store that as a variable (in number of days), pause the workflow for the number of days using the variable, and then have it e-mail me after the pause. It worked, but I&amp;#39;m wondering if having a workflow pause for possibly 11 months is a good idea.&lt;/p&gt;&lt;p&gt;The other thing is...&amp;quot;is there an easier way?&amp;quot; I just want to send an e-mail when a certain date (field) is reached - automatically. Ideas???&lt;/p&gt;</description></item></channel></rss>