About Harness rules
|
|
| New | Layout | Scripts and Styles | Pages & Classes |
| HTML | Display Options | History | More... |
C-451 Use harness rules to define the appearance and processing of work object forms used in your application to create work objects and process assignments.
Process Commander includes more than a dozen standard harness forms for entering, reviewing, updating, and processing work objects and assignments. Your application can override the standard rules to extend and tailor them to specific needs.
Before 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.
You can use harness rules
to define composite portals, as well as work object forms. For
this advanced special use, see How to create a
composite portal. GRP-378
On the Layout tab, each harness rule references one or more section rules that define the runtime presentation of the work object. You can directly edit these section rules in the Harness form, using these controls and layouts. (When you save the harness rule, the updated section rules are also saved.)
Layout |
|
Column Repeat | 
|
|
|
| Row Repeat | 
|
|
Tabbed Repeat |
||
| Tree | TreeGrid | Grid | |||
Basic |
|
|
|
|
|
|
|
|
|
|
|
|
|||||
Advanced |
|
|
|
|
|
|
|
|
|
|
|
Work object forms defined by harness rules are typical, but not required, elements of a Process Commander application. Some business process management applications use an external portal or external system and call Process Commander services to create work objects, 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. C-2467C-1975
Each flow rule that creates a new work object identifies a harness rule to capture initial information about that work object.
Standard activities that apply to the Work- class look
(using rule resolution) for harness rules with specific names, such as
New, Perform, and Review. To
display a work object form defined by a harness rule, call the standard
@baseclass.Show-Harness activity in your activity.
Harness rules that allow users to select from multiple flow actions (often called Perform harness rules) contain an action section. See Presenting flow actions.
For basic information about using work object forms defined by harness rules from an application user perspective, see Using work object forms.
Beginning with V5.5, a few rule forms are
defined through harness and section rules. This capability is reserved.
If your application includes custom rule types, use the Form Builder tool, not harness rules, to define forms.
Use the Application Explorer to access the harness rules that apply to the work types in your application. Use the Rules by Type Explorer to list all the harness rules available to you.
Harness rules are instances of the Rule-HTML-Harness class. They are part of the User Interface category
How to unit test a harness rule
|
Understanding
CSS styles
How to support work object copying How to support work object printing User interface — Concepts and terms |
|
Atlas — Standard Harness rules |
User Interface category
Help Home