5 Limitations and Constraints

Limitations and Constraints

Known limitations and constraints in the solution.
  1. It is currently required to send the reservationId of the account to which the charge is to be posted. It is not possible to simply post a charge against a room/roomId.

  2. Posting phone charges by only transmitting meter pulses/units or by transmitting call length and dialed digit (= amount calculation in PMS) is not possible.

    The final phone charge amount to charge must be sent in the postBillingCharges operation.

  3. Transmitting phone charges for non-revenue line numbers (for example, employee phones, office phones) is currently not possible as the postBillingCharge operation requires a reservationId.

Note:

We are working on creating an operation that simplifies the phone postings by using the roomId. Also, this operation would not require sending the reservationId to properly post phone charges into OPERA Cloud PMS.

Anti-patterns

These are things to avoid during implementation.

To learn more about functional, non-functional, and technical anti-patterns, refer to the Anti-Patterns topic in the latest OHIP user guide.