Links may not function; however, this content may be relevant to outdated versions of the product.
Organize the content and structure of a portal by defining harnesses. By populating harnesses with sections, you can build a modular interface that promotes reuse and maintainability.
Harnesses are instances of the Rule-HTML-Harness class and define the run-time form of your UI. You can use harnesses to organize a portal or a work form.
In a user portal, harnesses define the layout of the screen that the users see in a browser. For example, a harness can divide the portal into three separate areas: a header, a navigation pane, and a large content pane for displaying documents. Each of these areas points to a section that has a specific function, and that contains components that follow that function, such as links and menus in a header.
Because each area of a harness references a section, even if you update the sections, you do not have to update any of the harnesses in which you use the sections. This modular approach reduces development time and improves design consistency.
When you use harnesses as a basis for work forms, you can choose from several out-of-the-box harnesses to define an optimal interface for processing work items. For example, you can use a Review harness to present an assignment in read-only mode, and prevent users from changing information at later stages of case work. In addition, you can override the standard rules to adapt default harnesses to your specific business needs.
- Harness form -
Create a harness by clicking Create User Interface Harness in Dev Studio.
- Harness and Section forms Help Client Event Editor.
Use the Client Event Editor to identify a non-auto-generated control that, when a user interface event is performed on it, dynamically submits elements within a work item or flow action form and re-renders the display.
- Using the Condition Builder to configure dynamic UI actions.
User interface events such as entering a property value in an input box or selecting a value from a Dynamic Select field can automatically trigger UI actions such as refreshing a harness, a section, hiding a property or section, expanding a layout, and so on. Changes on the server or the clipboard, for example, through a declarative expression or
- Adding a role to an access group
You can assign access roles to an access group so that users who belong to the access group have a consistent set of functions available to them.
- Harness form - Completing the Display Options tab
Optional. Complete the Display Options tab to control the presentation of form-level and field-level error messages. You can customize the fonts, colors and image used in field-level messages in the Skin rule. See Skin form — Components tab — General — Errors.
- Harness form - Completing the Scripts and Styles tab
- Declare Trigger form - Completing the Pages & Classes tab
Use this tab to list the clipboard pages referenced by name in the Triggers tab. See How to Complete a Pages & Classes tab for basic instructions.
- List View form - Understanding the HTML tab
HTML tab on the List View form
- Harness form - Presenting flow actions
Harness form - Presenting Flow Actions
- Harness forms - Placing a button in a harness
On the harness form, a button is located in a cell at the bottom of the resulting user form. When clicked, a button executes an activity.
- More about Harnesses
Use harnesses to define the appearance and processing of user forms used in your application to create work items and process assignments.
- Viewing generated Java code of Access When rules
Previous topic Forms and fields Next topic Harness form -