Comparing HTML fragments with HTML rules
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.
Comparing HTML fragments with static Web server files
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:
<LINK HREF="https://docs.pega.com/ruleprostylesheet.css" REL="STYLESHEET" TYPE="text/css">
You can view the generated Java code of a rule by clicking. You can use this code to debug your application or to examine how rules are implemented.
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.
- include JavaServer Page tag
- Rule Security Analyzer
- About HTML Fragment rules
- HTML Fragment rules - Completing the New or Save As form
HTML Fragment rules