PEGACPBA88V1 Practice Questions

Order of Events:

A user clicks the button.

The system applies a data transform.

The order ID value is set to the value of the confirmation number if the system confirms the payment.

The system refreshes the section.

 A user clicks the button.

Explanation: The event sequence starts when the user interacts with the button by clicking it. This is the trigger for the subsequent actions.

Decision tables in Pega are ideal for situations where you need to apply multiple conditions to arrive at a decision. They are best used when you have a limited number of conditions and actions that result in a discrete set of outcomes.

B.  

A dance studio recommending a membership type based on the number and type of dance classes is suitable for a decision table. The number and type of classes can be mapped to specific membership types in a table format where each row represents a possible scenario and outcome.

D.  

A hair care company suggesting a line of products based on various attributes such as hair type, scalp moisture, hair moisture, and whether it is color-treated is also suitable for a decision table. Each combination of attributes can correspond to a specific product recommendation, making a decision table an efficient way to handle these rules.

References:

Pega Decision Management Overview

Pega Academy: Decision Table Rules

Property reference: .Address(1).PostalCodeField type: Single record data relationship

Property reference: .ShippingAddress.CityField type: Text

Property reference: .BillingAddress.TelephoneField type: Multiple record data relationship

Property reference: .Address(1).PostalCode

Field type: Single record data relationship

Explanation: The .Address(1).PostalCode property indicates a specific postal code within a single address. The (1) suggests it’s part of an indexed or paged list, but each PostalCode is a single entity within that address record.