Much like the Login Page, customisation of the standard Yellowfin Header & Footer can be performed two ways:
- Simple - this involves the replacement of images, and changes to the CSS files used by the header and/or footer, without having to write a panel. Generally this option is used for quick 'mock ups' but not the final restyled product.
- Complete - this involves writing a custom file to replace the header and/or footer panel. This method requires more technical knowledge, and more time.
The Yellowfin header sits at the top of each page in the system:
The footer is located at the bottom of the page, and is centred on the Dashboard if the dashboard position is set to Centre:
Dashboard footers were available in Yellowfin 8, then suspended in Yellowfin 9.0. They were reinstated in Yellowfin 9.6. To enable or re-enable footers, update the new system dashboard setting for footers, under Display Settings. If you had previously configured a custom footer in an earlier version of Yellowfin, re-enabling this setting will re-enable your old custom footer for all dashboards.
Yellowfin\appserver\webapps\ROOT\customimages) with your customised versions:
You will need to clear your browser cache once replacing these images in order for them to appear.
Note: the images you wish to use as replacements will need to have the same name and extension as the files listed above in order for the page to pick them up. You no longer have to overwrite the originals, simply place your new images in the custom directory. This will mean that they will not be overwritten during the upgrade process.
* You will notice that the text in the footer references Yellowfin; if you wish to remove or customise this, you must use Complete Styling.
The included HTML should be a fragment, suitable for including inline within another HTML page, rather than it being a full HTML document itself. That is, it should NOT contain <HTML>, <HEAD>, or <BODY> tags. Remember that any links inside the HTML will be relative to the Yellowfin page. It is recommended to use absolute HTML links.
It is also important to remember that the standard Yellowfin Header provides only one link for a user to log out of the system. If the header is being replaced and you wish to provide this link, include:
There is also a sample header file available as a starting point in the Yellowfin Examples directory (
- Save your custom Header & Footer files in the Yellowfin ROOT directory (
- Save any required images in the Yellowfin customimages directory (
- Update any CSS files used, or add new ones to the Yellowfin customcss directory (
- In Yellowfin, navigate to Administration > Configuration > Integration (tab)
Here you will need to specify the locations of your custom files, for example:
- Change the Page Header option from Standard Yellowfin Header to Custom Header and specify the URL of the file.
- Change the Page Footer option from Standard Yellowfin Footer to Custom Footer and specify the URL of the file.
The Custom URL is a link to the html fragment that will be included at runtime every time a page is loaded. It can be located on any server that the Yellowfin service can access, but for best performance it would be hosted on the same server. In this example we have placed the file in the Yellowfin ROOT directory (
Yellowfin\appserver\webapps\ROOT\header.jsp and can then be found via
Note: Instead of using the existing Yellowfin directories, you may wish to create a new folder in
Yellowfin\appserver\webapps\ROOT to contain your custom files, to make locating them easier.