Pegasystems Platform Fundamentals

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.

Property values defined in a model rule cannot be overridden at runtime on a work object - they are template values that apply when the model is first used. This design ensures consistency and prevents unintended modifications to the standard model behavior.

The Assignment Smart Shape is specifically designed to present screens and forms to end users for interaction or data entry. Connectors route flows between shapes, Integrators connect to external systems, and Flow Actions define what happens after a user submits an assignment.

Work-GenerateID is the rule used to automatically generate unique work object IDs in Pega. The other options are not valid rule names for ID generation - Work-ObjectID and Work-Object are not standard rules, and Work-New is not an ID generation mechanism.

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.

Forward chaining in Pega REQUIRES all input property values to be available before computation can proceed - it does not allow advancement with missing inputs. The statement describes backward chaining behavior, which can work with incomplete information. Note the typo 'Farward' in the question.

When an Assignment uses Worklist (which expects to assign to an individual worklist) but the Router uses ToWorkbasket (which routes to a workbasket), there's a routing mismatch. Pega saves the flow but raises a Java exception at runtime because the routing destination is incompatible - the flow cannot determine where to place the assignment.

A Local Flow Action allows a user to perform additional actions (like attaching a budget sheet) without completing the main assignment. Unlike Connector Flow Actions or Correspondence rules, Local Flow Actions keep the assignment open for the main action (approval) after the local action completes. Rule-Template-Excel is for Excel templates, not attachments.

Work parties are people or groups (like customers, stakeholders, or interested parties) who have an interest in the work object's progress but are not necessarily the workers performing the tasks. Option B describes work object covers/cases, C describes restricted work types, and D describes work users or operators assigned to tasks.

The standard Perform and Review harness forms use a specific icon (typically a paperclip or attachment indicator) to show attachments exist. However, the statement as given is marked False, suggesting either the indicator is different (like a specific icon variation), or there's a specific detail about when the paperclip appears that makes the universal statement false.

All three formats are valid work object IDs in Pega: W-1234 (standard prefix-ID), W-1234-S (with suffix for variations), and Pega-1234-Work (application-specific format). Pega's ID configuration is flexible and supports multiple patterns depending on the application and class structure.

Pega supports symbolic subscripts like CURRENT, LAST, INSERT, APPEND, and PREPEND when working with Page Lists. FIRST is not a valid symbolic index in Pega; numeric index 1 is used instead to reference the first item.

A business user interacts with the application to process, receive, and resolve work items. System and process architects design and implement the application, while administrators manage environment resources.

Pega's organization hierarchy is structured in three nested levels: Organization (highest), Division (middle), and Unit (lowest). This hierarchical structure supports reporting, access control, and organization-based routing. Options B, C, and D are incorrect because 'company' and 'job function' are not standard levels, and work group/user are not part of the organization hierarchy itself.

In Draft mode, a Flow cannot be executed (running is disabled) and cannot create Work Objects (work items). Smart shapes can still be added during drafting, and the Flow remains visible to rule resolution for development and testing purposes.

The Obj-List method returns results in a clipboard page of class Code-Pega-List. This is a standard Pega list class, not Rule-Pega-Obj (used for rule instances) or pxResults (a page name, not a class).

Work Party Roles and Access Group Roles are different classes with different purposes. Work Parties define roles for participants in a work object (like Customer, Reviewer), while Access Groups define authorization and security roles for users.

Rules Inspector is the debugging tool that shows HTML structure and embedded properties in the UI. Clipboard shows data pages, DB Trace is for database performance, and Tracer is for execution flow - none of these show HTML/properties like Rules Inspector does.

In Pega, folders and their contents have a many-to-many relationship. A single folder can contain multiple work items (cases), and a single work item can belong to multiple folders simultaneously, allowing flexible grouping.