Skins are a way to provide branding and navigation for Self Service. The skin provides the entire HTML surrounding the current view.
Skins use a
SkinDefintionitem descriptor to provide the data for theindex.jsppageThe
index.jsppage uses thestyleattribute as the name of aSelfServiceSiteOptionthat is included in the<head>sectionThe
index.jsppage uses thejavascriptattribute as the name of aSelfServiceSiteOptionthat is included in the<head>sectionThe
index.jsppage uses thelayoutUrlattribute to include the skin in the<body>section. ThelayoutUrlis included using a<dsp:include>tagThe skin may define additional options using the
additionalOptionsattribute. The Skin Settings page in Service Administration uses thehintattribute of theSelfServiceSiteOptionto determine which editor to place in the page. Valid values forhintare:null,int,string,longstring, andBooleanThe skin JSP page should include the
view.jsppage to render the actual viewThe skin needs to provide navigation for the application. The skin should have access to an object that lists all the currently available views
The skin author is responsible for providing the JSP page to be rendered, defining the SkinDefinition instance in the repository, and setting up the SelfServiceSiteOptions in the repository. The skin author must create at least a SelfServiceSiteOption for style and a SelfServiceSiteOption for javascript, even if the default value is empty. The skin author can define additional options that are used by the skin and these should be created in the repository.
Authoring a skin is a developer task. Configuring the SelfServiceSiteOptions for a skin should be done in the Service Administration > Skin Settings page.
