Overall Satisfaction with Nintex Process Platform
Nintex Workflow Cloud is used for several back-office processes such as manually routing insurance change requests (endorsements) to various groups for creation, approval, and distribution. Additionally, NWC was used extensively to allow for cataloging and storing claims materials including integration to cloud storage providers for document storage and retrieval. Another significant use-case for us was creating an Invoice approval process with conditional approval steps required based on department, invoice amount, etc.
- Integration to existing cloud solutions.
- Very smooth integration to o36/Sharepoint.
- Workflow builder (cloud) is modern and easier to use than most.
- The form designer is good for a no-code product with conditional rules for fields and support for file uploads.
- Difficult to fix flows that are in process (such as re-assigning a task for someone that is OOO or has left the company).
- Nintex support team does not have resolution SLAs (only acknowledgment SLAs). Occasionally this has led to key issues taking weeks to resolve.
- The number of integrations available is impressive, however, sometimes key methods are not available within an integration. This has been improving significantly in the past 2 years as the platform has matured.
- Process enablement - eliminates hundreds of extra emails, lost threads, and delayed business.
- IT Flexibility - Enables IT to respond quickly (and cheaply) to workflow requests for small projects without dedicating developers or other expensive staff to a project.
Integrations exist for Box.com, o365, Onedrive, Azure, SharePoint, in-house written APIs, microsoft flow, SQL Server, and others.
Nintex was purchased specifically to integrate a Nintex-hosted workflow with existing storage platforms such as OneDrive and Box. This has allowed Nintex to manage the workflow while a document is moved from a draft status all the way through to being a legally binding 'final' approved document. The integrations allow this to happen seamlessly with no special steps required by the users/approvers.
We use Nintex for any workflow that interacts with our users. It provides a much more professional and clean interaction and is easier to design that Power Automate. Power Automate is better at handling some technical scenarios and has good error handling capabilities, but is a clumsier interface than Nintex. We use the two platforms together and have even integrated the two into the same workflows in some cases by using the web service calls that are available on both platforms.
Do you think Nintex Process Platform delivers good value for the price?
Yes
Are you happy with Nintex Process Platform's feature set?
Yes
Did Nintex Process Platform live up to sales and marketing promises?
Yes
Did implementation of Nintex Process Platform go as expected?
Yes
Would you buy Nintex Process Platform again?
Yes
Nintex Process Platform Feature Ratings
Using Nintex Process Platform
35 - IT, Claims, Underwriting, Finance
2 - After workflows are authored, they take very little care-and-feeding if they are designed well. Most support activities occur when there is an outage in one of the integration steps or when someone leaves the company while there are still tasks pending.
- Invoice Approval
- Endorsement (document) authoring and approval
- Document management / storage
- Administrative IT tasks for Cloud solutions