2 Feature Summary
Column Definitions
| SMALL SCALE: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal. |
| LARGER SCALE: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher. |
| CUSTOMER ACTION REQUIRED: You must take action before these features can be used. These features are delivered disabled, and you choose if and when to enable them. |
| FEATURE |
|
STEPS TO ENABLE |
|---|---|---|
| Distribution Reservation Service API operations - postReservation, putReservation | SMALL | Yes |
DISTRIBUTION CHANNELS
Distribution Reservation Service API operations - postReservation, putReservation
Distribution Reservation Service API operations postReservation and
putReservation now support the global distribution values
guaranteeType and paymentType, in addition to the
existing OPERA Cloud guaranteeCode and paymentMethod
values. When a global guaranteeType or paymentType is
provided, the service maps the value through Distribution Reservation Codes to the
property-specific OPERA Cloud code. Where applicable, responses include the
reverse-mapped global value.
IMPACT OR OTHER CONSIDERATIONS
Existing integrations that use guaranteeCode and
paymentMethod continue to work. Requests must include either
guaranteeType or guaranteeCode, but not both. They
must also include either paymentType or
paymentMethod, but not both. Requests with conflicting guarantee or
payment fields are rejected. Reservations fail with an invalid guarantee or invalid
payment type error when the required mappings are missing.
STEPS TO ENABLE
Review the updated OHIP API specification. To use
guaranteeType or paymentType, verify that the
required Distribution Reservation Codes mappings exist for the property.