web technology Online Quiz - 80

To branch to another flow without returning control, you simply do not have any connectors emanating from the Flow shape. This creates a one-way transfer - execution continues in the called flow and never returns to the original flow. The Flow parameters do not have a 'Branch' option.

Property-Seek-Value is used to invoke backward chaining. In backward chaining, the system seeks a value only when needed (on-demand) rather than deriving it proactively. This is a lazy evaluation approach where the value is computed when first requested.

A property qualifier is an optional feature that adds one or more facts to a property's value. Property aliases are alternative names, enumerated text values restrict input, but property qualifiers actually extend the property with additional contextual information.

A Fork shape is used when you want to invoke a when rule (condition-based routing). Decision shapes invoke decision tables or map values. Fork shapes are specifically designed to evaluate when conditions and branch execution accordingly.

In PRPC, all custom classes inherit from three base classes: Work- (for work/case objects), Data- (for data/reference objects), and History- (for historical records). These provide the fundamental inheritance structure for the PRPC class hierarchy.

The Exit-Activity method is specifically designed to terminate the current activity's processing and return control to the calling activity. This is the standard method name used in Pega/Process Commander for activity termination, unlike Activity-End or End-Activity which are not valid method names in the system.

Forward Chaining is the correct declarative processing type that proactively obtains data by resolving triggered dependent property value changes. When a property value changes, forward chaining automatically triggers and resolves all dependent properties that need to be recomputed, working forward through the dependency chain to ensure all related data is available.

The statement is false - Process Commander does support creating rules for application-specific attachments. The platform provides capabilities to define attachment rules and handling mechanisms that can be customized for specific application requirements. This is a standard feature in Pega's case management and attachment functionality.

In the early stage of design, you should create a list of systems, information types, and interconnect mechanisms, but defer detailed message specifications to later stages. Option B correctly represents this high-level approach, while options A and C include excessive detail (message exchange details and property mappings) that should be refined after the overall integration architecture is established.

The statement is false - you should create properties for higher-level classes before lower-level classes in Pega's class hierarchy. This top-down approach ensures that inheritance works properly, as lower-level classes (subclasses) inherit properties and behaviors from their higher-level parent classes. Creating parent class properties first provides the foundation for child classes to extend.

The statement is false - a flow in Pega can have only one Start shape. The Start shape marks the entry point where flow execution begins, and having multiple start points would create ambiguity about where the flow should initiate. This is a fundamental rule in Pega flow design to ensure clear, predictable flow execution.

The statement is false - while you can create connectors for every possible return value from a Decision shape, it is not required. Pega flows can include default handling or error cases where not every return value needs an explicit connector. The best practice is to handle expected outcomes explicitly, but the system does not mandate connectors for all possible returns.

The statement is false - division names must be unique within the organization in Process Commander. The system uses division names as key identifiers for organizing rules, data, and organizational structure. While Process Commander has sophisticated differentiation capabilities, this does not extend to allowing duplicate division names, which would create conflicts in rule resolution and data organization.

In Pega PRPC, Work IDs can follow various formats depending on the work pool configuration. The formats W-, W-TCS, and TCS-W- are all valid representations of Work IDs, as they represent different ways work objects can be identified within the system.

In Pega PRPC, cover and covered objects must belong to the same ClassGroup to maintain proper inheritance and data organization. This ensures that related work objects are grouped together correctly within the class hierarchy, which is fundamental to Pega's data model.

The Property-Set method is the standard, recommended approach in Pega PRPC for updating property values within an activity. This method is specifically designed for property manipulation and provides proper error handling and validation. Java methods should be avoided for simple property updates, and AtSetValue is not a standard Pega method.

Development RuleSets in Pega PRPC must adhere to specific naming conventions. They can be a maximum of 32 characters in length. Development RuleSets cannot contain spaces or special characters, and they cannot use 'Pega' as a prefix (which is reserved for standard RuleSets provided by Pega).

According to Pega's 'Ten Guard Rails' best practices framework, application performance should be monitored on a weekly basis. This regular monitoring helps identify and address performance issues before they become critical, while not being so frequent as to be burdensome.

The Tracer tool in Pega has an 'Event Types To Trace' tab that includes various rule types like Flows, Declare Constraints, and Declare Decision Trees. However, 'Activity Steps' is not listed as a separate event type in this tab - you trace entire activities, not individual steps, making this the correct answer for what doesn't belong.

In Pega PRPC, Services are the mechanism that allows external systems to access Pega application data and processes. Services expose Pega functionality externally through various protocols. Connectors are used by Pega to reach out to external systems (the opposite direction). Servers refer to infrastructure, not an integration mechanism.