We performed a comparison between OutSystems, QuickBase, and ServiceNow based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Oracle, OutSystems and others in Rapid Application Development Software."Integrations with external systems with SOAP and REST are easy to implement off-the-shelf, but a developer can always implement specific libraries for other integrations."
"OutSystems is a low-code solution. Most features are like drag-and-drop, so it's pretty easy to work. Thus it helps the organization by saving time for developers."
"The most valuable feature is Agile development. I love that you save a lot of time on development and can focus on logic and business requirements."
"We can quickly develop an application using the tool."
"It is much easier to develop applications with the product’s IDE."
"We can do the validation before calling the API."
"Once built, web/mobile components can be reused in all new developments. In addition, the OutSystems Forge is very useful. We can exchange components and even already-built applications, reducing costs to build specific solutions."
"I really like the one-click publish feature in OutSystems. In other development tools/languages, it's not as easy. I also like how easily I can manage all my projects in one place."
"The need for little to no code knowledge has been huge."
"We have made good use of the ability in QuickBase to add multiple apps for various departments and purposes, while some apps are shared."
"It is low-code. We are able to go in and create apps quickly. It is very helpful for the size of our company. We're a mid-size company, and at this moment, we don't need anything externally. We don't have to go out and consult a consulting firm to build something from the ground up. So, the ease of that and being able to get development quickly up and running has been good for us."
"It provides a well-organized method for overseeing everything, especially considering the remote work aspect."
"Considering factors like functionality and price, the product proves to be worth the investment."
"There's a lot of stability in QuickBase...I really appreciate the processing part of QuickBase, especially considering how we're able to get information in real time instead of having to wait."
"It has helped streamline and simply track status and collection of data from suppliers and other internal departments."
"Allows users have anytime/anywhere access."
"I have found many features that are important and that are easier when compared to Remedy; for example, the Scripted REST APIs and the Flow Designer... The Client scripts are simpler when you compare with Remedy."
"It's easy to integrate. For instance, yesterday we closed the integration with SAP for the IP business management module to manage the forecast of projects. We created an interface between ServiceNow and SAP to control projects for accounting and on the forecast of the project. It was really easy. We don't have any problems with ServiceNow at the moment. As a company, they are improving constantly."
"A workflow automation platform that's reliable, performs well, and has good reporting and integration."
"The solution integrates well with other products."
"You can scale the solution."
"It facilitates the monitoring of major incidents and provides insights into the effort expended to resolve each incident."
"The look and feel is a valuable benefit for adoption."
"I find almost all the features valuable. It can do nearly everything except make your coffee, as my colleagues always say. It's got pros and cons, like every software, but the good thing about it is that it has a very structured approach."
"I would like to see improvements in versioning. It can be challenging to keep track of what changes should be committed, especially when many developers are working in one environment."
"We have performance issues while fetching bulk data."
"In OutSystems, cloud management is an area of concern where improvements are required."
"Mobile apps should have been fully native."
"There are not enough resources on the market."
"The new version could be improved."
"OutSystems could improve by being more like GitHub. It would be more helpful for us for division management and version control for our application."
"The product could be improved if there was a shortcut, or predefined, predictable templates provided."
"Its UI needs improvement. They should improve it and make it a little bit more modern. We should also be able to have more real-time information that connects with other software platforms. It has an open API, but it doesn't always connect with some of the other platforms that we would like to utilize. These are probably two of the biggest things for us, and hopefully, they will keep ensuring that in the future, they continually build QuickBase to be a little bit more efficient in that regard."
"I would like the product to add more working processes."
"This rule: The Maximum is 60 rules. We need to provide more in order to improve."
"I would like to see better options for producing paper reports from Quick Base, rather than viewing things exclusively on screen."
"Whenever we do onboarding, or we get new employees, there tends to be a delay of not just a week but a couple of weeks, and sometimes even a few weeks of being able to see certain new employees in the system."
"The dashboard is not organized."
"There is room for improvement in terms of user-friendliness."
"Third-party integration -- they are working on it and I find their brand-new still-in-beta Webhooks very promising."
"The level of complexity and the level of discovery are the two areas that can be improved. Its UI needs to evolve. They focus a lot on cool colors and other little things, which don't bring value in terms of functionality. They need to focus less on presentation and more on the functionality within the UI. Its discovery mechanism should be improved. There is a component in ServiceNow that discovers the assets, but it doesn't do an immediate discovery, and there is a lag. If I want to open a ticket for a laptop or an asset, that asset needs to exist within ServiceNow for me to be able to say that I need to have its disk space or memory increased. It is referred to as a CI or configuration item in ServiceNow. Sometimes, ServiceNow doesn't discover these items, and as a result, I cannot open a ticket and tag that system or asset. If a system was introduced to the environment last week and it is still not listed, it becomes a problem. I will either have to wait or manually enter that system or asset. So, if I have a laptop with only 8 GB of memory and I want to request 16 GB of memory, I won't be able to do that in ServiceNow because my system or asset hasn't been discovered yet. Discovery is not immediate, and there is a lag."
"The solution could improve by making the CMDB integrate with a CI better to allow it to be seen across multiple platforms."
"There should be fewer clicks and faster integrations between solutions."
"For healthcare, which is a pretty audited environment, there are no concrete solutions for digital signatures, apart from our license with Adobe, so it requires orchestration."
"The asset management application could be improved. They have a lot of the infrastructure built, but it does not come with already made compatibility with some of the most popular vendors, such as Cisco and Microsoft. You have to fix it yourself."
"The pricing of the solution could be better. It's a bit high."
"The RPA needs improvement. That's a new area for them that they're just entering into now."
"The challenge with ServiceNow lies in its expansive portfolio of services. It can be complex, and users may find it expensive and challenging to understand. There is a need for a configurator within ServiceNow that guides users on how to utilize the tool effectively. This configurator should provide insights into licensing, team requirements, and the best licensing model based on whether companies prefer ownership or consumption-based models."
