- About
- New
<li class="current><a href="skins.htm">Skins</a></li>
<li><a href="tabs.htm">Tabs</a></li>
<li><a href="spaces.htm">Spaces</a></li>
<li><a href="custom.htm">Custom</a></li>
<li><a href="options.htm">Options</a></li>
<li><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></li>
<li class="nottab"><a href="related.htm">More...</a></li>
</ol>
</td></tr>
</table>
</table>
<div class="INNER2">
<p>Use this array to identify a skin — a collection of styles
defined by a skin rule — and other presentation styles for this
portal.</p>
<p class="tippara"><img src="../../shared/tipstar.gif" alt="Tip" width=
"10" height="16" align="absmiddle" />As a best practice for new
applications, create <a href=
"../../definitions/c/compositeportal.htm">composite portals</a> for users
and managers, or copy and evolve the standard sample composite portals
<cite>User</cite> and <cite>Manager</cite>. See <a href="../../basics/portal/userPortalsAbout/aboutCompositePortals.htm">About composite portals</a>.</p>
<p>The combination of selections for the <strong>Role</strong> and <strong>Type</strong> fields determines what other tabs are available in the rule form.</p>
<table class="table1" border="1">
<tr valign="top">
<td align="left" valign="top" width="83">
<h2>Field</h2>
</td>
<td valign="top" width="401">
<h2>Description</h2>
</td>
</tr>
<tr>
<td align="left" valign="top"><p><strong>Role</strong></p></td>
<td>
<p>Select:</p>
<ul>
<li><code>User</code> — to indicate that this portal
rule supports application users who do not update rules.
The style sheet and JavaScript files for this choice
require substantially less memory on the user workstation
<code>Developer</code> setting. </li>
<li><code>Developer — </code> to provide portal capabilities used by developers or business analysts. While most aspects of the Designer Studio
are fixed, you can customize styles.
<span class="afield"> Skins</span>, <span class="afield"><a href="custom.htm">Custom</a></span>, <span class="afield"><a href="options.htm">Options</a></span>, and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available.</li>
</ul>
<p>For details about the effect of changes in this setting,
see <a href="../rule-portalskin/related.htm">More about Skin
rules</a>.</p></td>
</tr>
<tr>
<td align="left" valign="top"><p><strong>Type</strong></p></td>
<td align="left" valign="top"><p>Select a type.
The default type is <code>Composite</code>, which provides the most flexibility in development and the greatest support for localization and accessibility. See <a href="../../basics/portal/userPortalsAbout/aboutCompositePortals.htm">About composite portals</a>.</p>
<p>The available options depend on what is selected for the <strong>Role</strong> field.</p>
<ul>
<li>For the User role:
<p><code>Fixed</code> specifies a <a href="../../basics/portal/userPortalsAbout/aboutTraditionalPortals.htm">traditional</a> (V5.1+) portal. The <span class="afield">Skins</span>, <span class="afield"><a href="tabs.htm">Tabs</a></span>, <span class="afield"><a href="custom.htm">Custom</a></span>, <span class="afield"><a href="options.htm">Options</a></span>, and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available.</p>
<p><code>Composite</code> specifies a composite (V5.5+) portal. The <span class="afield">Skins</span>, <span class="afield"><a href="options.htm">Spaces</a></span>, and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available.</p>
<p><code>Custom</code> specifies a custom portal. Specify this when you want to use an activity to provide the capabilities you want to offer to users associated with this portal rule. The <span class="afield">Skins</span> and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available. Use the <strong>Activity</strong> field on the <span class="afield">Skins</span> tab to specify the activity.</p>
</li>
<li>For the Developer role:
<p><code>Classic</code> provides the older Version 4.2 legacy standard development portal. This choice remains for backwards compatibility but is not recommended for new portal rules.</p>
<p><code>Composite</code> specifies a composite (V5.5+) portal. The <span class="afield">Skins</span>, <span class="afield"><a href="options.htm">Spaces</a></span>, and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available.</p>
<p><code>Fixed</code> specifies a traditional (V5.1+)portal. The <span class="afield">Skins</span>, <span class="afield"><a href="custom.htm">Custom</a></span>, <span class="afield"><a href="options.htm">Options</a></span>, and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available.</p>
<p><code>Custom</code> specifies a custom portal. Use an activity to provide the capabilities you want to offer to users associated with this portal rule. The <span class="afield">Skins</span> and <span class="afield"><a href="../../basics/v6portal/v6completingrulehistory.htm">History</a></span> tabs are available. Use the <strong>Activity</strong> field on the <span class="afield">Skins</span> tab to specify the activity.</p>
</li>
</ul>
</td>
</tr>
<tr>
<td align="left" valign="top"><p><strong>Skin</strong></p></td>
<td>
<p>Select a skin rule to define CSS styles for work object
forms, report displays, and portal elements. <em>LAYOUT field
removed MARTT 11/3/05 B-16271 GAGNP 3/6/06 METAL now works with
Developer in SP6 </em><tt>B-20131 validation</tt></p>
<p>If you selected <code>User</code> in the
<strong>Role</strong> field, select <cite>User</cite>,
<cite>Classic</cite>, or a custom skin rule developed with the
Branding wizard. See <a href=
"../../tools/applicationskin/aboutapplicationskin.htm">About the
Branding wizard</a>.</p>
<p>The standard skin <cite>Developer</cite> is reserved for the standard <cite>Developer</cite> portal rule, which defines the Designer Studio.</p>
<p>The standard skin <cite>BusinessAnalyst</cite> is reserved for the standard <cite>BusinessAnalyst</cite> portal rule, which defines the Business Analyst portal.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><strong>Activity</strong></td>
<td><p><img src="../../shared/advanced.gif" alt="Advanced feature" width="16" height="16" />If you select <code>Custom</code> as the <strong>Type</strong>, an <strong>Activity</strong> field and a <span class="kbd2">params</span> button appear. Specify or create the activity that provides the capabilities you want to offer to users associated with this portal rule.</p>
<p> After you have selected the activity, click the <span class="kbd2">params</span> button. Enter appropriate values for each activity parameter.</p></td>
</tr>
</table>
<p><a href="main.htm" class="small"><img src="../../navdropup.gif" class="inline" alt="Up" /> About Portal rules</a></p>
</div>
</body>
</html>
|
Portal form