This document describes the new features, modifications, and corrections effected in mycloud release Sprint 1.0.1.1.3.

This document is divided into the following sections : 

1. About the Release
2. New Features
3. Modifications / Enhancements
4. Corrections / Bug Fixes
 5. Known Restrictions / Issues 

About the Release 

Release Date: 14 August 2017 

Modifications / Enhancements 

This release includes following new modifications / enhancements:

1. PMS => Manager functions => Meal plan => Define meal plans with per room concept :-

Meal plan set has been modified to setup "Meal plan" and "Meal type". now users can define a meal plan and meal type from the system itself.

* Now meal plan can be defined per room basis also. The previously meal plan can be defined based on the number of pax defined for a reservation. But now meal plan can be defined per room basis also.
* Meal plan can be amount or percentage-based. Previously this configuration was global for all meal plans, but now each meal plan can be set up independently as amount or percentage base.
* In a single meal plan different meal types can be defined with a different set up for per room or per pax. * If a meal plan is not defined as per room, then it is per pax. * Percentage based meal plan can not have per pax meal types, it can have per room meal types only. * To make a meal type per room, just check the "Per room" checkbox on the meal plan details screen. 

2. PMS => Reports => Over credit limit report :-

Over credit limit report has been modified to show the guest on the report whose balance of direct folios (1, 2, 3) exceeds the credit limit defined on the advance control setup.

Credit limit has been removed from reservation screen, now there is no individual credit limit for each reservation, it is common for all reservations and can be defined on advance control => step 4 as highlighted in the next screen.

The system checks the over-limit authorization amount value also to qualify the guest for over credit limit report. Over limit authorization amount value can be defined on "Folio instructions" screen as highlighted in the next screen. 

Guests, whose balance of direct folios (1, 2, 3) is more than defined credit limit, will be qualified in the report. There is a parameter on the report "Consider pre-authorize amount" if this is considered then the report will consider the pre-authorized amount and will show those guests whose balance of direct folios (1, 2, 3) minus authorized amount is more than credit limit. 

3. PMS => Reservation Rate Plan => Get auto post charge amount from default price of the charge code :-

PMS => Reservation rate plan screen has been modified to get the default price and populate in the amount field of autopost field as highlighted on the next screen. This default price is set on the revenue charge setup screen.
The amount column will be populated with default price when the value of charge value is changed in autopost column. 

4. POS => Cashiering => Print check on full settlement :-

Check settlement process has been modified to print the check on full settlement. After full settlement system will execute a direct print process which will result in a check print on the default printer. 

5. POS => Cashiering => check details => Give settlement details on check details section :-

POS cashiering screen has been modified to show the settlement details also as highlighted in the next screen. Previously this information was not available on check details section.

6. WBE => Show max adult and child message along with room type:-

Web booking engine modified to show the maximum allowed adult in a room as highlighted in next screen (this maximum number will be set on room type setup)

If guest try to put the number of adult more than defined maximum number of adults and rooms are available then the system will show the room but without book button, as highlighted in the next screen 

7. WBE => Web restriction should be applied in case of same day reservation from the website (Guest can’t book for same day booking):-

Web booking engine has been modified to restrict guest not to take booking for today (business date). Guest can not take booking if try to make a booking with arrival date equal to business date.
To configure this restriction System Admin => Interfaces configurations => Web booking engine has been modified as highlighted in next screen

"Restrict guest not to take booking for next 'N' days" option given on web booking engine configuration screen. If this option is checked then web booking engine will not show availability for next 'N' number of days including today. e.g. if given number of days is '1' then web booking engine will not show availability today (business date) only. if the given number of days is '2' then web booking engine will not show availability for today (business date) and tomorrow (business date + 1).
if given days is 'N' then web booking engine will not show availability from business date till (business date + 1 - N) 

Corrections / Bug Fixes 

This release includes the following corrections/bug fixes:

1. POS => Cashiering => Items do not get refresh if menu has apostrophe in description :-

If the menu description had apostrophe in it's description then the system was not able to load the items of that particular menu on clicking on it. The issue has been fixed in this release.

2. WBE => Calculate tax break up based on Inclusions also:-

If any rate having inclusions defined in it and the taxes attached to room charge and inclusions are different then the system was calculating taxes based on room charge tax definition resulting wrong tax value and total value. This issue has been fixed in the current sprint. Now web booking will calculate taxes on room charge and inclusion component separately giving correct tax and total value.