Which statements are true about creating new custom subtypes?

Creating new custom subtypes involves specific requirements and constraints within the Guidewire environment. Each statement provided highlights an important aspect of this process:

When a custom subtype entity is being defined, it is indeed true that it cannot have an ETX file. ETX files are used to define extensions on existing entities, and custom subtypes are inherently new definitions rather than extensions of existing entities.

Entities that are marked as final cannot have subtypes. This is a critical rule in object-oriented design, as marking an entity as final means that it is intended to be complete and cannot be subclassed or extended further.

A custom subtype entity is defined in an ETI file. The ETI file serves as the initial definition for the entity and its properties. This is where you specify the characteristics of your custom subtype.

Since all these statements are accurate reflections of the rules governing the creation of subtypes in Guidewire, it's correct to conclude that all of the provided statements are true. Understanding these principles is essential for effectively managing and extending entities within the Guidewire platform.