Reservation confirmation: analysis and design

1. Functional requirement

Prevent a reservation from being confirmed if its date is missing or earlier than the minimum allowed date. Preserve the existing availability check before saving.

2. Fictional evidence

101: Event 'Confirmar'
102:    ValidarDisponibilidad()
103:    GuardarReserva()
104: Endevent

The existing operation checks availability and then saves the reservation. Identifiers are retained from the fictional Spanish example.

3. Acceptance scenarios

• Missing date: show a message and prevent saving.
• Date before the minimum: show a message and prevent saving.
• Date on or after the minimum: continue with the existing availability check and save behavior.

4. Proposed design

Event 'Confirmar' // reference: 101
   If &FechaReserva.IsEmpty() Or &FechaReserva < &FechaMinima // ADD
      Msg('Select a valid date.') // ADD
      Return // ADD
   Endif // ADD
   ValidarDisponibilidad() // reference: 102
   GuardarReserva() // reference: 103
Endevent // reference: 104

This is illustrative pseudocode, not compiled GeneXus code. A reference to line 108 has no supporting evidence; line 103 matches the fictional source.

5. Follow-up checks

Compile the implementation, test each scenario, verify that rejected reservations are not saved, and confirm that existing availability rules remain intact.

This is a fictional design proposal. It does not establish approval, implementation or production behavior.