Veit Sanner's Blog

First looking at the action "Pause for..." I was thinking think that I could configure the delay period precisely to the minute. However, when I used this activity I discovered that the activity did not behave as I as expected. This was especially true when I entered an interval shorter than five minutes. I always waited longer than configured. Looking deeper, I found out that the cause for this is the SPTimerJob job-workflow  which controls the triggers for " Pause for... ". This timer job runs with the standard configuration every five minutes. If you set " Pause for... " to a shorter interval, the trigger send by the timer job will be sent every five minutes anyway. The same applies when you set the action to pause the workflow for any period of time that lies between the configured schedule for job-workflow . Of course, an option to solve this issue is to reconfigure the timer job to run in shorter intervals. But ask yourself if this is really nece

With version 2.3 Nintex introduced Run Now into Nintex Workflow 2010. Nintex promises that with Run Now the integration with other system will be easier, because workflow designers can test actions with Run Now support already during the design stage. It is not necessary to start and step through the workflow until you reach the actions. Can it keep up to the promise? Run Now can be accesed on all supported actions during the workflow design stage. Start with a new blank workflow and then drag an integration action into the design area. I will be using Query LDAP for the rest of this post. The other actions work alike. After you have configured the action select "Run Now" in the ribbon. A new window is displayed where you can test the configuration. If you are using workflow variables for the configuration you can replace them with actual values. And remember: As soon as you press execute the target system will behave as if you execute the action from the workfl