Skin form
Completing the Styles tab

Field

Description

If selected, normally indicates that this skins rule and associated CSS text file rules identified in the Desktop, Work, and Report fields were created and maintained by the Branding wizard. (The auto-generated skin rule and CSS text file rules all belong to one RuleSet version and have similar names.)

Clear the checkbox to enable access to these three fields. You can then modify the Desktop, Work, and Report fields, but can no longer copy or update this rule using the Branding wizard. See About the Branding wizard.

Do not clear this checkbox (if checked) if you plan to further modify these CSS styles through the Branding wizard. Any changes to you make through the text tile rule form will be overwritten if you re-run the wizard. Also note that text file rule for a circumstanced skin does not share the base rule's text file.

Optional. Select a text file rule with a name starting with css/desktop_ that defines styles for the Process Commander portal workspaces and navigation panel. Leave blank to use the classic CSS styles for the workspace and navigation panel.

Standard choices include:

The Style Picker list displays only text file rules with desktop_ as a portion of the second key part, but you can reference any text file rule that has webwb as the first key part and css as the final key part here.

This field is disabled if the Auto-generated? option is selected.

You can define a custom CSS for your application desktop and reference it here. As a starting point, download and copy the CSS definitions in desktop_.css (all empty) and carefully modify style definitions. Upload the CSS file into a text file rule in your application RuleSet. By convention, start the second key part of the text file rule with desktop_ (for example desktop_mortgage). Your CSS may introduce additional styles, but do not remove any styles.

Optional. Select a text file rule with a name starting with css/workform that defines styles for the work object forms defined though harness rules, section rules and flow action rules. Leave blank to use the css/workform styles.

This field is disabled if the Auto-generated? option is selected.

These standard choices are available to illustrate the range of possibilities:

Click the magnifying glass icon () to preview the appearance of eligible text file rules with a Style Picker display.

At runtime, the style sheet you reference here appears in HTML code before any custom style sheets or custom styles that are referenced in the Scripts and Styles tab of a harness rule.

The SmartPrompt list displays only text file rules with workform_ as an initial portion of the second key part, but you can reference any text file rule that has webwb as the first key part and css as the final key part here.

Leave blank to use the css/desktop CSS styles for the work object forms. See More about Skin rules.

You can define a custom CSS for your work object forms and reference it here. As a starting point, download the CSS definitions in workform_.css (all empty) and carefully modify style definitions. Upload the CSS file into a text file rule in your application RuleSet. By convention, start the second key part of the text file rule name with workform_ (for example workform_mortgage). WORKFORM OR WORK_FORM?

Your CSS may introduce additional styles, but do not remove any styles. Use the Style Viewer tool and the Style Discovery tool to identify the elements. See also Understanding CSS styles.

Optional. Select a text file rule with a name starting with css/report that defines styles for the Process Commander list view and summary view displays.

This field is disabled if the Auto-generated? option is selected.

Click the magnifying glass icon () to preview the appearance of eligible text file rules with a Style Picker display.

Leave blank to use the default CSS styles(as defined in release 04-02-01 of May 2004) for the report displays.

The SmartPrompt list displays only text file rules with report_ as a portion of the second key part, but you can reference any text file rule that has webwb as the first key part and css as the final key part here.

At runtime for list view reports, the style sheet you reference here appears in HTML code before any custom style sheets or custom styles referenced in the Format tab of a list view rule.

You can define a custom CSS for your reports and reference it here. As a starting point, download the CSS definitions in reports_.css (all empty) and carefully modify style definitions. Upload the CSS file in a text file rule. By convention, start the second key part with reports_ (for example reports_mortgage). Your CSS may introduce additional styles, but do not remove or rename any styles.

Optional. Select a text file rule with a name starting with css/ruleformstyles_zzzzz where _zzzz is arbitrary, that defines styles for the Process Commander rule forms produced by the Form Builder. GAGNP 5.1 4/7/06

You can define a custom CSS for your rule forms and reference it here. As a starting point, download the CSS definitions in ruleformstyles.css (which is a Final rule) and carefully modify style definitions. Upload the resulting CSS file in a text file rule. By convention, start the second key part with ruleformstyles_ (for example ruleformstyles_gaudy).

This field does not control styles of harness-based rule forms. For harness-based rule forms, the Scripts and Styles tab identifies the style sheet, normally css/workform_ruleform. 5.5

Do not attempt to remove capabilities from rule forms by making the styles not visible to developers. This approach may interfere with proper operation of the rule form, or affect multiple rule forms in unexpected ways.