HTML rules
|
|
As a best practice, before creating a new HTML rule, it is strongly recommended that you investigate using an auto-generated section instead. The New form displays a message with information about that alternative.
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 may copy data instances but they do not support specialization as they are not versioned.
Based on your use case, the Create, Save As, or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields
This
Create an HTML rule by selecting HTML from the Technical category.
An HTML rule has two key parts:
Field |
Description |
|
Apply to |
Select the name of the class that this rule applies to, typically the default source of property values for the JSP tags or directives in the rule. The list of available class names depends on the ruleset you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form. In the unusual situation that this rule is to be referenced in an activity but without an associated clipboard page, enter @baseclass as the class name. NOTE: If this rule is to be referenced only with the <pega:include > JSP tag (or include directive) and has no associated page, do not create an HTML rule. For better performance, create an HTML fragment rule rather than an HTML rule. |
|
Identifier |
Enter a name for this HTML rule. Begin the name with a letter and follow the rules for a Java identifier. See How to enter a Java identifier. |
When searching for instances of this rule type, the system uses full rule resolution which: