web technology Online Quiz - 79

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.

Rule-RuleSet-Version is the specific rule type in Pega PRPC that can be locked and unlocked to prevent or allow modifications to rules within that version. Locking a RuleSet-Version is an important governance mechanism to protect production rules from accidental changes. Other RuleSet-related rule types like Name, List, and ProCom don't have lock/unlock capabilities.

When a ticket is raised in Pega, it affects all active flow executions for that work object that are currently running and contain the configured ticket, forcing them to branch or jump to the designated ticket step.

In Pega PRPC's access control model, when an access role is specified on a parent class, it applies to that parent and all its child classes by default. However, this inheritance can be explicitly overridden by defining a more specific access rule on a child class. This provides flexible, hierarchical permission management.

Rule-Obj-SummaryView is specifically designed in Pega PRPC for displaying aggregated counts and statistics across work objects, such as counts by status (New, Open, Pending, Resolved). ListView is for listing individual records, Count is not a standard rule type for this purpose, and GroupBy is for grouping operations rather than summary displays.

In Pega PRPC, Work Objects are created when a flow is opened, which is typically the Opening Flow (also called the Starting Flow). This is the initial entry point that creates a new work object instance. Primary, Secondary, and Sub flows are process flows that operate on existing work objects rather than creating new ones.

In Pega, class names must follow specific naming conventions. A class name can be at most 64 characters long, which includes the organization, application, and class type segments. This limit ensures compatibility with database table names and system constraints. Options A (32) and C (128) are incorrect, and option D is false because there is a definite length restriction.

In Pega SLA (Service Level Agreement) configuration, the 'Late' interval can be specified multiple times to create graduated urgency levels. For example, you can have multiple Late thresholds (e.g., 1 hour late, 2 hours late) that trigger different actions or escalations. Goal and Deadline are single-value intervals that cannot be repeated. The question asks specifically about what can be 'repeated', making C the only correct choice.

Pega's Pattern Inheritance finds the parent class by removing pattern elements from the right. For 'MICO-Finance-', it first removes trailing special characters like '-' to find 'MICO-Finance', then looks for that class. Option A is correct because Pattern Inheritance strips the trailing dash. Option B lacks the prefix, and Option C still has the trailing dash which would be stripped in the next iteration.

Pega's organizational hierarchy follows a top-down structure: Organization (highest level) contains multiple Divisions, and each Division contains multiple Units. This hierarchy maps to the class structure: Data-Admin-Org, Data-Org-Division, and Data-Org-Unit. Option C correctly represents this order from top to bottom. Options A and B have incorrect sequences.

In Pega, to display a property as a drop-down (combo box) in user interface, you use the 'Prompt Select' HTML property. This property type automatically generates a drop-down control populated with the specified values (from field values, a local list, or other sources). Options A and C are not valid Pega property types, and option D is incorrect because there is a specific correct answer.

Edit Input rules (Rule-Edit-Input) are used to format and convert user-entered input data into a standardized format (such as stripping dashes from a phone number) before it is saved or validated in the property.

In Pega, the status of a work object is stored in the pyStatusWork property. This property holds the current status value (e.g., 'Open', 'Resolved', 'Closed') that determines the work object's state in the flow. Options A, B, and D are not valid property names for work object status. The naming convention pyStatusWork follows Pega's standard for protected properties (py prefix) indicating system-managed values.

Pega-ProCom is a mandatory prerequisite ruleset for all initial application rulesets in Pega. This ruleset contains core process commander functionality required for basic application operation. PegaApp and Pega-Rules are not prerequisites, and option A is incorrect because initial application rulesets MUST have prerequisites. Pega-ProCom provides essential foundation classes and rules that every application builds upon.

In Pega, every class MUST have a Direct Inheritance specified - it is mandatory. Direct Inheritance defines which class the new class immediately extends (its parent class in the class hierarchy). Pattern Inheritance is optional and only applies if the class name follows pattern conventions. Option B is correct because without Direct Inheritance, a class cannot be created. Option A is not mandatory, option C is incorrect (only Direct Inheritance is required), and option D contradicts the requirement.

Style Sheet (CSS) templates in Pega are stored as instances of the RULE-FILE-TEXT class. This class is used for text-based file rules including CSS, JavaScript, and other plain text resources. Option A is for binary style files, option B is not a standard rule type, and option D is for binary files (like images). Text-based style rules use RULE-FILE-TEXT, making C the correct answer.

In Pega, Correspondence Types are instances of the Rule-CorrType rule type. This rule type defines the metadata and configuration for correspondence templates (letters, emails, faxes) that can be generated during case processing. Options A, C, and D are incorrect - they either don't exist as rule types or are malformed names. Rule-CorrType is the standard Pega rule type for correspondence type definitions.

For short to medium-sized lists that change frequently, the TableEdit tab should specify 'Field Value' as the source. Field Values allow easy addition, modification, and removal of list entries without code changes. Option A (Local List) is for hardcoded lists, option C (Remote List) is for external data sources, and option D (Prompt List) is for dynamic prompts. Field Value (B) is the best choice for frequently changing short/medium lists.

In PRPC, Service Level Agreement (SLA) rules are categorized under the Process class because they define time-based processing expectations for work objects. Technical, SysAdmin, and Security are separate categories that don't contain ServiceLevel rules.