In Guidewire, when are entities in a new bundle automatically committed?

In Guidewire, entities in a new bundle are automatically committed when they are processed by the application. This means that once the application takes action on the entities, such as through workflows or user interactions that trigger processing, the changes are saved to the database. This concept is crucial in understanding the concept of bundles in Guidewire, which encapsulate changes made to entities during a transaction.

The option referring to a read-only interface does not result in changes being committed, as read-only operations are designed to fetch data without modifying it. Similarly, entities that are created without user input do not automatically guarantee a commit unless processed, as they could remain in memory until explicitly saved. Lastly, modifications made by queries also do not trigger an automatic commit; they typically retrieve or display data without altering the state of the entities in the bundle. Therefore, it is the action of processing within the application that leads to the automatic commitment of changes to the entities.