GUI and Web Frameworks

When creating a ListView to display operator information (Full Names and User Identifiers), the Data-Admin-Operator-ID class is the correct 'Applies To' class because it contains the operator ID records with these properties. Rule-Obj-Operator is an obsolete class, Rule-Obj-ListView is for defining list views themselves, and Rule-Access-Role-Name contains access roles not operator data.

Pega properties prefixed with 'px' are system-managed and read-only. They cannot be modified using standard methods like Property-Set. The special method Property-Set-Special is designed specifically to modify these system-controlled px properties.

Page-New is the correct method for creating top-level pages on the clipboard in Pega. Obj-Open is used to retrieve existing pages from the database into the clipboard, not create new ones. The other options are not valid Pega methods.

The Rule Inspector tool identifies and displays rules that are actively being used during case processing and UI rendering. It specifically detects Properties, Harnesses, and Sections which are the UI and data structure rules that are currently active. When conditions are logic rules that evaluate but aren't typically surfaced in the inspector.

In a Rule-Declare-Expression, the Page Context identifies the embedded page (or page list/group property context) on which the properties referenced in the expression are defined, ensuring Pega resolves the properties relative to that correct context.

For a small, fixed set of 5 values, Local List is the correct choice in the Table Edit tab. Remote List is for external data sources, FieldValue is for dynamic lists stored in database, and ClassKey is for keyed access.

In PRPC (Pega Rules Process Commander), the standard activity NewDefaults is a placeholder (dummy activity) that can be overridden in user classes to implement pre-display logic before the harness new is shown. Static values for work objects are typically set in pyDefault.

To display a calendar icon alongside a single date value property in a perform harness, use the Date-Calendar Rule-HTML-Property. This control provides both the date display and a calendar icon for date selection in one interface element.

After Page-New creates a temporary page, you should clean it up with Page-Remove to prevent memory leaks. This is especially important when the page is only used temporarily during the activity. Obj-Save (D) would persist data, which isn't needed for temporary pages. The other options don't address cleanup.

pyLabel is the correct property for storing a short description in a work object because 'py' properties are standard Pega properties, and pyLabel is specifically designed for holding labels and short text descriptions. pyShortDescription (A) and pzShortDescription (C) are not standard Pega properties, and pzLabel (D) is used for internal purposes.

In Pega, Single Value properties are NOT aggregate properties - they hold a single atomic value. Page, PageList, PageGroup, ValueGroup, and ValueList are all aggregate property types that can hold multiple values or nested structures. Therefore, Single Value is the correct answer as the only non-aggregate property listed.

In Pega, the standard local actions for attaching content are: AttachANote (for attaching notes), AttachAURL (for attaching web links), and AttachAFile (for attaching files). AttachADocument is not a standard local action name in Pega's library.

Limiting custom Java ensures application maintenance and upgradability, which is a key Pega guardrail. Reusing standard flow actions as placeholders or starting points promotes best practice compliance and accelerates development.

Step pages define the context for executing a specific step in an activity. They are optional because a step can run in the context of the activity's primary page. They are not automatically deleted upon activity completion and their class can differ from the activity's class.

Wireframes are low-fidelity schematics that show structural placement of content elements (text, images, buttons) and screen flow without visual design details like color or typography. They focus on layout and interaction, not aesthetics. Color schemes, visual standards, and development strategies come later in high-fidelity designs and specifications.