The Alfresco platform, from Hyland, delivers comprehensive cloud-native content services. It is used to intelligently activate processes and content to accelerate the flow of business.
N/A
Nintex
Score 7.9 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
Nextcloud is good for it's intended use case but because Nextcloud has an AGPL license, that limited what we could do with our Proprietary solution, where's Alfresco LGPL is more flexible for us.
The integration is very easy and can be done with minimal time. The features like sending email, inbuilt integration with CAMEl, MULE, BOX, etc. In addition to this, the adoption of activiti-7 (the microservice version) wins the race against other tools. As the infrastructure …
The biggest positive about Alfresco Content Services is its open-source nature. There are many possibilities of utilizing it in existing ecosystems using integrations.
All software has some pros and some cons. Alfresco has some good pluses, and suits our environment very well. It fit perfectly in the place that we are working on. That is why we decided to go with this software. Overall, the kind of content management that needs to be done in …
- Alfresco provides more capabilities by leveraging open source components. The core architecture itself is JCR compliant which gives easy options for future migrations. - The PDF rendition in Alfresco comes with LibreOffice at no additional cost. - Alfresco support integrations …
Java based open source wide community and popular ECM which is used by fortune 500 companies.
Verified User
Anonymous
Chose Alfresco
none
Verified User
Anonymous
Chose Alfresco
As already explained earlier, the cost of licensing and support comes down very much by using Alfresco compared to Stellent and Sharepoint. Plus the overall performance and feature set is much broader for Alfresco. Since it is a newly developed content management system, it …
Alfresco provides by default a very user-friendly user interface, And it's highly configurable. Moreover, the license model is really interesting compared to both solutions.
Ultimately a cost decision - Alfresco community is free and has a decent community and various forums, books, etc available. The enterprise version is far less expensive than other options (although costs can add up depending on the the hardware it's running on). It is built …
We selected Nintex because Process Manager is a purpose designed platform for knowledge management. However, what we discovered is that there are significant limitations, which has lead us to now explore developing a knowledge management platoform in sharepoint. this is a much …
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 …
Nintex Process Platform is a great tool for automatic tasks and creating forms in SharePoint Online. For automating using other applications, including third party, Power Automate has more usage.
Xmind was great for mind mapping, but when I tried to use it as a process mapper, I found it was rather lacking. It has its uses, but process mapping (at least for us in our stage and phase of mapping) was not up to the task, unfortunately. We didn't have any other software we …
We use Outsystems for other processes in our operation but we see that this platform is not able to indentify processes when drawed. Besides that OutSystems requires some basic development knowledge to use it. This makes it not really useable for business units.
Nintex workflows has much complex process management tools and better integration tools than Microsoft Power Platform. Being able to host it on premises is also an important feature for companies that are not cloud fans.
Nintex was selected because it was somewhat unique in its capabilities and depth/breadth of ability 7+ years ago. However, the competition has now caught up and pricing is a significant factor in whether we continue to use Nintex going forward.
Nintex Process Platform was and still is by far the most flexible and easy-to-use than any of the other form creation and workflow designer apps we looked at.
It's much more reasonably priced and we were able to actually experience the platform for a bit before we made a decision. And by the time our demo was finished we had already started depending on it for some of our processes so it would've been very hard to separate from it.
We use Microsoft Power Automate as well in our organization but used Nintex Automation Cloud workflows for most of the automation workflows because NWC is low code solution to develop automation workflows for SharePoint, integrate well with Microsoft teams, better designer tool …
We are using Nintex for SharePoint 2016 forms and workflows only for all kinds of automation. It has the following benefits over others. It is faster than working with the old SharePoint Designer and its
textual design or Visual Studio with coding. Less complex workflow can
If you have regulatory or business needs that require saving email into Alfresco and you are using Outlook for Mac, you may need to perform significant customization to make it work. Additionally, if you will have users that will be members to a large numbers of sites over time, you need to thoroughly explore what functionality will be degraded or lost and how to mitigate the impact. Other than these two scenarios, I cannot think of any scenarios where Alfresco would not be well suited to an organization's needs.
The Nintex K2 platform is not only efficient and developer-friendly, but the support provided by the vendor is also highly commendable. The platform's ease of use and robust functionality make it a preferred choice for developers, while the vendor's exceptional support ensures smooth implementation and ongoing assistance, enhancing overall user satisfaction.
Alfresco Process Services and Alfresco Application Development Framework integration makes for best functionality/application of ECM.
Use case alignment - Marketing content and documentation of specific business requirements and user stories being available as reference material/documentation.
Difficult to fix flows that are in process (such as re-assigning a task for someone that is OOO or has left the company).
Nintex support team does not have resolution SLAs (only acknowledgment SLAs). Occasionally this has led to key issues taking weeks to resolve.
The number of integrations available is impressive, however, sometimes key methods are not available within an integration. This has been improving significantly in the past 2 years as the platform has matured.
As per the current market and the line of products that are available for content and document management system, Alfresco is a very good option compared to other systems in terms of features and cost. Plus the community support is great. Also since the product is open source, it can be extended or understood in a better way.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
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.
I am not big fan of Alfresco Content Services' support; it works on its own speed and sometimes it becomes challenging to achieve business needs. However, I appreciate regular delivery of security patches and updates
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.
Process was relatively smooth and overall, downtime minimal. MSI was very responsive to our needs and made the transition easier than it otherwise might have been.
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.
The integration is very easy and can be done with minimal time. The features like sending email, inbuilt integration with CAMEl, MULE, BOX, etc. In addition to this, the adoption of activiti-7 (the microservice version) wins the race against other tools. As the infrastructure and application modules can be deployed independently.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
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.
It definitely has a positive ROI in the overall business, as content management has become easier and more centralized.
Video and image content management has become a major plus, as they play an important role in dynamic digital marketing. Once the code is written to accommodate image and videos, we can change this content any time depending on the season of the year, what products we are looking to market, and to what type of clients.
It helps with easy control of the system with the business teams rather than having control with the technology teams. Hence it makes it easy to customize and make changes at any time. This also reduces the overlap that technology has with business and helps treat both of them as separate entities.
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.
