Guidewire configuration follows the principle ofModular UI Design, especially when dealing with entity inheritance (subtypes). In this scenario, the carrier has a base Watercraft_Ext entity with multiple subtypes (e.g., PowerBoat, Sailboat). These subtypes share common attributes (like Make, Model, and Year) but have unique attributes (like MastHeight for sailboats or EngineType for powerboats).

The best practice for designing an interface for subtypes is to useModal InputSets(Option D). This approach involves creating a "master" Detail View (DV) that contains the common fields shared by all watercraft. Below the common fields, a ModalInputSet is added. Guidewire's PCF engine then uses a "mode" (typically the subtype name) to determine which specific InputSet to render at runtime.

This method is superior to others for several reasons:

Maintenance:Common fields are defined in only one place. If you need to add a "Color" field to all watercraft, you change one DV, not five separate pages (avoiding the redundancy of Option A).

Performance and Cleanliness:It avoids a massive, cluttered page with hundreds of "visible" expressions (Option B), which is difficult to maintain and can slow down page rendering.

User Experience:It provides a seamless experience where the UI dynamically adjusts to the specific boat type without the jarring transition of moving between entirely different pages (Option C).

By using InputSet widgets with the mode property, developers can create a highly scalable and organized UI that mirrors the object-oriented structure of the underlying Data Model.