Auto-generated HTML

PRPC translates information on some types of rule forms to HTML, JSP tags, and JavaScript when you save the rule form. The assembly of an auto-generated stream takes places in two phases.  In the first auto-generation phase, the default data transform in the stream rule is converted to JSP by the pzAssemblePreprocess activity, which updates the pySourceStream property of the rule version. In the second phase, the JSP is built into Java code by the stream assembler.

• Control rules (auto-generated controls were introduced in V6.1 SP2. See Standard auto-generated control rules)
• Sections
• Flow Actions
• Harnesses

Auto-generation provides these benefits:

• Eliminates hand-coding, which simplifies design and maintenance.
• Preserves custom settings when you upgrade your system.
• Eliminates manually entered inline JavaScript, which reduces cross-site scripting (XSS) vulnerabilities and improves performance.
• Ensures browser independence and compatibility.

These rule types typically accept manually entered HTML, JavaScript, and code:

• Correspondence rules
• Correspondence fragment rules
• HTML rules
• HTML fragment rules
• XML rules

About Sections About Control rules

Definitions