Best fit for this product: - Advanced or Sophisticated Enterprise Search platform: If you spend effort on your search capabilities, Endeca is the tool. - If you are looking for capabilities to search and navigate similar to a relational-database system, then Endeca is not the best fit. - If you are spending effort to drive customer experience, especially around customer interaction with your web application, Endeca can help with that in a multichannel environment.
We can recommend this software without hesitation, as it has the ability to generate reports and data analysis, as well as process the data automatically, which saves time. It is ideal for small and medium-sized companies that wish to improve their services in the business world
Provides exact, correct counts of items in its dimensions.
Allows for flexible, out-of-the-box boosting of content (based on combo of any/all of: user profile, date, dimension being browsed and search keyword).
It has a reasonably good admin interface for the administration of boosting/promotion rules for the business user.
The Yellowfin user interface fits seamlessly into our own web software as it too is designed in the latest web technologies making it easy to use and easily accessible to our client base.
The Yellowfin user interface is intuitive and easy to use, elevating VSV clients from needing in-depth training on the product before true value can be realised.
The Yellowfin architecture supports the Pintl architecture 100% due to a similar design strategy and as such no real overhead is added to the Pintl system for the addition of the Yellowfin product nor does it add any additional IT overhead to be used.
The Yellowfin product is quick and simple to develop reports and dashboards in cutting turn-around-time at the VSV development team and when new/custom reports are required by VSV clients.
For the most part, it is quite intuitive, however, you need to have an intermediate knowledge of HTML to be able to construct unique promotional web pages. Nowadays, with WordPress and other content management systems that have WYSIWYG interfaces, Endeca may prove to be challenging to HTML beginners.
The ability to predefine a colour for a specific graph as a selection option dynamically.
The ability to customise the label of a chart, especially with respect to performance related reporting graphs we need an increase in dynamic charting options to meet our more specialised requirements.
If the solution is implemented well and the business understands the purpose of the Endeca stack, it offers a great way for a business to explore and benefit from its existing data. From my experience, the Endeca solution has exposed data patterns to a business that were not thought about or explored before because of the lack of available tools to properly expose these patterns
The system itself is very usable, and with proper training is very sensible in its organization and method of operation. There are some downsides in initial setup in the way things are imported (or not in some cases) in setting up properties and dimensions. Overall however it's amazingly flexible in terms of the content it can index and make available for search.
Yellowfin has large promises that did not meet our expectations after we got it installed. We tried to configure it but things did not go as planned. After 1 year of trying - we still cannot get it working. Be very careful when signing up with them - everything is not what it seems.
Support has been very good, and the trainers for the various Endeca courses have all been very willing to help long after the classes have been completed, so in the instances where we're waiting on support from Oracle, it's often that the members of their training arm can help us out as well.
Anytime I needed a report, I ran into issues with this software. We used Yellowfin for a period of months, having switched from Salesforce. I found the reports were difficult to produce, and the data management was okay at best.
The training is actually really good, and absolutely necessary - although this is software that has great documentation, the documentation itself is so vast, that it would be difficult to learn haphazardly, not to mention being incredibly time consuming to do so. Online training probably would have been fine except for the fact that having someone look over your shoulder to see where you're going wrong is helpful. This also allowed our team to sit in a single room and converse about functionality, etc. that would have been difficult to facilitate via an online class.
We did some online Q&A with the Oracle team, but I would definitely recommend doing an in person class if you have a large team that will be attending - there's definitely no replacements for a large class of technically oriented staff members who can drive conversation about specific topics that might surface.
There were some features we were hoping to get implemented in this particular release of Endeca, but were unable to facilitate those requirements due mostly to timeline. Having seen several other implementations, we will definitely have future iterations to add functionality and improve upon our implementation of Endeca. For the time being, we are satisfied with our implementation as it turned out.
Endeca is brilliant for setting up simple and straightforward search platforms that utilise only basic search rules. On the other hand, Apache Solr supports far more complex search platform implementations, including multi-index search. Overall, I would say Solr is far more powerful than Endeca.
Yellowfin is no doubt, a stronger, more eloquent and polished tool compared to Microsoft's Power BI. The issue with our company specifically is that we are a big Microsoft shop, and pay for Power BI more or less in our bundle esp w/ O365. While the Yellowfin tool is a more sleek tool, the cost to our company is something that we have to weight against a negligible cost with Power BI.
It is a searching tool, and hard to estimate its impact on conversion.
It does its job regarding better searching; In terms of efficiency, it's hard to say: it has big learning curve. It requires a dedicated Endeca developer to work on it.
