Harness form -

Create a harness by clicking Create > User Interface > Harness in Dev Studio.

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Note: When generating a harness, HTML Fragments that do not already exist in a core ruleset cannot be directly referenced with a generated JavaServer Pages (JSP) tag. Instead, an error displays and the harness does not generate. To address this issue, create a stub for the HTML Fragment in a core ruleset.

> Key parts:

Field Description

Field	Description
Apply to	Select a class that this harness applies to. In most cases, select the name of the class which contains the work items that the harness supports. Choose the class that is most specific to the application and its work items, rather than a general Work- class. Typically the class you specify in this field is derived from the Work- base class. In special cases, a harness can apply to a class derived from the Assign- base class.
Identifier	Enter a name for this harness. If this rule is to override a standard rule, choose: `AutoClose` — An empty harness that closes automatically. An alternative to `Confirm`, for use in those flow actions that do not require users to see (and dismiss) a confirmation form. `Confirm` — To display the results, including the work item ID, of an update. `New` — To create a work item. (You can choose a value other than `New` if desired; identify the harness in the Harness for work item creation field on the Process tab of the Flow form.) `NewCovered` — To create a work item that is associated with an existing cover work item. `Perform` — To update and possibly complete an assignment. `Reopen` — To allow a resolved work item to be reopened. `Review` — To review a work item and assignment without the ability to update. Begin the name with a letter and use only letters, numbers, the ampersand character, and hyphens to form a Java identifier. See How to enter a Java identifier.

Apply to

Select a class that this harness applies to. In most cases, select the name of the class which contains the work items that the harness supports. Choose the class that is most specific to the application and its work items, rather than a general Work- class.

Typically the class you specify in this field is derived from the Work- base class. In special cases, a harness can apply to a class derived from the Assign- base class.

Identifier

Enter a name for this harness. If this rule is to override a standard rule, choose:

AutoClose — An empty harness that closes automatically. An alternative to Confirm, for use in those flow actions that do not require users to see (and dismiss) a confirmation form.
Confirm — To display the results, including the work item ID, of an update.
New — To create a work item. (You can choose a value other than New if desired; identify the harness in the Harness for work item creation field on the Process tab of the Flow form.)
NewCovered — To create a work item that is associated with an existing cover work item.
Perform — To update and possibly complete an assignment.
Reopen — To allow a resolved work item to be reopened.
Review — To review a work item and assignment without the ability to update.

Begin the name with a letter and use only letters, numbers, the ampersand character, and hyphens to form a Java identifier. See How to enter a Java identifier.

Note: When completing the Add to ruleset field, you cannot add a harness to a component ruleset.

Additional creation options

Field	Description
Template	Select a template rule to copy for the harness and mark the new rule as JSR 168 compliant. Specify `PortletHarness` to create a harness that uses portlet-compliant HTML and can be displayed in a portlet window on a portal server through Service Portlet rules. Note: The rule type Service Portlet is deprecated. Use Pega Web Mashup instead.

Rule resolution