Related information
You can create a "universal" part in an HTML rule by using the ultimate base class (@baseclass) as the Applies To part of the key.
If you use an HTML fragment instead, then at runtime the system avoids the overhead of the class inheritance algorithm, improving runtime performance.
If the HTML (or scripts or style sheets) text does not contain JavaServer Pages (JSP) tags, you can place the HTML in a text file rule rather than in a fragment rule. The system exports a text file rule to an appropriate directory the first time that the file is needed. In contrast to fragment rules, text file rules are not processed again, so using this approach improves performance.
You can incorporate static elements into your HTML forms and displays using normal HTML means, such as the following in the <HEAD> section:
<SCRIPT SRC="filename.js" TYPE="text/JavaScript>
</SCRIPT>
<LINK HREF="ruleprostylesheet.css" REL="STYLESHEET" TYPE="text/css">
When you save an HTML fragment rule, the system converts your inputs to Java source code. As a learning or debugging aid, you can review this Java code.
Click the Show Java toolbar button to see the system-generated Java code that implements the rule. The window presents a read-only preview of the Java code that implements this rule instance. This Java code is not identical to the Java code that is executed at runtime, which includes Java code inlined from other rule instances and reflects rules in the requestor's ruleset list.
Through directed inheritance, the immediate parent class of the Rule-HTML-Fragment class is the Rule-Stream class.
If your application rulesets contain HTML-Fragment rules, run the Rule Security Analyzer before locking a ruleset version, to look for possible security issues.