X

It's All About the Platform.

  • March 10, 2015

Using The Browser Based Theme Editor

Richard Bingham
Senior Development Manager

Overview

This blog post reviews the new Theme Editor available in Release 9. This
tool allows you to customize the look-and-feel of your Fusion
Applications environment using an easy-to-use browser interface. 

The following embedded video provides a simple functional overview of the Theme Editor available in Release 9. The intended workflow is that all new themes are designed and built in a test environment where validation can be done. Once verified the migration of the theme is done using the Customization Migration feature.



Enabling the Menu

The link
to access the Theme Editor is available under the Navigator menu, under Tools - Customization -
Themes. In order to access this, it is recommended to use the job role
Application Implementation Consultant. As shown below, this inherits the Application Administration duty role (FND_APPLICATION_ADMINISTRATION), which in turn has the Manage Themes privilege (FND_MANAGE_THEMES_PRIV) assigned. Obviously you could setup you own custom security roles with this privilege as you see fit.

In addition, you may find the Theme menu item is still hidden by default. You can enable it using Setup and Maintenance screen, selecting the Manage Menu
Customization
task. From here navigate the tree to the Themes item and edit it. You can either just check the Rendered box, or alternatively (as shown below) you can add Expression Language logic for its conditional display.


Considerations, Tips and Tricks

Unlike Page Composer themes do not require the use of sandboxes since
only one theme can contain all changes and be active at a
time.

Whilst all Desktop pages will have the selected theme applied, there are a few places these do not apply:

  • The Simplified UI - which has its own theme customization.
  • BI Reports and Analytics.
  • The BPM Worklist regions and pages.
  • Other middleware administration consoles, such as OIM and APM.

Customizations made using Page Composer have precedence over
the changes made using Theme Editor. It is therefore recommended to create your theme first, then apply page composer changes on top.

Whilst the branding colors, text styles, and logo images can be changed in a theme, you should use Page Composer to change the application
name.

Skyros is the default skin that forms the base theme upon which to extend. You can then extend an existing theme with a new theme, however be aware that if you make changes to the base theme then they will be inherited.

Whilst you can load branding images using the Theme Editor, the
support for hosting them inside Oracle Webcenter Content server
remains as an alternative, as explained in Note 1605094.1.

Useful Resources

In addition to the links above, the following documents contain more detail on using themes:

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.