If you have a highly bureaucratic organization that is heavily focused on procurement, Emptoris can provide some value. It seemed to be very good at linking the contract information to procurement for better spend control. If you are trying to implement a standalone contract management solution that allows you to easily create contracts and store them in a central location, this isn't the tool for you. There doesn't appear to be a simplified implementation. In general, when a SaaS solution has a complicated and expensive implementation, I am very skeptical. This does not show that the vendor is trying to move customers forward on a single code base. If that many things need to be done during implementation, you are starting to customize the solution for every customer. This hurts the vendor's ability to scale and make improvements in the future.
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.
Document protection - the Check Out contract feature is a great way to allow external parties to make modifications to contract language without the ability to accept those changes. Those redlines can then be imported back into Emptoris and reviewed or further modified as needed.
Notifications & reminders - you can trigger an email manually from within the system, or you can configure automated notifications andreminders to alert users when a new task is received or has aged a given amount of days, etc.
Interview wizard - there is a lot of value in the interview wizard. Administrators can configure screens with selecting options via check boxes, radio buttons, or typed-in values. Variables and conditions can be used to selectively populate fields within the contract or apply other options, making for a quick and convenient method to generate contracts conforming to corporate standards.
Field customization - administrators can customize a list of options for various fields including contract substatus, address type, and user created business term variables.
Approvals - many different options are available to configure approvals to trigger automatically upon presenting and/or executing the contract including specific individuals, one or more approver groups, or based upon various criteria including terms within the contract, type of contract, or the contract's owning organization.
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.
Reporting, Emptoris comes with standard reports which can not always can be fit into our business. This needs to be improved. I hope Emptoris is addressing this issue in their latest releases.
Though the feature of editing language in MS word is excellent, loading MS word takes time.
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.
There are a lot of new, exciting products coming out in every field and I believe that there is always something better right over the horizon. If it was my choice, I would review my usage of Emptoris and other software periodically to make sure I'm using the most efficient software possible.
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.
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.
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 above rating for the overall support from Emptoris is for their product / product support, roll out training and refresher training / ongoing training, which is not only good but superior. There is no major or reconizable bad review that can be given to Emptoris at this point in time, from where is stands.
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 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.
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.
I am a fan of Ariba to be used for the entire lifecycle of Sourcing. From RFX's to cutting PO's. I feel Emptoris misses the boat on the idea of a "One Stop Shop" for all of your Sourcing/Purchasing needs
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.
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.
We won the 2005 Baseline Magazine Award for best ROI related to a technology implementation with an ROI 5544% (see 2005 Baseline ROI Awards, GlaxoSmithkline).
We always felt we could do "two times the work, with half the people and deliver double the savings".
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.
