Markup and Web Languages

The Show-Page method is the standard Pega method for displaying XML-formatted output. It serializes page data into XML format for display or transmission. Options B, C, and D are not valid Pega methods for this purpose.

In Pega's rule naming convention, Harness rules are named 'Rule-HTML-Harness'. The naming follows the pattern Rule-{Type}-{Specific}. Option A correctly identifies the full rule type name.

The Show-Page method in Pega PRPC is used to display a clipboard page in XML format. This is the standard method for viewing page data structured as XML. Apply-Parse-XML is used for parsing XML into clipboard pages (the reverse operation), and Show-XML or Display-XML are not standard Pega methods.

Page Context in PRPC rules specifies which page's properties the rule will operate on. It's not about excluding actions (A), not specifically about $Any/$None usage (B), and not limited to declarative rules (D). The Page Context directly targets the property scope.

Pega HTML rules use a custom comment syntax with curly braces: {COMMENT} text {/COMMENT}. This is not standard HTML (which uses ), but specific to Pega's HTML rule format. The other options show incorrect syntaxes (* line *, // Comment) that aren't valid in Pega HTML.

In Pega, 'HTML' type properties or rules containing HTML code are primarily used for rendering and customizing the display of user interfaces, screens, and fields, rather than manipulating XML or simply displaying escape characters.

PEGA HTML provides several directives for working with properties: Reference (for reading property values), Lookup ( for searching), With (for context), and Save (for persisting). All of these are valid HTML directives in PEGA for property manipulation.

Auto-generated HTML is available in Section rules and Flow Action rules. HTML Fragment and Harness rules are manually authored. HTML Property is not auto-generated in the same way - it's a specific rule type for property-level HTML.

Embedded pages in PRPC cannot be nested within other embedded pages due to architectural limitations. The system does not support hierarchical embedding of pages, which prevents potential circular references and maintains predictable page structure.

When the Auto-generated HTML checkbox is re-checked, PRPC regenerates the entire HTML section, replacing any custom code that was added while the checkbox was unchecked. This is by design - auto-generation takes precedence over custom modifications to maintain consistency.

Rule-Obj-Validate is the standard Pega rule for validating property values entered through HTML forms. It contains validation logic for individual properties or entire pages. Rule-Form-HTML (A) defines form structure, not validation. Options C and D are methods, not the primary validation mechanism.

Page.User.Identity is correct because it provides the identity information of the authenticated user, including the username. Page.User.IsInRole (B) checks role membership but doesn't return the name, and Page.User.Name (C) is not a valid property. The Identity object contains the Name property that holds the username.

Rule Resolution in Pega does NOT apply to Rule-HTML-Property rules. Rule Resolution is the mechanism that determines which rule to execute when multiple versions exist, but HTML Property rules are resolved by class inheritance and directory structure, not through the Rule Resolution process. Therefore, the statement is False.

Text files in Pega store static content like HTML style sheets, JavaScript code, or other static text that should bypass rule resolution. Fragments, streams, and harnesses are different rule types that serve other purposes - fragments are reusable UI components, streams are for data processing, and harnesses define the overall UI structure.