PeopleTools provides branding features that are powerful and flexible, allowing you to manage the look and feel of any PeopleSoft application.
With PeopleTools, many common branding tasks, including managing definitions and objects associated with the overall site style are performed online. In addition, other tasks such as maintaining style sheets, images, and other objects can be performed either online or by using Application Designer.
With PeopleTools branding, you can apply branding definitions to:
- The entire system.
- Individual portals.
- Users by role or permission list.
- Individual classic components.
- Fluid components by node.
The key branding definition is the theme, which can be applied system wide, to specific portals, and by specific user attributes. A theme definition includes:
- Homepage header, footer (optional), and target page header (optional).
- Theme macro set (optional).
- Default theme style sheet for classic components (optional) if necessary to override the style sheet of the theme family.
- List of additional skins for classic components (optional).
- Mapped theme style sheets for fluid components by node (optional).
- Global theme style sheet for fluid components if necessary to override the style sheet of the theme family (optional).
At the system level, branding settings include:
- Selection of the default theme family (which includes the default theme and compatible default style sheet for classic components)
- Selection of a navigation collection for custom homepage tabs (optional).
- Additional style sheets and JavaScript objects for all classic components (optional).
- A default style sheet for all fluid components (optional).
- The branding framework application package and class.
At the portal registry level, additional settings can be specified, some of which override the system settings:
- Default theme.
- Default skin style sheet (optional).
- Default custom tabs collection (optional).
- Default custom homepage tab (optional).
- Default fluid homepage (optional).
At the user attribute level, additional settings can be specified, some of which override the system settings and the portal registry settings:
- Theme.
- Skin style sheet (optional).
- Custom tabs collection (optional).
- Default custom homepage tab (optional).
- Default fluid homepage (optional).
In addition to these system, portal, and user attribute settings, different branding can be applied to individual classic components.
In Application Designer, the component’s developer can specify style sheets and JavaScript objects as component properties. Through the browser, the portal administrator can specify additional custom style sheets and JavaScript objects as component properties. (These capabilities are in addition to existing features in Application Designer that allow the component’s developer to apply a style sheet to each page definition, and to apply style classes to fields and field labels.)
Source: Oracle
