Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Portal rules - Completing the Skins tab

Updated on March 28, 2008

 This presentation is part of the Portals Overview Self-Study Course.


The Skins tab allows the user to select the portal type and an associated skin rule.  Skins are a collection of styles sheets defined by a skin rule.

The Type field allows you to choose the type of portal you are creating.  The User type is a much lighter portal than the Developer type.  The style sheet files and JavaScript files for the User type require substantially less memory on the user workstation than is required by the Developer setting.

The Developer type is used in version 5 systems and allows you to customize the style sheets and menus of the standard Developer portal.  When you select “Developer” as the type, the “Tabs” and “Custom” tabs of this form are not used.

The Classic type allows the user to utilize the 4.2 legacy portal or other older portal rules.  This choice remains available for backwards compatibility.

The Skin field defines a specific set of CSS style sheets for work object forms, report displays, and portal elements.  The values populating this field are instances of the Rule-PortalSkin class.

Developers may add new Rule-PortalSkin instances and within those, create new CSS files in the Rule-File-Text class.  Remember, these style sheets define the appearance of the portal.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us