Create a harness by clickingin 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.
> Key parts:
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
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.
Enter a name for this harness. If this rule is to override a standard rule, choose:
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.
Additional creation options
|Template|| Select a template rule to copy for the harness and mark the new rule as JSR
168 compliant. |
The rule type Service Portlet is deprecated. Use Pega Web Mashup instead.
- Harness form Adding a screen layout
Screen layouts determine the overall structure of your screen. They define the structure of a harness that is included in a composite portal. When you create a new harness it contains a screen layout by default. A harness can contain only one screen layout.
- Harness form Adding a container.
A container can provide a visual grouping of other elements on a harness form, including sections and subsections. Every harness contains one or more containers. A container can contain a header, and includes the area of the harness form where tabs appear, if you use tabs to present sections.
- Harness forms - How to support work item copying
Follow these steps to allow users of your application to enter a new work item by copying information from an existing work item. Through a data transform, you can control which properties in the existing work item are copied.
- Harness forms - Supporting work item printing
Follow these steps to support complete or custom printing of work items in your application, including information about attachments and history.
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.