[16.0][ADD] pms_l10n_es: unaccompanied minors declaration - #435
Open
jesusVMayor wants to merge 1 commit into
Open
[16.0][ADD] pms_l10n_es: unaccompanied minors declaration#435jesusVMayor wants to merge 1 commit into
jesusVMayor wants to merge 1 commit into
Conversation
Minors travelling on their own with their guardian's authorization could not be checked in: every guest under 18 required a relationship with an accompanying guest. The declaration waives it, and lives on the folio since guardians and minors may be booked in different reservations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Minors travelling on their own with the authorization of their legal guardian cannot be checked in.
pms_l10n_esrequires every guest under 18 to declare a relationship with an accompanying guest, and when the whole party is made of minors there is nobody to relate them to.This adds a declaration that waives that requirement, plus an optional binary to keep the guardian's authorization. The case was tried against the staging environment of the Hospedajes webservice, which accepts it.
Why the authorization is optional
The hotel is legally required to keep the authorization of the minor's guardian. The field stays optional so no hotel is forced to store it in Odoo.
Why the declaration belongs to the folio
The guardians may be booked in one reservation and the minors in another one of the same folio, so a reservation would decide it on the wrong set of guests.
The fields are exposed on the reservation as well, since that is where they get managed.
Why unknown birthdates are ignored
Checkin data gets filled in any order, so a guest whose birthdate is not known yet is left out of both rules:
Completeness and consistency are kept apart: what a single guest must fill in stays in
_checkin_mandatory_fields, and the folio-wide check that the declaration still holds runs on boarding.