Harness form
Completing the Scripts and Styles tab

Field

Description

js — Identify the text file rule for JavaScript references.

bundle — Identify a static content bundle rule references.

Enter the File Name and File Type key parts of a text file rule that contains source text for JavaScript scripts referenced in the HTML of this harness, separated by a period. The system assumes webwb is the first key part. A script file can use any scripting language supported by the user browsers such as VBScript (for Internet Explorer) or JavaScript.

For example, enter mortgage.js to reference a script file named navigation.js, stored in the text file rule named webwb.mortgage.js.

You can enter more than one script file reference. Order is significant.

To reorder the rows of this array, hold the mouse pointer over a number. Click and drag to another row. To duplicate or move a row, hold the mouse pointer over a number. Or, right-click to access a context menu with Cut, Copy, and Insert options.

Script Bundles

Enter the Bundle Name and Bundle Type key parts of a static content bundle rule. See About Static Content Bundle rules.

You can enter more than one static content bundle reference. Order is significant. Reorder the rows in this array using the mouse pointer or right-click menu.

As a best practice, leave this array blank and apply styles through a Skin rule. Using a Skin rule ensures that the styles apply uniformly to all work item harnesses throughout your application.

You can add the styles to the Skin rule, which auto-generates the CSS, and makes it easier to maintain and upgrade. Alternatively, you can include additional style sheets on the CSS tab of the Skin rule. However, the recommended approach is to add the styles directly to the Skin rule.

By default, many styles referenced in harness forms are defined in a standard text file rule named webwb.workform.css. An empty style sheet (containing many style definitions as comments) is named webwb.user_work_form.css. You can override the webwb.user_work_form.css text file rule with another containing style definitions of your own design, being careful to retain the same style names as the standard. Values you enter in this field affect the appearance of only this harness.

To apply a set of custom styles to all harnesses associated with an application, use a skin rule, associated with a portal rule. See About Skin rules and About Portal rules.

This array provides for backwards compatibility with versions before V5.4.

Applying V6.2 styles to screen flow harnesses

The V6.2 case manager and case worker portals (pyCaseManager and pyCaseWorker) and standard V6.2 user form harnesses use the EndUser62 skin and styles. However, the standard V6.2 screen flow harnesses including Work-.PerformScreenFlow, Work-.TabbedScreenFlow, and Work-.TreeNavigation do not, by default, use these styles.

To keep the user interface styles consistent, copy the screen flow harnesses to your application RuleSet and select the standard CSS text file pyScreenFlow_EndUser62 in this Style field. In the Start shape properties panel for each screen flow used by your process, specify your harness in the Harness field.

If you modify the EndUser62 Skin rule, you can reflect those changes in your screen flows by copying the CSS file pyScreenFlow_EndUser62 to your application RuleSet and manually modifying the file's contents. If you change the application skin from EndUser62, remove pyScreenFlow_EndUser62 from this field.

Text and verify the results, as some styles may have been removed unintentionally. Also, if you intend to enable this harness throughout the application, the system produces for every harness a unique style sheet that is generated and downloaded individually. In this case, it is preferable to download all of the styles once, even if they are not all used.