Overall Satisfaction with Nintex Platform
We are using it as a self service portal for IT functions. This includes updating user details, alias email requests, new user accounts, licensing requests and help desk tickets.
- Paging in forms.
- Dynamically changing requested information on forms.
- Automating repetitive tasks.
- Update forms quickly if information needed changes.
- Let our apprentices update forms.
- Querying third party data sources on the form live (Equipment).
- Save and resume later.
- Error capture.
- Hours used by IT have dropped a lot to deal with low level issues.
- Apprentices have more involved roles now we ask them to maintain the systems thank to low code no code interface.
- The forms look nice with pages which really helps with user adoption.
- We've saved enough hours in terms of money to invest in new equipment.
We use in in Microsoft 365, which is really well embedded and integrated, which makes automating some IT things really easy. It also means our team don't have to learn a new system or memorise a new login, it's all inside what we already do.
It seems like you don't need a UAT environment for Nintex, which is different, we did try but found it didn't move easily and we lost the benefit of having this environment as we were rebuilding on live. There isn't any downtime and we export the previous version so we can roll back if we need it.
It seems like you don't need a UAT environment for Nintex, which is different, we did try but found it didn't move easily and we lost the benefit of having this environment as we were rebuilding on live. There isn't any downtime and we export the previous version so we can roll back if we need it.
It is by end users, they fill in forms, but they don't yet build with it, although we are trying to adopt this end user development model where possible.
These used to be great tools until the new pricing model made them really painful and expensive to use. Nintex pricing is more reliable and we can plan better.
Also PowerApps/Flow don't seem as intuitive to learn, they need some 'development' background.
A pet hate is also how Flow treats API call as a premium feature, this seems shocking. In Nintex it's standard.
Also PowerApps/Flow don't seem as intuitive to learn, they need some 'development' background.
A pet hate is also how Flow treats API call as a premium feature, this seems shocking. In Nintex it's standard.