Question

For example, consider an application to process automobile insurance quotes. To price the quote, you need to know the accident history of the driver. Each accident record is an instance of a specific data type. You create a report to return the accident history for a driver and use a filter to return only accidents for the driver requesting the quote. If the report filter uses the UserName property from pyWorkPage, you must tell the report the class for pyWorkPage (for example INSCO-Quotes-Work). This allows Pega to reference the UserName property and the report filter functions as intended. Otherwise, Pega assumes that UserName is part of the data type, rather than the case, and the filter does not work correctly.

A. True
B. False

Answer 1

The statement is true; in Pega, specifying the class for pyWorkPage ensures the report filter correctly accesses the UserName property for automobile insurance quotes.

Step-by-step explanation:

In the context of generating automobile insurance quotes using Pega systems, the statement is true. When creating a report to return the accident history of a driver, it's crucial to use the correct property reference for filtering. If a report filter uses the UserName property from pyWorkPage, specifying the class for pyWorkPage (e.g., INSCO-Quotes-Work) is necessary. This specification allows Pega to correctly reference the UserName property in the context of the case (work object) and not the data type (accident record). Without this, Pega might assume UserName is part of the accident record's data type, which would result in an incorrect filter operation.

Understanding data types is essential for Pega developers. For instance, the number of accidents would be considered discrete quantitative data because it represents countable incidents. The distance to the nearest grocery store would be continuous quantitative data, as it can be measured with infinite precision.