Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Oracle BPM Suite
Score 8.5 out of 10
N/A
The Oracle Business Process Management Suite is an integrated environment for developing, administering, and using business applications centered around business processes.
N/A
ServiceNow IT Service Management
Score 8.2 out of 10
N/A
Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
N/A
Pricing
Nintex
Oracle BPM Suite
ServiceNow IT Service Management
Editions & Modules
Enterprise - Process Platform
$480
Minimum 1,000 users per user
No answers on this topic
ITSM Standard
Custom Quote
ITSM Pro
Custom Quote
ITSM Enterprise
Custom Quote
Offerings
Pricing Offerings
Nintex
Oracle BPM Suite
ServiceNow IT Service Management
Free Trial
Yes
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
—
—
ITSM Pro and ITSM Enterprise also are available with optional "Plus" add-ons. These include AI Agents, an AI Agent Studio, and other features that augment the capabilities of the platform using AI Virtual Agents to automate tasks.
Nintex Process Platform has a comprehensive guide, that equips subscriber regarding the use of the program. Further, the Nintex Process Platform generates a design that requires no coding, where some staff without the ICT basics maximize it. Lastly, the Nintex Process Platform …
Nintex is still ahead of the curve on many of its competitors for a number of actions they offer. We do frequently evaluate other tools as many other offerings are rapidly closing the gap. Microsoft Flow has come a long way in the past year and I foresee them giving Nintex a …
Nintex is a true no-code software platform that provides tremendous flexibility and ease of use that allows our nontechnical employees to get greater usage out of the platform. We viewed the platform as just more versatile than others and it can grow throughout our …
Nintex forms has easier onboarding then PowerApps, but perhaps doesn't have as much freedom to connect to different datasources. Nintex workflow is a lot more feature rich than MS Flow however not as easy to access.
The integration of Nintex with SharePoint was seamless and the affordable cost allowed us to deploy the service as a shared platform without the need for complex charge back models to each team. Developing in ServiceNow is significantly more complex and more expensive since it …
Nintex was selected to extend our Sharepoint-based workflow automation capabilities. It literally grew out of the Sharepoint ecosystem and was used by people who were familiar with this technology stack. Nintex never fulfilled the vision of a process automation stack but found …
We’ve used both Windows Workflow Foundation and Windows Workflow Manager, and for very simple tasks ornprocesses these can work, although fall short when more complex process are introduced. We had also evaluated K2, and although it had MOST of the same functionality, we found …
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Oracle BPM is well suited to organizations and environments that have a good understanding of their business processes and organizational structures. Trying to introduce a tool such as Oracle BPM into the organization without a good grasp on how the business operates is a recipe for disaster as the implementation will uncover all of the dirty secrets of an organizations business processes and bring them to light. BPM is not to be utilized for smaller service orchestrations or technical service implementations, these should be handled by the Oracle SOA Suite using the BPEL process manager, leaving BPM to handle the organizational business processes, referring to and including lower level services and BPEL processes as needed.
It is well suited for medium to large companies that require a tool to allow users to create IT requests, have a self-service portal, track the completion of such requests and have access to KPIs to understand the satisaction level of the requestors. It is not the best tool if you want to have a heavy personalized IT Service Management tool to cater to all your needs or when you want to have an easy way to search for past tickets using specific keywords.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
Oracle BPM is left behind by other tools more modern in terms of user experience, usability and ability to integrate with everything else.
To really harvest the potential of Oracle BPM you need to do it in JDeveloper and with ADF. This restricts its usage to very technical people.
The administration of the Oracle BPM tools has really put a burden on our team. It is running on Weblogic and we experience issues very often either with performance or with a bad configuration of the system.
As with all Oracle products, the price can be an issue for smaller shops.
Finding requests that I opened and have since been completed by the assigned group/individual is very difficult to accomplish unless I've written down the request numbers somewhere.
Requests that I opened and are subsequently closed, often continue to appear in the list of "My Open Requests" giving the appearance that they were not completed when in fact they were.
It may exist, but if it does I haven't found it yet, which makes it less than intuitive, but I would like to see the ability to recall a request in ServiceNow.
I believe our firewall rule change request for is a custom form, but it has a serious drawback. If I submit such a request and need to make a correction to it before it is approved, there isn't anyway for me to do so. The request has to first be rejected with the creation of a sub-task in order to edit it before it is resubmitted for approval.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
It has helped us a lot, and after some training and getting to know the product, we are quite comfortable with it and feel much more capable of understanding what's going on in our IT environment. The only reason it doesn't get a perfect score from me is that there is a learning curve for both end users and IT admins using ServiceNow. Once you customize the UI and remove unnecessary fields. You are left with a very clean product that does what it needs to and does it well.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
We evaluated Bonita and found that it might fit a smaller-sized company better; we found that Oracle BPM Suite scaled much more evenly. We almost went with one of the competitors, but in the end chose Oracle BPM Suite after we factored in the cost of VMware licensing. There are literally tons of analytics on the back end which are great for upper management, but not so much for average users, but this fits our business model quite well.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
You'll most certainly need a deep dive and extensive training before your users can even think of using the product and they are very expensive.
Lack of documentation makes it very difficult to manage the application if any error is encountered which will result in you ending up hiring a dedicated person to look into the application once it's deployed.
For a very large org., if properly implemented and used, it can help identify the cost-intensive and inefficient processes.
We don't currently have a CMDB, so we are leveraging ServiceNow to build one using their ITSM and ITOM tools. This is a huge gap for us as a company and it will be a big win once this is in place.
The core help desk functions are comparable to most other tools on the market, but SN does a great job of integrating that data with other modules like Problem, Change and Event Management to provide a truly integrated solution.
The tool is expensive, so you will need to try to do as much as you can with the platform. We currently use other systems for HAM and SAM but will be including these in our ServiceNow instance in the future to help maximize our ROI.
