The unvarnished opinion
November 25, 2019
The unvarnished opinion
Score 9 out of 10
Nintex Workflow for Office365
Overall Satisfaction with Nintex Platform
We use the workflow engine and forms for several processes. One of our major processes is for the request and approval of secure access to our ERP. The form allows users to request access ad based on their choices, the form gets routed through different workflows to get access. Another use we have is with archiving old list items (automatically moving from one list to another).
- Branching logic in forms - This allows for a single form to cover related processes depending on choices made in the form.
- Seamless integration with Office 365, allowing us to drive actions in the workflow based on item changes in SharePoint Online
- The fact that it uses a separate service to offload the processing power instead of having to provide it as part of our organization.
- The new licensing structure can be confusing.
- The workflow canvas can get unwieldy to use as the workflow steps and branches expand.
- More builtin connections to more 3rd party services for data.
- With our diverse organization, being able to establish consistency is key and we can do this by creating a standardized form, process, and workflow with automation. So the process is easier and all of our people are doing it the same way. That is a game changer.
- The licensing is a little hard to follow and can make the product unaffordable.
- The approach of Nintex hosting the solution makes Nintex design their product for maximum usage. They have to make sure they can have their product embedded in a number of different systems; so, they use industry standard protocols and development.
We use it in SharePoint Online only right now. The flexibility of having options to use this in other systems is appealing, but we don't have the resources (personnel) to approach this yet.
We don't have any none IT staff designing or implementing the solutions yet. However, when our IT staff designs solutions, they work with the business and process owners closely in every step, often showing them iterations of the workflow diagrams and forms. The non-IT staff are heavily involved in testing and often make suggestions to the workflows.
Nintex is much more powerful for complex workflows. Flow is great for simple and quick personal level (or maybe even team level) scenarios. For more complex workflows, that require extra care and handling or approval, as well as adherence to a more stringent lifecycle such as saving to the enterprise data stores, etc., Nintex is much better.
Running complex or multi-step workflows is really where Nintex shines, especially if you don't have developer resources on staff. With the WYSIWYG like workflow canvas, you can easily see the logic and build the necessary steps using out-of-the-box controls included in the product. Branching logic or conditional steps are easily supported and the concept of state machines is supported as well.