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.

About HTML rules

Updated on April 5, 2022

Use an HTML rule to describe how the system is to assemble, through stream processing, portions of HTML displays in your application.

The following tabs are available on this form:

For highest quality and security, minimize the use of HTML rules that you create in application RuleSets. While HTML rules are necessary for a few specific features, use of auto-generated sections in flow actions and harnesses is preferable when possible. Auto-generated rules may often provide better performance, greater security, greater levels of browser independence, and more consistent branding and styles than hand-crafted rules.

If your application RuleSets contain HTML rules, use the Guardrails landing page to assess guardrail compliance, and use the Rule Security Analyzer to check for security vulnerabilities.

Where referenced

HTML rules may be referenced in flow actions, flows, sections, and harnesses. For example, the input fields on a flow action are defined through an HTML rule. You can also use HTML rules for data mapping in services and connectors.


Use the Application Explorer to access HTML rules that apply to the work types in your application. Use the Records Explorer to list all the HTML rules available to you.


HTML rules are part of the Technical category. An HTML rule is an instance of the Rule-Obj-HTML rule type.

  • 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.

  • HTML

    Complete this tab to define the HTML and JSP tags or directives for this rule.

  • HTML form - Completing the Pages & Classes tab

    Identify what is known about the class of each page that is referenced in the source HTML on the HTML tab. See How to Complete a Pages & Classes tab for basic instructions.

  • More about HTML rules

    Referencing other rules and static files

  • Viewing generated Java code of Access When rules
  • Improving your compliance score

    Follow development best practices to improve your compliance score. By eliminating risks, such as custom code or degraded performance, you can improve quality and resolve issues before your application goes into production.

  • JavaServer Pages tags
  • Rule Security Analyzer

    To make Pega Platform applications more secure, you can run the Rule Security Analyzer. This tool searches through non-autogenerated rules to find specific JavaScript or SQL coding patterns that match regular expression rules, some of which might indicate security vulnerabilities, as detailed below.

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