Complete these two optional arrays to supplement or override the standard client JavaScript scripts that support the harness form, and to supplement or override the standard Cascading Style Sheet style definitions that support the harness form.
Note: As a best practice, apply styles through a Skin rule instead. Using a Skin rule ensures that the styles apply uniformly to all work item harnesses throughout your application. You can add styles to the Skin rule, which auto-generates the CSS, and makes it easier to maintain and upgrade.
If you choose to apply styles on this tab, rather than in the skin, reference the second and third key parts of a text file rule in each array. Order is significant; the scripts and styles in files you reference on this tab have precedence over those inserted automatically.
When you save the harness form, Pega Platform generates HTML that contains <pega:include > JSP tags, to cause stream processing to reference the text file rules. In the sections referenced by this harness, you can create HTML text that references the custom styles or scripts.
For harnesses, unlike sections or flow actions, HTML code is always automatically generated; you cannot edit it.
Field |
Description |
| Type |
Optional. Select one of the following to indicate the type of script reference you want to use:
|
| Name |
If you selected a js script type:
If you selected a script bundle:
|
Click the Add a row icon to add additional scripts.
| File Name |
Press the down arrow to select a text file rule that contains source text for cascading style sheets (CSS) referenced in the HTML code of this harness. Order is significant; the bottom style sheet is applied last. Note: As a best practice, leave this 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 styles to the Skin rule, which auto-generates the CSS, and makes it easier to maintain and upgrade. 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. Applying PRPC Version 6.2 styles to screen flow harnessesThe PRPC Version 6.2 case manager and case worker portals (pyCaseManager and pyCaseWorker), and standard user form harnesses use the EndUser62 skin and styles. However, the standard Version 6.2 screen flow harnesses, including Work-.PerformScreenFlow, Work-.TabbedScreenFlow, and Work-.TreeNavigation do not use these styles by default. To keep the user interface styles consistent, copy the screen flow harnesses to your application ruleset and select the standard CSS text file If you modify the EndUser62 Skin rule, you can reflect those changes in your screen flows by copying the CSS file |
| Generate harness specific CSS |
Displays when a style sheet is selected in the Style Sheets File Name field. This option is intended to enhance performance when using custom styles. When selected, the system generates the style sheet based on the CSS selectors used by this harness; all the unused selectors are filtered out to reduce the file size. The generated CSS is not shared with other harnesses. Caution: Verify the results, as some styles may have been removed unintentionally. Also, if you intend to enable this harness throughout the application, note that 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. |
Click the Add a row icon to add additional style sheets.
If you leave the Scripts and Style Sheets area blank, the resulting HTML code references the JavaScript functions and CSS styles produced by the standard HTML Fragment named WorkFormStandard, which includes other HTML Fragments that include standard text file rules: