Run Now in Nintex Workflow 2010

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 workflow. Meaning you are able to create, read, update and delete data in the connected system.

Once you click "Execute" in the ribbon area the action is executed and the configuration is tested. The result is afterwards displayed in the lower part of the window.


Conclusion
Run Now definitely makes configuring workflow actions lot easier. Any change to the configuration can be directly tested. There is no need to step through the workflow every time you make a change to the configuration in order to check that everything still works just fine. Further on, it is possible to test how the action behaves for different configurations if you use workflow variables.

An additional benefit is that you can easily retrieve the result from actions which support this feature. This can be then used to configure subsequent actions correctly.

Overall I say that Run Now helps during the design and testing of your Nintex Workflows. And it will not only shorten the time required to bring workflows which integrate with other system, but it will also help to make the workflows more robust. Promise is kept.

List of actions supporting Run Now:
  • Build String 
  • Call Web Service 
  • Execute SQL 
  • Query BCS 
  • Query LDAP 
  • Query List 
  • Query XML 
  • Regular Expression 
  • Web Request

Comments

  1. Kev Annfield25 January, 2012 23:20

    Nice post Veit. Just to add to the list of actions that have Run Now on them.

    -Query List
    -Regular Expression
    -Build String

    I think I've seen it on one more too but I can't find it now. Run Now is certainly a great new feature of Nintex Workflow 2010, v2.3

    ReplyDelete
    Replies
    1. sfsfsf28 January, 2012 14:42

      Thanks Kev for your input. I have updated the post with the three additional activities you mentioned.

      Delete
  2. Unknown31 August, 2012 02:10

    I'm having some difficulty. I do not have the "Run Now" option in any of my workflow items, it doesn't even show up. When I go to Central Administration, the option to "Enforce allowed actions at run time " is set to yes.

    I have tried running iisreset to enable the changes, it still doesn't show up. Any advice would be GREATLY appreciated.

    ReplyDelete
    Replies
    1. sfsfsf31 August, 2012 06:37

      James,
      Nintex Run now became available with Nintex Workflow 2.3 from January 10th, 2012. You should check your version in the Central Administration. Therefore, go to "Nintex Workflow Management" --> "Licensing". There you can see which version you have currently installed.

      Delete

Post a Comment

Popular posts from this blog

How long does "Delay for..." really wait?

Image
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
Read more

How to Handle Environment Variables with Nintex Workflow

Image
A topic you sure will run across is how to handle environment variables when you deploy workflows designed with Nintex Workflow. The values are by definition just valid for one specific environment, and have to be changed in order to deploy the workflow into another environment. Example for environment variables are URLs of web services or service accounts, which are different between development, test and production system. Basically, there are three ways how you can handle this information: store the information within the workflow activity create a workflow variable create a workflow constant Most people start with alternative 1 . The environment specific information is directly configured on the workflow activities. This has one advantage: You are pretty fast when you configure the activities the first time. But in the long run the disadvantages outweigh. After deploying the workflow from environment to the next stage, you have to update all affected activities. Beside th
Read more