skin on on CRM

By using skins, you can adjust the visual layout of the user interface (UI) to fit your corporate

identity.

You can change the visual layout of the CRM WebClient UI using the

Skin dropdown list

located under

Personalize 􀄺 Personalize Layout in the navigation frame.

SAP CRM 7.0 comes with the following standard skins:

􀁸

Signature Design (SAP standard design)

􀁸

Default

􀁸

Serenity

􀁸

New Hope

􀁸

High Contrast (suitable for users with visual impairments)

As of SAP CRM 7.0, a workbench is provided in Customizing for manipulating and copying

SAP standard skins.

Skinning also allows you to create your own skin modifications. For example, you may want

to adapt a skin in the following ways:

􀁸

Create a dfferent visualization of mandatory fields

􀁸

Follow your company’s branding in regard to color schemes

􀁸 Embed a company-specific logo


*********************

1.1 Skins Overview

The general purpose of skins is to provide the following:

􀁸

Styles that can change from skin to skin (for example, background colors) and that

customers are likely to change

􀁸

A variety of styles that are valid for as many purposes as possible for each

usage (such as different browsers, base directions (RTL or LTR), or visual effects)

􀁸

Reduced need for CSS hacks to tackle browser differences

The standard skins are stored in the MIME repository of BSP application THTMLB_STYLES.

Depending on the skin, the files are automatically uploaded by the

thtmlb:content tag.

A skin consists of a number of style sheets. Style sheets contain CSS styles. The CSS style

definitions of one style sheet can be overwritten (completely or in parts) by a new definition in

a style sheet that is higher up in the hierarchy. Note that in the figure below, “higher” does not

necessarily mean higher visually.

For example, a definition for class

th-inp in thtmlb_core_stand.css can be

overwritten by a definition for class th-inp in thtmlb_stand.cs


**********************************************