Most Helpful Review
Our solutions using Nintex has been most successful in automating HR processes because it allows you to easily and rapidly build solutions that conform to the unique business processes for each entity.
This tool set makes it easy to integrate current processes and increase adoption rates and usage for the tool, as well as the process changes to update it on the fly.
I like the feature of getting an email for a workflow error, then I do not have to go through every instance.
This tool is really helpful in reducing a lot of manual work. Its drag and drop components help to create a workflow faster than SharePoint Workflow Designer.
The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging.
The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)
Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed.
I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well.
Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API.
It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console.
I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods.
Bring all features available from the on-premise product into the cloud version and the workflow error reporting.
User interface could use some improvement. Perhaps integration with Visual Studio or SharePoint Designer would be useful.
Currently, copying workflow actions from one workflow to another is not possible. Also, the Office 365 solution is not as mature as on-premise.
Nintex seems to be very server intensive. It is one of the reasons that we are moving to a different product on the SharePoint 2016 platform.
While Nintex Workflow has pretty robust troubleshooting abilities, I think that improving the default logging and notifications would be helpful.
Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion.
When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods.
The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that.
The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution.
Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems.
This product has too many gaps. You find them after update installations. This should be covered by automatic testing.
Pricing and Cost Advice
Offering a licensing model that allows for multiple small workflows would be a huge improvement to an already great platform.
Nintex products are expensive, but valuable. Licensing in on-premise was historically based on a perpetual model, where you’d license per Web front-end. However, they are switching exclusively to a consumption (subscription) model, where you purchase the number of workflows you think you’ll use in your environment, and can scale up from there.
Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client.
Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials.
Compared 50% of the time.
Compared 25% of the time.
See more Nintex Workflow competitors »
Compared 7% of the time.
Compared 28% of the time.
Compared 9% of the time.
See more webMethods competitors »
Compared 6% of the time.
Also Known As
|Also Known As||Nintex Workflow Platform|
The award-winning webMethods Integration Server, our Enterprise Service Bus (ESB), is a complete enterprise application integration solution. It's standards-based so it "speaks" any technology. You can integrate any technology from any vendor: ERP systems, databases, mainframes and legacy apps. SaaS platforms, Web services, JMS messaging systems and packaged apps.
Learn more about Nintex Workflow
Learn more about webMethods
Information Not Available
|Fujitsu, Coca Cola, ING, Credit Suisse, Electrolux, GTA, CosmosDirekt|
No Data Available
VISITORS READING REVIEWS
VISITORS READING REVIEWS