Customizing Cascading Style Sheets

In Planning, cascading style sheets help define user interface (UI) themes, which control the appearance of Planning. You can customize a Planning cascading style sheet to meet your needs. Some common style sheet customizations include:

Before customizing cascading style sheets, ensure that you have basic knowledge of cascading style sheets and are familiar with style sheet editor tools. Some settings are necessary for displaying portions of the product.

Changes to cascading style sheets are made on the Web application server, so they affect all connected users. Style sheets are not located in a default directory, rather the Web application server extracts the files to a temporary location at runtime. For information on where to find these files on the Web application server, see Location of Cascading Style Sheet Files.

Planning primarily uses two cascading style sheets: a global sheet that defines Web UI elements common to multiple Oracle products, and one specific to Planning. The global cascading style sheet is called global.css. This table lists the major sections in the global.css file, and shows the sections that Oracle strongly recommends against customizing.

Table 80. Major Sections in the global.css File

Customizable Sections

Sections Not Recommended for Customizing

Non-Navigation Styles

Tadpole Menubar

Tadpole Menuitem

Menu Styles (order is important)

Tadpole Masthead

Tadpole Minimized Masthead

Tadpole Content Area

Tadpole Toolbar

Tadpole Logon Styles

Tadpole Viewpane

Tabs

Tab Anchor Tags

Tab Body

Tadpole Tree

TaskTabs

Task Tab Body

 

Groupbox

Groupbox Anchor Tabs

 

Buttons

When Drawing Buttons in HTML

When Using Button Tag

When Using Input Tag

 

  To customize a cascading style sheet:

  1. Extract the HyperionPlanning.ear file and then the HyperionPlanning.war file to a temporary location.

    See Location of Cascading Style Sheet Files.

  2. Locate the HspCustom.css file (under the custom directory in the temporary location where the HyperionPlanning.war was extracted).

  3. Customize HspCustom.css and save it to HyperionPlanning.ear.

  4. You must redeploy for the changes to be picked up.

All Planning Web pages refer to the HspCustom.css file, and settings made here override those in global.css and planning.css.

To customize styles in data forms to reflect members’ hierarchical positions within the row or column axis, see Customizing the Style of Row and Column Members in Data Forms.