Application Guardrails landing page
About the Rule Security Analyzer
About HTML rules |
|
Use an HTML rule to describe how the system is to assemble, through stream processing, portions of HTML displays in your application.
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.
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.
|
|
guardrails |
|
|
About JavaServer Page tags
Application Guardrails landing page About the Rule Security Analyzer |
|
|
Standard HTML rules |
Technical category