Not too long after giving up on Bluespring’s BPM solution I came across Nintex on advise from somebody in the SharePoint community message boards. I think it was Ishai Sagi… Nonetheless I promptly signed up for the Nintex Workflow 2007 Beta and then their Release shortly afterwards. Ok, enough gibberish, so here’s my quick and dirty run down on my impressions of this software:
- Workflow 2007 is built as SharePoint Solution files and enabled using Features.
- Totally leverages the existing SharePoint workflow engine, no need to install any other process engines, or clients. Basically just upload the Solution files and install via Central Administration.
- The workflow designer is built into each site and can be enabled as a Feature.
- The designer utilizes AJAX enabling you to create the workflows ala Visio drag and drop style right in the browser. (That was key for me, no need to install separate designer client).
- Email enabled workflow approvals. Using their LazyApproval system you can just reply to the workflow email with specific keywords to enable it to continue.
- The UI is one of the best, very easy on the eyes.
- Feature set may not be as robust as other full blown BPM solutions.
- Relatively cheap (~$7000 US) and no crazy software licensing schemes. You can even buy it right off of their website without having to haggle with sales guys.
- Tech Support was AWESOME. The couple of emails and bugfix requests that I sent them were totally attended to and resolved by the very next business day.
Nintex Workflow 2007 is definately welcome in any of my SharePoint implementations as it is very easy to install, administer and use. The browser based designer would enable any business user to be able to design workflow processes. So why only 1.5 thumbs up? Well, it could always be better 🙂
I wonder if anyone from Nintex will see this post…maybe they can send me some schwag eh? 🙂
Nintex are cool, but two things need improvement:
1. they cannot attach a workflow to a content type
2. the workflow is not packageable and you cannot migrate it through environments (dev-test-prod)
oh, and my last name is Sagi (not sagai)
Whoops, sorry abut that Ishai! I’ve edited the post.
Thanks for the review Henry, and your comments Ishai. Just to let you know, Nintex Workflow 2007 already supports importing and exporting workflows through the Designer, however, we are currently working with Echo, another Australian company to enable replication of workflows across sites and different servers for the dev-test-pro scenario you mentioned.
Henry, thanks for this tip, I’ve just started to look in to how we can make best use of the workflow in sharepoint. It sounds like this tool might fill the gaps.
thanks for your tip..
by the way,,can you give me more information about the specification that needs to install this software?
or would you send the tempate?
please contact me at:
thanks for ur help;
i mean template,,
Have you seen k2 blackpoint? http://www.k2.com. You can attach a workflow to a content type. A lot of features and functionality connection to back end line of business systems via SmartObjects etc…
Nintex is currently also enrolling local European partners, e.g., in Germany, Luxembourg, and Belgium. E.g., check out the first German partner at
We have just released a tool for defining and deploying State workflows in MOSS. It is very easy to use and really powerful. You can download it from our website: http://www.datapolis.com.pl/en/Offer/Products/WorkBox/Pages/FreeVersion.aspx
We have also prepared small flash demo: http://www.datapolis.com.pl/en/Offer/Products/WorkBox/Pages/tutorials/tutorial_1/tutorial_1.htm
Plese send me your opinion about our product: firstname.lastname@example.org
Nintex received a very good review in a recent edition of asp.netPRO magazine.
This was a Excellent write up, I will save this post in my Mixx account. Have a good evening.
Right away I am ready to do my breakfast, later than having my breakfast coming yet again to read more news.