Anytime an embedded BI vendor claims to be white label, it behooves us to ask to what extent.
White label, like embedded (which we unpack in this infographic), is one of those industry terms that means different things to different people. By definition, it’s the process of stripping away all of the manufacturer’s branding so that those companies licensed to use the software may rebrand it as their own—but for us, it’s more than that.
At Exago, white labeling is less about swapping logos and more about making the application look, feel, and behave like an extension of its host. We don’t just want to blend in, we want to pass as part of the original; and passing often means more than a few CSS changes. Exago BI can be white labeled in not one, not two, but five different ways.
Let us walk you through the transformation.
This is what Exago BI’s Advanced Report Designer looks like by default.
All UI elements are either in grey or in our one accent color, blue. All text elements use our out-of-box American English text, and all database schema information (object and field names) appear exactly as they exist in the database. Reports may be styled using out-of-box report themes, and the application takes up 100% of the browser window.
This is an example of a fully white labeled instance of Exago BI embedded into a fictitious application called Vision.
1. UI Theming and Branding
This is what most people think of when they think of white labeling. Easily re-skin the UI by making changes to our open CSS files and swapping out-of-box icons for your own. Application themes, which allow you to assign a UI theme to a user or group of users, are also available as of 2016.3 with a dark theme slated for release later this year!
2. Integration and Embedding
The host application architects can dictate how much screen real estate to allocate to Exago BI on which pages and how users will access the reporting suite. In the example above, the entire Exago UI is displayed between Vision’s navigation bar and footer. Exago could also be displayed in part, if desired, showing only a dashboard or a design tool rather than the entire UI; and it can appear multiple times on a single page.
Applications with international users can translate virtually any UI text element into the local language on the fly based on user login credentials. All of the UI’s text (on buttons, tabs, etc.) can be edited dynamically using our language files. It is also possible to have static report text (such as column headers) and database schema information (such as data object and field names) appear in the local language.
4. Report Theming and Branding
This example shows a Vision-branded report utilizing a custom chart theme built using Exago’s theme maker. If desired, the report designer could also use the logo function to dynamically insert his or her company’s logo into the report. Lastly, instead of using Exago BI’s default filter dialog windows, Vision’s admins could design custom prompting filter dialogs instead.
5. Custom Static Pages
Last but not least, static pages like the Getting Started Page and the tooltip displayed here can be edited and localized like the other language elements on the page. Exago BI’s context-sensitive help, accessible via the question mark icon in the upper right-hand corner of the window, can also be edited and translated as needed.