Add New Aggregate Base Field

To add a base field to an aggregate, you define its type, responsibility, persistence, and calculation behavior. This process ensures the new field is correctly configured for manual input or calculated values within the domain model.

Manual aggregate fields require direct input, calculated volatile fields compute values at runtime without persistence, and calculated persistent fields store computed results in the database. This distinction governs how fields are loaded, calculated, and exposed via DTOs.

You configure calculation behavior by integrating the new aggregate field into lifecycle hooks like doCalcAll(). This ensures calculated volatile or persistent fields are automatically computed and updated during the domain model's execution cycle.

You should expose a calculated aggregate field through a DTO when the computed value needs to be transmitted to the presentation layer. Mapping calculated fields to DTOs ensures the calculated results are available without exposing underlying domain model persistence logic.

Yes, you can define a new aggregate field as calculated volatile, meaning it skips database persistence entirely. The field is computed at runtime via lifecycle hooks like doCalcAll(), providing transient values without requiring persistent storage configuration.

Without defining calculation placement, new calculated aggregate fields lack execution triggers, leading to stale or null values. Properly mapping fields to lifecycle methods like doCalcAll() is required to enforce calculation rules and ensure data consistency across the domain model.