web technology Online Quiz - 86

A WorkPool in PEGA is a collection of similar Work Objects that share common characteristics and are processed together. WorkGroups are organizational groupings, not collections of work objects. The WorkPool helps in managing and routing similar types of work items efficiently.

Work Objects are created during Opening Flows in PEGA. The Opening Flow is the initial flow that creates a new work object instance. Primary, Secondary, and Sub flows are executed after the work object already exists.

An HTML property rule (now known as a Control rule) is used to customize the display of property values on user interface screens, allowing developer-defined custom formatting and behaviors.

Declare rules (like Declare Expressions, Constraints, and OnChange) execute automatically. They run during flow execution, at the end of activity steps, or upon database commits depending on the rule type, making 'All of the above' correct.

The Integrator shape in PEGA is used to send and receive data from external systems. It handles the communication interface between the PEGA application and external systems. Ticket is for routing, Fork is for parallel processing, and Split-Join is for subprocess coordination.

The Property-Set method is the standard way to update properties in PEGA activity steps. Java methods are not the recommended approach, AtSetValue is not a standard PEGA method, and {PropertyName INPUT} is a reference syntax, not an update method. Property-Set ensures proper clipboard manipulation and rule compliance.

Rule-RuleSet-Version rules can be locked and unlocked in PEGA to prevent or allow modifications. Rule-RuleSet-Name, Rule-RuleSet-List, and Rule-RuleSet-ProCom are other rule types that don't have the lock/unlock capability. Locking rule versions helps maintain stability in production environments.

PEGA class names have a maximum length of 64 characters. This is a platform constraint to ensure database compatibility and system performance. Options A (32) and C (128) are incorrect, and there is definitely a length restriction enforced by the system.

For short to medium-sized lists that change frequently, Field Value should be specified in the TableEdit tab. Field Values are optimized for dynamic lists. Local List and Remote List are for different scenarios, and Prompt List serves a different purpose in UI configuration.

Ticket events impact only the flows that are actively being executed at that time AND have that ticket configured. This is a targeted mechanism that doesn't affect all flows or all flows with the ticket - only the currently running ones. This allows precise control over flow interruption.

ServiceLevel rules for setting SLAs are found under the Process menu in PEGA. Technical is for technical settings, SysAdmin is for administrative functions, and Security handles security configurations. SLAs are process-related governance tools.

Activity Steps are NOT a separate category in the Event Types To Trace tab. The tracer traces Flows, Declare Constraints, and Declare Decision Trees as event types, but Activity Steps are traced at the Activity level, not as individual step events. This is a common point of confusion.

This is a duplicate of question 146856. The Property-Map-Value method takes a single row input to evaluate a 1D map value, whereas Property-Map-ValuePair takes both a row input and a column input to evaluate a 2D map value.

External systems access PRPC application data and processes using Services. Services expose PEGA functionality externally. Connectors are used when PEGA initiates outbound calls to external systems. Servers refers to infrastructure, not integration patterns. The direction matters: Services are for INBOUND access from external systems.

In Pega, correspondence types are defined using Rule-CorrType rule instances. This rule type contains the template and settings for correspondence. Rule-Obj-CorrType and other options are incorrect as they don't follow the standard rule type naming convention for correspondence type definitions.

In Pega SLAs, the Late interval can be repeated multiple times to create recurring escalation patterns. Goal and Deadline are single events that occur once. This repeated Late setting allows for ongoing reminders until the assignment is completed.

SmartBuild follows this sequence: Class Structure (define the data model and inheritance), Properties (define fields on classes), User Interface (design screens using those properties), Activities (add automation and processing logic). This order ensures each layer builds on the previous one.

The Show-Page method is used to display XML-formatted output in Pega. This method sends the current page as XML to the user's browser. Options like Show-XML or Display-XML are not valid Pega methods.

Operators can share the same workbasket when their operator IDs belong to the same WorkGroup. WorkGroups determine which workbaskets are visible and accessible to group members. ClassGroup, WorkPool, and AccessGroup serve different purposes in Pega security and organization.