A business analyst has a requirement to use either the EmailAddress1 or EmailAddress2 field on...

When extending the functionality of base Guidewire entities (like ABContact), developers use Enhancements. Enhancements allow you to add methods and properties to a class without modifying the original source code. For the requirement of deriving a value from existing fields (logic often referred to as a " calculated " or " virtual " field), the best practice is to use a Property Get.

A property get allows the derived value to be accessed using standard dot notation (e.g., myContact.EmailAddress_Ext) just like any other field on the entity. This is particularly beneficial in PCF Configuration, as the property can be used in the value attribute of a widget, and the UI engine will treat it as a readable piece of data. Using a function (Option C or D) would require parentheses in every call, which is less " Gosu-esque " for a simple data retrieval task.

Furthermore, naming conventions in Guidewire dictate that custom extensions should include a suffix like _Ext to prevent naming collisions with future base application updates. By choosing a property get, the developer ensures the code is clean, readable, and highly reusable across the entire InsuranceSuite. This approach encapsulates the null-checking logic within the entity ' s enhancement, meaning that if the business logic for choosing the email address ever changes, it only needs to be updated in one place rather than in every PCF where the email is displayed.

==========