One of our biggest clients needed a workflow solution which can be used across the organization without much dependency on the IT Team. Nintex proved to be a natural choice because of it's ease of use, integrated nature and time saving features.
Now most of the teams in the organization are creating and maintaining their own workflows with little or no support at all from the IT team.
Out-of-the-box SharePoint workflows were very tedious to build and manage, whereas Nintex is an easy to use, integrated solution that speeds development of workflows while increasing transparency and accountability.
Integration with various platforms - One very stimulating feature about Nintex is the way it integrates with the other platforms that we use every day. To be specific, it allows you to connect to web service, CRM, Excel services, BCS, LDAP, active directory, XML and BizTalk. Moreover, the best thing about these integrations is that they require no code, thus allowing any of the users to incorporate them easily into workflows.
Debugging and troubleshooting - It reduces the effort in debugging and troubleshooting through explicit log messages, and the ability to easily disable specific workflow actions / branches.
Features like state machine multi-level approval, Lazy Approval (reply to approvals via email), Workflow visualizations, scheduled workflows, constants, delegation and so on, are available out of the box, without the need to write a single line of code, which makes it very appealing.
Manual start of site workflows - Currently Nintex Online does not allow a way to toggle manual start for site workflows.
Support for operators in *Wait for field change in current item* action.
Wait for item update action in Nintex on-prem enables developer to use different operator based on need. Please enable operators in Nintex online action or wait for field change in current item action.
Permissions to Nintex Apps (Forms and/or Workflows).
Currently anyone with full control to a list or library can access the Nintex forms and workflows. We want our business users to have full access to lists and libraries, but do not want them modifying workflows as they are business critical. We need only the development team to have access to Nintex in O365. In SharePoint 2013 on-premises, I would go to Site Settings -> Nintex -> Allowed Workflow Designers -> Remove permissions except for the development team. We need this same access control in O365.