Explore Yellowfin now with our sample datasetGet Started
By default, Yellowfin operates as a stand-alone web application. However many clients choose to embed or integrate Yellowfin into their application, website or portal. Yellowfin offers a variety of rich capabilities to support the specific style of integration that is required.
Broadly, there are two main methods for integrating Yellowfin:
Integration methods can be mixed together to achieve the optimal user outcome for the amount of integration effort.
Combined with Yellowfins’ extensive white-labelling features, both methods allow for Yellowfin capabilities to be seamlessly integrated into your target application.
Software companies can embed Yellowfin using one of the methods described below in order to bring valuable reporting and analytic capabilities to their users. Yellowfin provides for fine-grained control over which capabilities are made available – from individual content items such as a chart, through to the entire Yellowfin application.
How you choose to embed is based on the user experience you want to create. If you are simply augmenting an existing workflow you may want to bring in analytic content. For example, embedding a dashboard into an enterprise portal or placing charts within your application workflow.
If on the other hand, you want to allow users to create reports via self-service then you will want to embed the entire application.
In this approach, you embed individual content items, such as reports and dashboards, from the Yellowfin application for display on your own.
Content integration offers you the ability to display Yellowfin content geared for consumption(as opposed to creation) in a standalone fashion, often tightly integrated with the rest of your application’s workflow.
This can range from one small chart on its own on a page primarily dedicated to an activity stream, through to a fully interactive dashboard.
Individual content items can also be integrated using the iFrame method and using custom URL links to land on that specific content.
Any type of reports visualization (tables, charts, report canvas) and any type of Dashboard (predefined layout or canvas) can be integrated.
By default all reports and dashboards will require a user to be authenticated, ensuring that their data security and users preferences are inherited. However, by enabling guest users it is possible to allow insecure access to content as well.
In addition to the primary report and dashboard loading calls, Yellowfin also offers several supplemental calls and APIs, to allow custom interaction between your application and the Yellowfin report:
In this approach you provide your users with direct access to the Yellowfin application, offering some or all of the rich experience and features contained. For a seamless integration, we can limit the Yellowfin components displayed and re-style the application to feel like it belongs in the broader UX.
Application integration is the favored approach when you wish to offer your users some of the interactivity features that can only be accessed through the application including:
Application integration is typically done via one of two approaches:
In this approach, which is generally the easiest of all options to implement, you route your users directly into the Yellowfin application. To maintain a consistent feel with the rest of your portal or software, you may want to restyle the application <see restyling>. At the simplest, this might consist of swapping the Yellowfin logos and possibly changing core element colors.
More advanced implementations may use custom headers <link to wiki> to control user navigation, both within the Yellowfin Application and between YF and your application.
In this approach, you embed the Yellowfin application within your own portal, inside of an iFrame. The Yellowfin header is often disabled in favor of your own application’s header. This approach also tends to be easier than redirection when implementing custom navigation.
By using a combination of re-styling and application integration options you can make Yellowfin feel like a seamless extension of your application.
It is possible to choose the components that you want to embed into your application. Either via functional access or managing distinct URLs you can precisely tailor the components you deploy in your application.
Every component of the Yellowfin application is accessible by itself, either as a distinct URL or through entry parameters. When this feature is combined with the ability to limit user navigation within the application (also through entry params), we are able to embed components of the application individually.
As an example, you may create a link on your application that takes a user directly to the Report Builder. Because standard Yellowfin navigation has been disabled, once the user is finished creating a report, they are forced to interact with your application to move to their next destination, which may not include Yellowfin.
To aid in custom navigation, Yellowfin provides several Administrative Web Service <link> calls that allow you to obtain content ids and locations programmatically.
Like the standard Yellowfin application, access to functionality is primarily controlled by a user’s role permissions. With distinct user roles, you are able to offer any experience you desire in application integration from a full system administrator, to an ad-hoc report builder, to a simple consumer who only has the ability to see one dashboard.
Insights provided by a BI tool mean little if no action is taken upon them. Yellowfin code mode offers the ability to drive that action facilitating a user’s day to day workflow. There are a number of ways that you can include actions in your dashboards, these include:
Yellowfin can be silently installed behind a third-party installation process. This allows Yellowfin to be installed without the end-user knowing that it is being installed. This may be required when Yellowfin is used as an analytics module inside another product. The parent installation process can prompt the end-user for required parameters in its own interface, before passing installation parameters to the Yellowfin installer via a properties file.
The silent installer can also be used for automatically provisioning Yellowfin in DevOps processes, such as automatic installation in a Docker container.
The Yellowfin application can be upgraded in a silent mode. This allows Yellowfin to be upgraded as part of a parent application’s upgrade process, or via scripted Dev Ops processes.