Back Forward About Harnesses
 

User Interface category
  1. About 
  2. New 
  3. Layout 
  4. Scripts and Styles 
  5. Pages & Classes 
  6. HTML 
  1. Display Options 
  2. History 
  3. More... 

Purpose

Use harnesses to define the appearance and processing of user forms used in your application to create work items and process assignments.

PRPC includes more than a dozen standard harness forms for entering, reviewing, updating, and processing work items and assignments. Your application can override the standard rules to extend and tailor them to specific needs.

NoteBefore creating or editing harness, section or flow action forms, set the Skin preference (in the Run Process area of the General Preferences group) to the skin that application users are expected to use. This provides the closest approximation during development of the runtime look and feel of the form.

NoteYou can use harnesses to define composite portals, as well as user forms. For this advanced special use, see How to create a composite portal.

Controls

On the Layout tab, each harness references one or more sections that define the runtime presentation of the work item. You can directly edit these sections in the Harness form, using these controls and layouts. (When you save the harness, the updated sections are also saved.)

</

Layout

AccordionColumn RepeatContainerDynamic ContainerLayout
 Panel SetRow RepeatSectionTabTabbed
Repeat
 TreeTreeGridGrid

Basic

ButtonCheck boxCalendarIconImage
 Input BoxLabelRadio ButtonsTextAreaSelect
URL  

Advanced

AutoCompleteChartData FieldDynamic SelectList to List
 Menu BarParagraphSmart Label  

Applications without user forms

Work object forms defined by harnesses are typical, but not required, elements of a PRPC application. Some business process management applications use an external portal or external system and call PRPC services to create work items, advance them through a flow, perform flow actions, and so on. The Process Engine API is a collection of standard activities that apply to the Work- base class to support such headless applications.

Where referenced

Each flow rule that creates a new work item identifies a harness to capture initial information about that work item.

Standard activities that apply to the Work- class look (using rule resolution) for harnesses with specific names, such as New, Perform, and Review. To display a user form defined by a harness, call the standard @baseclass.Show-Harness activity in your activity.

Action section

Harnesses that allow users to select from multiple flow actions (often called Perform harnesses) contain an action section. See Presenting flow actions.

User interaction with user forms

For basic information about using user forms defined by harnesses from an application user perspective, see Working with user forms (V5X) and Working with user forms (V6).

Rule forms

Advanced featureSome rule forms are defined through harness and sections. This capability is reserved.

Access

Use the Application Explorer to access the harnesses that apply to the work types in your application. Use the Rules Explorer to list all the harnesses available to you.

Category

Harnesses are instances of the Rule-HTML-Harness class. They are part of the User Interface category

How to unit test a harness

Related topicsHow to support work item copying
How to support work item printing
User interface   — Concepts and terms
Standard rulesAtlas — Standard Harnesses

User Interface category
Help System home pageHelp Home