Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.


Updated on April 5, 2022

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.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us