Thanks for the reactions.
I want to close the subject but I do not know how.
At the OneXacademy we have been working hard to produce a full learning syllabus to cover Nintex Office 365. It is in QA review @ Nintex.
So now we know the differences. Thanks for all the contributions.
Anybody who has reacted to this post can have a free copy. Please send your request directly to email@example.com.
@ the OneXacademy we are providing online learning material for Workflow and Forms as well exams. We have been approached by people who want to have a 365 training.
We are a bit puzzled.
This is what we know ourselves:
I'm working on a blog about this. Would love to co-author one if anyone else is up for it. :-)
There are some inherent difference between on-prem and O365. From what I know using both, workflow and forms are easier for end users on-prem. You have way more actions and the ability to do certain timer job like functionality that is simply not available in the cloud due to either permissions issue or the fact that Microsoft wont let you.
Also most workflows in the cloud has to run based on the URL of something or a web service call etc... This is because things are not as relative to your site and they are on-prem. There are less function/actions that are available as well.
Some quick thoughts.
Would be very keen to see this once done, just about to start a feature comparison specifically for what I use, which isn't the whole feature set.
On a licencing point of view :
Office 365 users have to be licensed and if the customer plans to include external people into the processes, they have to be counted as well.
We don't have a document as such, but my colleagues blog may help with whats available in Office 365: Nintex Workflow for Office 365 - Available Actions - Vadim Tabakman
I hope this helps!
Nintex Workflow and Nintex Forms for Office 365 are completely new products developed from the ground up for Microsoft Office 365. As a result, they have quite a number of key differences compared to the on-premises products as outlined below:
In the case of Nintex Workflow for Office 365, there are a number of additional key differentiators:
New Workflow Engine - Nintex Workflow for Office 365 uses the new Workflow Manager engine that is available in Office 365, and takes full advantage of the benefits and actions this platform provides.
You can find the entire list of available actions here.
Thanks for the answer. The list from Vadim helps.
Is there a similar list for Forms?
The problem with answering this question in a formal document is that the answer will change very frequently, and future searches will produce links to what will quickly become inaccurate documents. New things are being added to the online versions every month.
To me, the biggest difference *at this time* (early August of 2014) is that NW and NF honor the default behavior for SharePoint 2013 workflow task items, meaning that there's a default workflow task behavior, and if you want to change it, you must create a custom content type. It's admittedly not as easy as the FlexiTask -- yet -- but it does work.
You can create a custom NF form for a specific workflow task content type in a given task list, so task forms are very possible. It's admittedly not as easy as designing the form from within the workflow -- yet -- but it does work.
Both of these things will change, but we opted to remain linked to SharePoints' content type-based approach to tasks in order to ensure compatibility with Outlook and other client-side extensions.
Thanks Mike, love to see you again in the Netherlands @ Triple A. Still remember the discussions with you about future Nintex functionalities.
Twan Deibel, CEO
M: +31640259724 | E/Lync: firstname.lastname@example.org<mailto:email@example.com> | I: www.onexacademy.com<http://www.onexacademy.com/> |
Most other products have release documentation detailing what has been added in the latest version. If Nintex are hesitant to release a static document, could they instead put the current action list on the Community site and add to it as new actions/features become available? It would make it much easier for companies to plan workflow migration from Nintex in SharePoint on prem to NWO365. Even if it does become out of date, it's still better than nothing at all (providing it's date stamped).