Nintex works well at our fire department
August 23, 2019

Nintex works well at our fire department

David Witmer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Software Version

Nintex Workflow for Office365

Overall Satisfaction with Nintex Platform

I work for the Fire Dept. Other departments in the city also use the platform. We use it a lot for notification/approval of actions. For instance, if a firefighter desires a vacation day, the enter the request on a Nintex form and workflow is initiated when the form is submitted. The request goes to those authorized to grant the vacation day and record.
  • Approve/reject requests - form is auto-created. Workflow build is fast.
  • Email notifications - simple and fast.
  • Reminders for approval - easy to set up and insures action as required.
  • Getting the name of the responder to an assigned task is cumbersome. Requires strong extraction from string variable as opposed to just reading the name.
  • Determining if a particular document entry is the first or not is fairly complicated. You have to query the list, loop and add to the collection and then count items in the collection to determine how many entries have been made.
  • Streamlined business processes and reduced time required to change/adapt processes.
  • O365 workflow does not seem to be as robust as the in-house product. This perception is based on googling answers to data manipulation/processes.
Workflow and forms are based on the O365 platform. When we moved to O365, most of our old forms were in Infopath. We are still using infopath as it had some features that have not been found in Nintex. Deployment flexibility has been great for us, since we have multiple hardware platforms in the fire department.
Our IT staff consists of myself and my manager. We build the forms/workflows and the staff utilizes what we create. We have automated as much of the day to day activities as we can.
We have and continue to use Infopath for forms. There are certain aspects of functionality that Infopath gives that cannot be duplicated in Nintex. With Infopath, we could create multiple forms, with minor changes (date, location, etc.) and submit them whereas, with Nintex, we cannot do so. There was also more functionality options in manipulating form field in Infopath. Be that as it may, I think Nintex works better with Sharepoint.
Routing requests for approval and notifications are easy and quick to build. Working with documents is not nearly as straight forward. The issue with having to pay extra for document generation is unacceptable.
There is a lot of functionality that I have not been able to take advantage of due to not having the time to study the documentation. Also, the documentation is lacking somewhat. An example or two would make a great difference.

Nintex Process Platform Feature Ratings

Process designer
Business rules engine
Form builder