In some cases, it is difficult or impossible to tell whether the values set/entered by a user are actually what the user meant, or simply the result of ignoring some of the existing controls. A key example is not entering any vacation data: Does that mean the employee did not take any vacations? Possibly, but it is quite likely that the person entering the data simply forgot to bring up the vacations dialog.
It may be worthwhile to consider modifying/adding controls to the dialog to differentiate between these two cases, e.g. a checkbox labeled "Employee did not take any vacation", which defaults to being unchecked; this can allow the app to properly warn/request confirmation for printing the "computation results" when the user has actually neglected to enter vacation-related data.
In some cases, it is difficult or impossible to tell whether the values set/entered by a user are actually what the user meant, or simply the result of ignoring some of the existing controls. A key example is not entering any vacation data: Does that mean the employee did not take any vacations? Possibly, but it is quite likely that the person entering the data simply forgot to bring up the vacations dialog.
It may be worthwhile to consider modifying/adding controls to the dialog to differentiate between these two cases, e.g. a checkbox labeled "Employee did not take any vacation", which defaults to being unchecked; this can allow the app to properly warn/request confirmation for printing the "computation results" when the user has actually neglected to enter vacation-related data.